[Index]

Model: data/FieldDisplayPolicy

Field Display Policies

To access the latest documentation, go to Documentation and Resources at: https://voss.portalshape.com

Overview

Field Display Policies (FDPs) are applied to certain item types in order to modify the default form that is displayed when these items are created or accessed.

With FDPs, the fields on an item detail form can be grouped, disabled, and on-line help text can be added for a field. A field can be provided with a new label and its position on the form can be moved up or down.

More than one FDP can apply to a particular item type so that the selection of a particular policy will present another view of the form.

A FDP for an item type can be applied from a Menu Layout by selecting and associating it with the item on the Menu Layout. The Menu Layout is then selected to be part of a user Role so that users who have this role and log in will be able to have the item displayed according to the relevant FDP.

For example, a system may have users at Provider, Customer and Site administration hierarchy levels - all of whom may access the same items, but perhaps some item fields need to be hidden for administration users at a certain level. Field Display Policies can then be made that are applied to the Menu Layout associated with the administration users at these levels.

A quick way to add a FDP is to clone an existing Field Display Policy, modify it as required and then to select it for the model on a user's menu layout. In this way a user's interface can be modified from the point of user access to the model on the menu.

There is a unique constraint on the name of the FDP per hierarchy level. The same name can be used on another hierarchy, but a new name is needed at the same hierarchy.

If a FDP is called default, it will apply to a model by default.

Related Topics

Multi-vendor Subscriber Field Display Policy in the Core Feature Guide

Field Display Policy Input Reference in the Advanced Configuration Guide

Rules for Creating Field Display Policies

When creating groups and selecting the field transfer boxes of a group, a number of rules apply.

To understand the rules, consider a selected Target Model Type with the fields as listed below. Where the name starts with "A", the field is an array and where it starts with an "O" it is an object. The values "x", "y", "z" are also objects. The field "F" is neither object or array.

• A, A.x, A.x.b, A.x.c, A.x.d, A.y.r, A.y.s, A.y.t
• F
• O, O.v, O.z, O.z.a, O.z.b, O.w.d

Inclusion Rules

The following inclusion rules apply:

• If a parent object or array field is included, the parent and all its children will be displayed in the GUI.

  Example: if O.z is selected, O.z is saved as the fields and the GUI will display O.z and also inner fields O.z.a and O.z.b.

• If a specific selection and order of child elements are required, select these child elements and order them.

  Example: if O.w.d, O.z.b, F are selected, these three fields are saved in that order in the FDP group fields and the GUI shows only the inner field O.w.d, followed by the inner field O.z.b and lastly the field F.

• Inclusion of child fields in a group without the inclusion of the parent fields will display these child fields at the root level of the form.

  Example: if O.w.d, O.z.b are selected, these fields are saved as is in the FDP group fields list and only the inner fields O.w.d and O.w.b are shown in the GUI.

• Array children fields without their parent fields will be ignored by the GUI. Therefore, if the child fields of an array field are selected, the parent field should also be selected.

  Example: if A.y.s, A.y.t are selected, A and A.y should be selected.

• Array fields may not be split into different groups.

• The parents of fields cannot be in one group and its children in another.

  Example: O.z cannot be in Group 1 if O.z.a, O.z.b and O.w.d are in Group 2.

• Fields of the same object and members of the same array type cannot belong to more than one group.

  Example:

  • If A.y.s is selected for Group 1, then A.y.t cannot be selected for Group 2.
  • If O.z.a is selected for Group 1, then O.z.b cannot be selected for Group 2

• You can split the first level children of object fields into different groups.

  Example:

  • O.v can be in Group 1 while O.z is in Group 2.
  • For second level children: O.z.a can be in Group 1 and O.w.d can be in Group 2.

• To hide a field, do not move it to a Selected box.

  Example: To hide O.z.b, select O.z.a, O.w.d.

To order fields in a group, arrange them in the Selected box. Use the Move Up and the Move Down buttons under the box.

Ordering Rules

The following ordering rule applies:

The ordering of child fields and their parents depend on the presence of siblings, other parents and children. If a child is selected in a group and not its parent, but a sibling of that parent is selected, then the sibling's order will affect the order of the fields.

The logic of order resolution starts from parents to children, according to the rules below.

For example, we select fields in this order in Group 1:

C.z, A.x.b, A.x.c, B, A.y, A.x, C, C.w

Result:

• Parent fields on their own are considered first, hence our initial order is B, C.
• However, parent A is not selected; only the children. We determine where A was mentioned. In this case the children of parent field A were mentioned before the parent fields B or C. Hence children of A will eventually be ordered before B and C.
• Next we consider the selected first level child fields: C.z, A.y, A.x, C.w. The order becomes: A.y, A.x, B, C, C.z, C.w
• We now move down the levels: A.x.b, A.x.c.

Thus the final display order will be:

A.y, A.x, A.x.b, A.x.c, B, C.z, C.w

Further examples below illustrate the presence of parents, siblings and children on the selected order.

• We add fields C.w, A, C, B, A.x, A.y.

  Result: The order is: A, A.x, A.y, C, C.w, B.

• We add fields A.x.b, A.x.c, A.y, A, B

  Result: The order is: A, A.x, A.x.b, A.x.c, A.y, B.

  Note

  Note that A.x was added and that A.y is placed after A.x, since the children were ordered before A.y while A.x was never selected.

Clone a Field Display Policy

This procedure creates a copy, or clone, of an existing field display policy (FDP) to create a new FDP, starting with the configuration of the FDP you're cloning.

1. Login as Provider administrator or higher.

2. Choose the hierarchy.

3. Go to (default menus) Customizations > Field Display Policies to view a summary list of existing field display policies (FDPs).

4. Click on the FDP you want to clone.

5. Choose Actions > Clone.

6. Update the necessary fields for the cloned FDP.

7. Click Save.

   You can apply the cloned FDP by choosing it in a menu layout available to a role.

Add or Edit a Field Display Policy

This procedure adds and edits a field display policy (FDP).

1. Login as Provider administrator or higher.

2. Choose the relevant hierarchy.

3. Go to (default menus) Customizations > Field Display Policies to open the list of existing FDPs.

4. To edit an existing FDP, click on the relevant FDP and update the configuration, as required.

5. To add a new FDP, click Add on the toolbar, and configure the following:

   1. In the Name field, enter a name for the new FDP.

      • If the name is default, the FDP is applied to the target model type by default.
      • Each FDP at the same hierarchy level must have a unique name. FDPs at different hierarchies can share the same name.

   2. Optionally, enter a description.

   3. At Target Model Type, choose a model reference.

      The target model type defines the fields available for use in the FDP.

   4. At Groups, click the plus icon (+), then configure the following:

      All fields in the FDP must belong to a group.

5. At Field Overrides, click the plus icon (+), then configure the following:

   This step configures fields added to the Selected transfer box.

6. Click Save.

   If you're editing an existing FDP, your changes are saved.

   If you're adding a new FDP, the FDP is created and is available for applying to the item by selecting it in a menu layout available to a role.

Field Display Policies are applied to data models and domain models in order to modify the default form that is displayed when instances of these models are created or accessed. With Field Display Policies, the fields on a model form can be grouped, hidden, on-line help text can be added, a field can be set as read-only, it can be provided with a new label and the field order on the form can be re-sequenced. More than one Field Display Policy can be created for a particular model so that the selection of a particular policy will present another view of the model form. A Field Display Policy can also be selected for a particular model in a User Role so that users that belong to this User Role will by default view the particular model according to this display policy.

Model Details: data/FieldDisplayPolicy