Harmony Core Field Loop Extensions

Expansion Tokens

<HARMONYCORE_CUSTOM_FIELD_PARAM>

Inserts the name of a custom field parameter based on the fields user text or long description containing a special value like this:

HARMONYCORE_CUSTOM_FIELD_PARAM=name;

Alternate forms: none

<HARMONYCORE_CUSTOM_FIELD_TYPE>

Inserts the type of custom field based on the fields user text or long description containing a special value like this:

HARMONYCORE_CUSTOM_FIELD_TYPE=type;

Alternate forms: none

<HARMONYCORE_CUSTOM_FIELD_VALIDATOR>

Inserts the name of the custom field validation class based on the fields user text or long description containing a special value like this:

HARMONYCORE_CUSTOM_FIELD_VALIDATOR=name;

Alternate forms: none

<HARMONYCORE_FIELD_DATATYPE>

Inserts the data type of custom field based on the fields user text or long description containing a special value like this:

HARMONYCORE_CUSTOM_FIELD_DATATYPE=type;

The text inserted is defined by the value of type. If the data type is not defined in this way then the token will insert the base data type of the field based on <FIELD_SNTYPE>.

Alternate forms: none

<HARMONYCORE_FIELD_DATATYPE_VB>

Inserts the data type of custom field based on the fields user text or long description containing a special value like this:

HARMONYCORE_CUSTOM_FIELD_DATATYPE=type;

The text inserted is defined by the value of type. If the data type is not defined in this way then the token will insert the base data type of the field based on <FIELD_VBTYPE>.

Alternate forms: none

<HARMONY_ROLES>

Provides a way for field level role based security to be implemented. If you wish to restrict access to a field then you can specify the role or roles that are allowed to access the field by adding a special instruction in the fields long description, like this:

HARMONY_ROLES=role[,role...];

Note that the instruction is terminated by a required semi-colon. For example, to restrict the visibility of a field to only users that are members of the Managers role:

HARMONY_ROLES=Managers;

To restrict access to users who are part of the Managers or HR roles:

HARMONY_ROLES=Managers,HR;

Expressions

Does the field have a custom field parameter defined because it contains a value similar to HARMONYCORE_CUSTOM_FIELD_PARAM=name; in its user text or long description field.

Is the field is defined as a custom field because it contains a value similar to HARMONYCORE_CUSTOM_FIELD_TYPE=type; in its user text or long description field.

Does the field have a custom data type because it contains a value similar to HARMONYCORE_CUSTOM_FIELD_TYPE_DATATYPE=type; in its user text or long description field.

Does the field have a custom validation class because it contains a value similar to HARMONYCORE_CUSTOM_FIELD_VALIDATOR=name; in its user text or long description field.

The field has custom roles specified by a HARMONY_ROLES= specification in the long description. For more information see <HARMONY_ROLES>.

Is the name of the current field a reserved word? Currently the reserved words are "globalrfa", "synergyrecord", "metadata" and "originalsynergyrecord".