The Infor Lawson Transaction activity node

The Infor Lawson Transaction node enables you to perform a transaction to a "classic" form (Infor Lawson applications that are not Landmark based). These calls go through the Infor Lawson System Foundation Transaction service.

The Infor Lawson Transaction node can make use of the error connector. Configuring error handling and the error connector in Infor Process Designer

Some special characters that might be used with the Infor Lawson Transaction node require configuration to enable them. For more information, see the Infor Process Automation Administration Guide. For additional information about special character handling, see Encoding special characters for use with Infor Process Automation.

Note:

Input data will not be encoded by the node if an EJB connection is used. This could cause a problem if the ampersand (&) character is included in the data. Ensure that the ampersand (&) is explicitly encoded before passing in the value to the Infor Lawson Transaction node.

The Infor Lawson Transaction node builder displays all the hidden fields from the token in gray.

The "Direct IOS" method of connecting to Infor Lawson should be configured before you run a process that calls this activity node. If you are unsure if you are using this connection, contact your system administrator.

Infor Lawson Transaction node use (example)

Suppose you wanted to automate a process for updating the salary records for all employees who receive an annual increase. The Infor Lawson Transaction node is the part of the process where the update (to the HR11 form) takes place.

General tab


Field	Description
Name	The name of the Transaction Service (AGS) call to be performed. This name must be unique. This name becomes the prefix for variables from this Transaction Service (AGS) call. For instance, if in an e-mail you wanted to refer to an employee identified by this Transaction Service (AGS) call, you would use this variable: <!TData_EMPLOYEE> You can also reference a variable from a Transaction Service (AGS) call by indicating the order number of the data element returned. For example, <TData_1> refers to the second data element returned, that is, EMPLOYEE.
[open area]	The area where the Transaction (AGS) Query Builder appears. You may specify a query manually or use the Import or Build buttons.
Import button	Select this button to open the File Selection dialog box. From the File Selection dialog box, you can import a Transaction Service (AGS) query saved in a file and paste it to the Transaction Service (AGS) query string.
Build button	Select this button to open the Transaction Service (AGS) query builder. Note: Any hidden fields for the selected token are included, but are gray in color.
Stop process on error	When this check box is selected, and if no records have been returned, the process is stopped. This is especially useful when the data being queried is to be used elsewhere in the process.

Output variables


Variable	Description
NODENAME_RETURN_CODE	The return code (where 0=Success and 1=Failure) returned by a Transaction Service (AGS) call. For example, <!AGS2480_RETURN_CODE>.
NODENAME_ RETURN_MSG	The message returned by a Transaction Service (AGS) call. For example, <!AGS2480_RETURN_MSG>.
NODENAME_`FieldName`	The data returned from a Transaction Service (AGS) call. This is the field name that appears in the Fields column when you perform the call, for example, <!AGS2480_RQH_REQUESTER>. This example specifies the form field RQH-REQUESTER information that was returned by a Transaction (Transaction Service — AGS) activity node with the activity name AGS2480.