|
![]() |
Optional. Complete this tab to:
Page
and Page List
properties, define auto-population mechanisms.The format and contents of this tab depend on the Property Mode value (on the General tab).
Field |
Description |
Max Length |
Optional. If the type is Enter the number here. If a user or activity attempts to assign a longer value to the property, the clipboard does contain the longer value, but also has an associated message.
This field is visible only for |
Expected Length |
Optional. Enter the typical length in characters expected for the property being defined, as entered into a form. This does not affect the number of characters that can be stored internally in the property value. If you associate the standard HTML Property rule FixedSizeForInput with this property, the system uses this value to define the size of HTML input textboxes. Use the similar FixedSize HTML Property rule to apply this limit to both input and display presentations of the property. This field is visible only for |
Override Sort Function |
Identify here a function rule in the Pega-RULES:Sort library or a custom function in a custom Sort library. For a custom function, enter the RuleSet name, a colon and the sort function name. This field is visible only for |
Access When |
This field is meaningful only when the Type is Identify the second key part of an access when rule (Rule-Access-When rule type) that controls whether or not the clear-text or encrypted value appears in reports and forms. Design the access when rule to be true for those operators, situations, and times when the clear text of the property value is to appear, and false otherwise. |
Edit Input |
|
Validate |
When users complete and submit a form containing a value for this property, the system first applies the edit input rule. This rule may transform the input text. Next, it applies the edit validate rule, which may cause a message to be added to the property indicating that the property value has failed validation.
This field is visible only for |
Column Inclusion |
Optional. If this
The other choice
See How to expose a property as a database column.
|
Cannot Be Declarative Target |
Select to prevent this property from being the target of a Declare Expression rule.
This restriction is meaningful only for |
Cannot be included as an input field |
Select to turn on the pySpecial restriction for this rule. If selected, users cannot directly enter a value for this property on an HTML form. This restriction improves system security and reduces the chance of errors that can occur when one property is in some cases computed and in other cases directly input. Such properties are sometimes called special properties.
|
Reference Property |
Select to make this property a reference property, a property that can link to a source property. Reference properties can reduce the need for duplicating data values on multiple pages or objects, and can simplify lengthy property references. Use the Property-Ref method in an activity to establish the contents of a reference property.
|
Optional. If the mode of this property is Page
or Page List
and the Page Class identifies a concrete class, your application can automatically retrieve, compute, or references values for the property by defining a source of page data. If configured, then Process Commander at runtime, when the page or page is accessed, retrieves data for the page or pages based on the value of specified properties.
Use of auto-populated Page
or Page List
properties can simplify your application by eliminating the need to write an activity to populate the properties, or by eliminating a routine step in an activity. The content of the page or pages can be copied from:
If the Reference Property option is selected, the data is retrieved and copied to a temporary page (or a Code Pega-List page, for Page List properties), rather than copied to the property.
Auto-populated pages are analogous to backwards-chaining Declare Expression rules, in that the value of a property is computed only when the value is needed. However, Declare Expression rules compute only scalar properties; this feature computes entire pages or lists of pages.
Auto-population occurs only when at least one embedded property on the page or pages is accessed, for example displayed on a work object form or used in an activity.
To debug auto-populated properties, start the Tracer tool, open the Tracer Options form, and select the Auto Populate Properties event type.
Field |
Description |
Auto-populate Property |
Select to indicate that values of this This field is visible only for properties of type |
Use Declare Page to Perform Load |
Select to indicate that values for this property are to be populated by a declare pages rule. |
(no label) |
If this property has mode |
Advanced Auto-population Options |
Typically, you can cause auto-population of this property by
For example, to populate a page of class Data-Admin-Operator-ID, set a value to the property Data-Admin-Operator-ID.pyUserIdentifier. On the Basic tab of the Class form, pyUserIdentifier is listed as the key to these objects. In less typical situations, the key value is as the value of a separate property in the current object, or is computed from multiple separate properties each providing one key part. Select this option to record how Process Commander obtains the key to an object (or keys to a list of objects). You can load a Page mode property, with an object from the PegaRULES database. Select:
|
Autopopulate using instance handle from parent page | |
Get handle of associated instance from |
At runtime, when this |
Autopopulate using class keys from parent page |
![]() |
Key of associated Instance |
Read-only. Identifies a property that forms the key, or part of the key, of instances of the Page Class class. |
Value from Property |
At runtime, when this |
Auto-Populate List using Conditions |
![]() |
List Condition for Associated Instance |
Read-only. Identifies a property that forms the key, or part of the key, of instances of the Page Class class. |
Value from Property |
Enter at least one nonblank value. When the |
Optional. Complete this array to associate one or more property qualifier rules (Rule-Obj-Property-Qualifier rule type) with this property.
Each property qualifier you list here provides additional information at runtime about the property, and may alter the behavior in computations or presentation of the property.
You can
provide a value for the qualifier on this tab, thereby defining
a permanent value. Or when desired, you can leave the value
blank and use Java methods in the PublicAPI to set or test
values dynamically. For details, see More about Property Qualifier rules.
Field |
Description |
Qualifier |
Optional. For a permanent qualifier, enter the value in a pop-up dialog box:
|
Click Explore after you save the form if you completed the Table Type field on the General tab and want to preview the presentation of choices for this property when presented in input mode. This display also identifies any Declare Expression rules that reference the property, and dependencies among expressions. See Properties — Working with the Explore Window.