This documentation supports the 9.1 version of Remedy Action Request System.

To view the latest version, select the version from the Product version menu.

AROutput step

The AROutput step allows data to be inserted into a BMC Remedy AR System form. It also:

  • Connects to the AR System server using the connection input parameters. A connection is created once and reused.
  • Substitutes commit size and qualifications with real values, if variables are used.
  • Checks if it should start a new batch based on the flag, if the commit size is provided. This flag is true by default. After a transaction is started, it changes to false. Once the transaction is committed, the flag is reset to true.
  • Retrieves the input row from the previous step using the Atrium Integrator get row API function.
  • Converts the Atrium Integrator input row to an AR System form entry using the Mapping Field list. The Atrium Integrator row data type is converted to the AR System data type. After the value is converted to the corresponding AR System data type, a second-level conversion is required if the field's data type does not match the converted value's data type. The data type conversions are listed below.
  • Parses the matching qualifications and substitutes the values of stream fields from the input row in the qualification object.
  • Prepares the merge type based on duplicate request action, requires any required fields, and enforces pattern-matching flags.
  • Uses the Java ME API call by providing the AR System form name, qualification (optional-if not present it passes a NULL), merge type, and multi-match option. If the server does not support the new Java ME API with a qualification, then it explicitly gets the matching request using a GLEWF call. Then it performs the merge based on the specified merge type.
  • Checks whether it is time to commit the transaction based on the record number if a bulk transaction is started. If it is, then it calls the end bulk entry transaction API and sets the start bulk entry transaction flag to true.

AROutput step in the Spoon client

General tab

The General tab contains three fields:

Connection — Click the New button to create a new AR System server connection. Click the Edit button to edit an existing connection. Select an existing connection from the dropdown menu.

Form Name — Name of the AR System form used to import data.

Batch Commit Size — (optional) If provided, data will be imported using bulk API, which may be specified as a variable. If it is specified as a variable, the AROutput step will use the actual value provided.

Checkbox — An option to switch to a single-row commit if batch-commit fails.

General tab in the AROutput step

Duplicates tab

The Duplicates tab contains four fields:

Duplicate Request Action — Select Error, Create New, Overwrite or Update for the duplicate request ID action.

Match By Request ID — Select to use the Request ID for a matching output row.

Multi Match Option — Select when more than one record matches the matching qualification.

Matching Qualification String — (optional) If a qualification string is not provided, matching occurs with the Request ID. Variables may be used in the string. At runtime, variables are substituted for actual values. Click the Configure Matching Qualification button to open the qualification helper dialog and configure a matching qualification. Fields from previous steps are displayed here and may be used inside the qualification.

Duplicates tab in the AROutput step

Data Handling tab

The Data Handling tab contains three options:

Require Required Fields — Select this option to allow or disallow null values for required fields.

Enforce Pattern Matching — Select this option to enforce pattern matching. For example, a pattern may be configured such that a field's value is alphanumeric. Selecting this option will ensure that this pattern is enforced.

Skip Workflow Processing — Select this option to bypass workflow processing when this row is written to the form. When selected, workflow defined on a merge action for this form will not be executed.

Data Handling tab in the AROutput step

Field Mapping tab

The Field Mapping tab allows you to map the output fields from previous step(s), or stream fields, to their respective AR System form fields.

Field Mapping tab in the AROutput step

The Edit Mapping button provides a helper dialog to map the fields.

Enter Mapping dialog from Field Mapping tab

AROutput data type conversions

Atrium Integrator Adapter Data Type

AR System Data Type

None

Null

Number

Real

String

Char

Date

Date

Boolean

Enum

Integer

Ulong

Bignumber

Decimal

Binary

Attach

Was this page helpful? Yes No Submitting... Thank you

Comments