Managing AIS Properties

Management > Administration > Customization: AIS Properties

You can define additional properties for the asset interface system (AIS). Set or unset these properties in the Management > Asset Interface System > View and Change Properties window or, with a folder or asset selected, in Explorer > Assets > Properties. Search for and use these properties in automatic actions and other APIs. You can also search custom AIS Properties in the AIS Property Search window.

Property	Type	Description
Name	Text field	The name of the property
Inheritance	Drop-down list	The inheritance of the property, either: Not inherited – Property value set on a node is not inherited by its children. Inherited – Property value set on a node is inherited by its children, unless overridden by a child's explicit value. Inherited with path – The AIS path is appended to the property value for every child.
Property Type	Drop-down list	The Property Type allows you to determine whether this AIS Property takes an arbitrary string (if it is of type Text) or if the AIS Property will force the user to choose from a set of predefined values (if it is of type Selector). The type of property value can be either: Text – Can contain any text value. Selector – Value may be one of the specified values, as defined in the Selector Values property.
Selector Values	Text field, List, Add and Remove buttons	The Selector Values allow you to define a list of values that the user will be forced to select from. For example, if you define a new AIS Property called "Status" you might specify Selector Values of "In Progress," “Not Started,” and "Done." You can then associate an asset or folder with a particular Selector Value, for example, "In Progress," in the Change Properties screen. To add a value, enter the value in the text field and click Add. To remove a value, select the value from the list and click Remove. There are various ways you can use these property values. For example, you can design a business rule that looks for assets with a value of “Done” (following the example given above), and when it finds one, send notification that it is done. You can use property values to determine which cost model to use, by defining Selector Values for each model, associating assets with a value, then writing an automatic action to look at the value and apply the appropriate cost model. You can define product property values, and map these to TM properties, and when your translators are looking at multiple previous translations, they can see which product the translation was for, so they can determine if that translation should be used for this product or not. These are some examples of how Selector Values can be used.