Configuring the Landmark Transaction node

  1. Select the Landmark Transaction start node.
  2. On the General tab, specify this information:
    Configuration name

    Select the configuration that will be used 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 text box. This script can be edited 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 using 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 will be disabled if Execute via web service is not selected.
    It will return zero records rather than an error if the role you have specified 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 one you've specified doesn't have enough access.

    Optionally, you can use Run as Role and Run as User 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 will be automatically escaped (\&).

  3. On the On Error tab, specify this information:
    What should happen on an error?

    Select from these options:

    • Notify

      Select this option to send a notification when an error occurs. If this option is selected, you must fill out the notification details.

    • Custom log entry

      Select this option to create a custom log entry in addition to the system-generated log entry.

  4. Select the Landmark Transaction end node.
  5. On the Break Condition tab, specify any valid true/false conditions that must be satisfied to end the iteration.
    Note: If a variable is used as part of the condition, you must remove the surrounding brackets (<! and >).