When you use an activity or an HTML form to set the value of the property, the value can contain any graphic characters in addition to tabs, carriage returns, and line feeds.

Use the Text Property Type if a user may enter the value in a text area of an HTML form.

The values of properties with this Property Type are always encrypted when stored in the database. When on the clipboard, the values may appear as clear text (not encrypted), until the page containing the property is validated.

The value can contain only legal graphic characters. Tabs, carriage returns, and line feed characters are not allowed.

You can prevent any text field from echoing when typed into an HTML form using the PASSWORD input type:

<INPUT TYPE="PASSWORD" NAME=...>

This HTML does not cause any encryption. This native HTML feature is not related to the Password Type.

When you specify the value in your later configuration, use any sequence of digits for the value. You can precede the digits with a plus sign (+12) or a minus sign (-12).

Select Double to allow the property to hold a 64-bit floating point value. Do not use the Double property type to represent a precise value. Double properties are represented through Java double primitives, which are implemented in double-precision 64-bit IEEE 754 floating point format, and provide minimal precision. For precise decimal numbers, use a Decimal property type instead.

Your property can reference the standard property qualifier named pyDecimalPrecision to fix the number of digits the system keeps after the decimal position in values of this property.

Internally, a DateTime value is stored in the format YYYYMMDDTHHMMSS.QQQ GMT where T and GMT are literal characters, YYYY represents a year, MM is a month, DD is a day, HH is an hour value between 00 to 23, MM is a minute value between 00 and 59, SS is a second value between 00 and 59, and QQQ is a millisecond value between 000 and 999.

Users need not enter DateTime values in this format, as shortcuts and alternative entry formats are available.

Application users are not required to enter Date values in this format, as many shortcuts and alternative entry formats are available.

As a best practice, use DateTime rather than Date for properties that are part of work items, assignments, or other persistent objects in your application. Avoid using Date property types in persistent objects, such as work items or assignments, even if your application is used in only a single time zone, unless a time zone value is also stored in another property of the object.

Internally, a TimeOfDay value is stored as six digits in the format HHMMSS, with two digits for the hour, two digits for the minute, and two digits for the second.

For example, 000000 represents midnight and 120000 identifies noon. The value 235959 identifies the second before midnight.

Application users are not required to enter TimeOfDay values in this format, as shortcuts and alternative entry formats are available.

As a best practice, use DateTime rather than TimeOfDay for properties that are part of work items, assignments, or other persistent objects in your application.

• 1, -1 or Y for true
• 0 or N for false

A TrueFalse property with a null value ("") can be saved into the PegaRULES database, but this is not a desirable practice. To avoid possible confusion and errors, choose a value "true" or "false" when initializing a TrueFalse property using a data transform or through other means, as appropriate to the business situation.

The TextEncrypted type is differnt from the Password type. For TextEncrypted values, clear-text values are visible only if a Rule-Access-When rule evaluates to true.

If each value of the linked property forms the entire key to the instances of the linked class, enter the property name (the value you entered in the New dialog) in the Source Property column. If the values of the linked properties form only part of they key to instances of the linked class, complete the Source Property column by identifying the properties that supply the other key parts.

• If there is no value, the system uses the control named Default.
• Choose Default-NonNLS to use default presentations that do not reflect operator locale settings.
• Choose PromptSelect (for a drop-down list) or RadioButtons (for a rectangular array of radio buttons) in most cases when Table Type has Local List, Remote List, or Prompt List selected.
• Choose PromptFieldValue when Table Type has Field Value selected.
• ShowTextEncryptedPropertyValue is the default if the property Type is TextEncrypted.
• Do not choose SmartLabel, StartSmartField, SmartInfoBehavior, SmartInfo, ListView, ListToList or Chart; these are pseudo-controls with special, restricted use.

• Checkbox — pxTrueFalse
• Date — pxDateTime
• DateTime — pxDateTime
• Decimal — pxNumber
• Double — pxNumber
• Integer — pxInteger
• Password — pxPassword
• Text — pxTextInput
• TimeOfDay — pxDateTime

When completing a Field panel (for a cell in a harness, section, or flow action), you can override the parameter values entered here with values that apply to that cell only.

This button does not work with auto-generated controls. You can customize an auto-generated control only in a section or harness that contains the control. To customize the control, specify the rule in the Control field on the Cell Properties panel and use the Gear icon next to the field to open the control's Parameters dialog.

• None — No table validations apply.
• Local List — The set of acceptable values is provided directly in the General tab of the Property rule form. See Property form: General tab — Configuring validation.
• Field Value — The set of acceptable values corresponds to a set of field value rules. See Property form: General tab — Configuring validation.
• Class Key Value — The set of acceptable values is defined using the keys of a known class (a class other than this property's class). See Property form: General tab — Configuring validation.
• Remote List — The set of acceptable values consists of the elements of a Value List, Page List, Value Group or Page Group embedded within a single object. See Property form: General tab — Configuring validation.
• Prompt List — Acceptable values are enumerated as with a Local List, but for each internal value, a different localized value appears on input or output. See Property form: General tab — Configuring validation.