M3 Workflow Builder

The M3 Workflow Builder creates a ready-to-use workflow for a single M3 API transaction. You pick a connection, program and transaction, review the input and output fields, give the workflow a name, and the builder generates the workflow for you, with no manual step configuration.

What it is for

The main purpose of the M3 Workflow Builder is to make it easy to build workflows against Infor M3 for use in App Builder. For workflows that end users run from Excel in VXL Live, build a regular workflow instead — see Create a New Workflow.

Go to Administration → Workflow Management → M3 Workflow Builder. The menu item requires write permission on workflows.

You can also open the builder from inside App Builder: in a draft app version, choose Resources → Workflows → New Workflow → Simple M3 Workflow. See Workflows as app resources.

---

Build a workflow

An M3 program is an M3 API, such as MMS200MI (item master data). A transaction is one operation in that program, such as GetItmBasic (read basic information for an item).

1. Connection — select an M3 connection.
2. Program — search for and select an M3 program.
3. Transaction — search for and select a transaction of that program.
4. Review the Input Fields and Output Fields tables. They show each field's name, description, type and length, and which fields are required.
5. Under Create Workflow, enter a Workflow Name and select Create.

When the workflow is created, a message shows its Workflow ID. If a workflow with the same name already exists, nothing is created.

---

What is generated

The workflow takes the transaction's fields as input and returns the matching records and any error message. You can open and edit it in the normal workflow builder.

---

Test the workflow

After creation, the Run Workflow section confirms that the workflow can be used by App Builder. It is available immediately, so testing is optional.

To test, fill in the input fields (required fields are marked with *) and select Run Workflow. The result shows the number of records returned and a table with the output fields, or the error details if the call failed.

---

Technical details

• The workflow has a manual trigger, a Transform step that builds the M3 request, a REST API step that calls M3 through the selected connection, and a second Transform step that shapes the result.
• Input schema: numeric fields are numbers, other fields are text limited to the M3 field length, and date fields use the YYYYMMDD format. Mandatory M3 fields are required. A maximum-records input limits the number of returned records (default 1000).
• Output schema: a count, a records list with the transaction's output fields, and the fields errorMessage, errorType, errorCode and errorField, which are empty when the call succeeds. Numeric output values are converted from text to numbers.