Selecting document attributes

Select at least one attribute of the policy’s document. You can use the selected attributes in the policy rule, or the policy conditions.

  1. On the Attributes tab, click Add to display the Select Attributes window.
  2. Expand the tree and select the desired attributes. The selected attributes are displayed in the tooltip of the “Selected” count at the top of the window.

    For details on the attribute types you can select, see Attribute types.

  3. Click OK. The selected attributes are displayed on the Attributes tab.
  4. Optionally, change the names of the attributes on the Attributes tab. For example, you can specify the name of the document, to which the attributes belong, as a prefix.
  5. Optionally, specify filters for selected attributes.
    Data elements and attributes that are part of a repetitive structure may require additional filtering to be used in a condition. For example, the Location from the ShipToParty information on a Contract document can exist several times. To specify which Location address details must be used in the condition evaluation, add a filter on the attribute type of the Location element.
    Users who create alarms cannot specify filters. If a repeating element is used without a filter, then the first occurrence is only used in a comparison condition.
    To specify filters:
    1. On the Attributes tab, add one or more attributes that belong to a repeating group.
      For example:

      Contract/ContractHeader/ShipToParty/Location/Address/StreetName

    2. Select the attribute. The Filter button becomes enabled.
    3. Click Filter. The Edit Filter window is displayed. The xml-attributes of the selected element and the xml-attributes of its repeating parent elements are displayed.
    4. Specify the attribute to use for filtering. For example, specify type.
    5. Click in the Equals Value column and specify a value. For example, specify Office.
    6. Click OK.
    7. The path of the monitor attribute has now been updated with the filter condition.
      For example:

      Contract/ContractHeader/ShipToParty/Location/Address[@type=”Office”]/StreetName

  6. Click Save.

    There are some limitations when filtering the standard Infor BODs PulseTask and PulseNotification.

    Each BOD contains, among others, these sections:

    • Parameters = name/value pairs with types such as string, integer, etc. Each parameter has a Parameter/@sequence attribute that can be used for filtering.
    • TreeParameters = structures with nested levels and several fields per level.

    If the BOD contains both sections, for example the workflow task contains parameters and structure, then you cannot filter by Parameter/@sequence.