Configuring the Landmark Transaction node

  1. Select the Landmark Transaction start node.
  2. Click the General tab and specify this information:
    Note: All Landmark Transaction queries run with dataview off mode by default.
    Configuration name

    Select the configuration to use for this activity. To use an existing configuration, select a name from the list. To use the default configuration, leave blank.

    Landmark transaction string

    Click Build to use the Landmark Transaction Builder. The script of the API you built is displayed in the Landmark transaction string field. You can edit this script manually.

    Click Import to import a script that you created through another text editor.

    You can also specify the text of your script from scratch. Developers and other power users who are familiar with creating queries might find it faster to write a query manually rather than to use the Landmark Transaction Builder.

    Execute via web service
    The Landmark transaction is processed through the web service if this setting is enabled. Only the web service option is compatible with this setting, which uses run as role.
    Once enabled, specify the role in the Run as Role field in Landmark Transaction Builder > Properties.
    Note: The Run as Role field is disabled if the Execute via web service check box is cleared.
    When run through web service, the Landmark transaction returns zero records rather than an error if the specified role does not have access to the business class you are trying to query.
    Note: There is only support for one role. You can give that role access to multiple security classes if the specified role does not have enough access.

    Optionally, you can use the Run as Role and Run as User fields at the same time.

    Automatically escape & in variables

    This option is selected by default.

    If this setting is enabled, any ampersand (&) in the value of the variable supplied to the Landmark transaction query is automatically escaped (\&). However, this automatic escaping does not apply to the filter string function of the Landmark Transaction query node. For filter strings, you must manually escape variables using the format: Landmark_field_name operator \"value\".

    Wait for async action
    Select this check box to set a waiting time for any async action to complete. If you enable this option, you can specify a maximum wait time in the async action properties, or use the default wait time of 600 minutes.

    This option enables you to specify a waiting time for an async action, ensuring the process flow continues only after the specified duration. By default, the process proceeds when the async action is completed or the specified maximum wait time is reached, whichever occurs first.

    During this period, the Landmark transaction node is in Waiting status, and the working thread is released so another process can use the resource.

    Keep work unit active (recommended for short running actions only)
    Select this check box to prevent releasing the work unit thread during the process. This option is recommended only for actions that complete in a short duration.
  3. Click the On Error tab and specify this information:
    What should happen on an error?

    Select one of these options:

    • Notify: Send a notification when an error occurs. If this option is selected, you must fill out the notification details.
    • Custom log entry: Create a custom log entry in addition to the system-generated log entry.
  4. Select the Landmark Transaction end node.
  5. Click the Break Condition tab and specify any valid true or false conditions that are required to end the iteration.
    Note: If a variable is used as part of the condition, you must remove the surrounding brackets (<! and >).