Property form
|
The General tab for properties has three sections: Property Type, Data Access, and Display and Validation.
A property has one of eleven modes. Each is defined in the table below. Three are string-based modes, three are page-based modes, and five are modes used with Java objects. The appearance of the General and Behavior tabs depends on the mode chosen.
Use the Property Mode selection box to choose a mode. The property mode determines how the system represents the property data. After you select a mode, consult these topics to complete the General tab fields:
Mode |
Description |
|
Select The internal value of a For example, use this mode to create a property that can hold a birth date. The standard |
|
Select If you create a Value List property named LetterSent, you can use it to hold a list of values. For example, you can use an activity or an HTML form to set LetterSent(1) to Mom and LetterSent(2) to Dad. After setting these values, the LetterSent An example of a standard |
|
Select If you create a Value Group property named Birthday, you can use it in your future configuration to hold a group of values. For example, you can use an activity or an HTML form to set Birthday(Bob) to July and Birthday(Mary) to September. Birthday(Bob) and Birthday(Mary) become elements of the Birthday Value Group. |
|
Select For example, a Page mode property named Originator can contain information about the originator of a work item, such as the originator's name, account number, and so on. An example of a standard |
|
Select For example, a Page List property named Contacts can contain the pages Contact(1), Contact(2), Contact(3), and so on. Work-.pyFlowActionCosts is an example of a standard |
|
Select For example, the standard |
|
Note: Select Some properties with this mode can be saved as persistent data in the PegaRULES database. If the Java class of the Java object instance implements the |
|
Note: Select |
|
Note: Select |
|
Note: Supports the Pega 7 Platform Java pages feature that enables your application to interact with Java objects as though they were pages and properties on the clipboard. Select For information, see Working with Java Objects (April 2005), a document available in the Integration section of the PDN. |
|
Note: Supports the Pega 7 Platform Java pages feature that enables your application to interact with Java objects as though they were pages and properties on the clipboard. Select |
Caution: If you update an existing property and change the Property Mode, additional steps may be necessary. See Revalidation is necessary after certain property updates in More about Properties.
Use this section to configure automatic data access and persistence settings.
Section | Controls |
---|---|
Data Access |
Select a Data Access Type. The options are:
If you choose Automatic Reference to class instance (Linked) , further fields appear:
|
Data Persistence |
The system saves the property data with the work item for which it is used by default. Check the "Don't save property data (transient)" check box to prevent the system from saving the data with the work item. |
Section | Controls |
---|---|
Data Access |
Select a data access option from those provided:
If you choose "Refer to a data page", further fields appear:
If you select Copy data from a data page, you can select a data transform in the Data Transform field that appears. This allows you to copy only a subset of the results on a data page into the property. To create a new data transform, specify a name and then click the edit icon to the right of the field. Note: When you select Copy data from a data page, be aware of the following behavior if the value for a parameter is missing:
|
Data Persistence |
|
In this section, you configure which control displays the property and, optionally, validation of input data.
To configure the UI control:
For information about configuring validation tables, see Property form General tab — Configuring validation.
You can use other methods to associate a value with a property, including:
It is also possible to use any of the Property-Set methods in an activity, but Pegasystems does not recommend using this method.
Note: The values of many standard properties, such as pyUserName (which holds the identifier for the current user), are set automatically at log-in.