Process Inputs define which records are retrieved from the database and loaded into the Process Logic workbook when a Process runs. Each input specifies an object to read from, a filter to control which records are retrieved, and a named range in the workbook where the data is written.
When the Process executes, all attributes of the specified object are loaded into the workbook in the order they are defined in the object specification. One column is provided per attribute. The workbook then recalculates using the loaded data.
Before you begin
Ensure the following are in place before configuring Process Inputs:
The Process record already exists.
The Process Logic workbook contains named ranges to receive each set of input data. See Process Logic Workbook.
Any Filters you need have already been created. See Filters.
Although there is a standalone Process Inputs screen that lists inputs across all Processes, configure inputs from the individual Process screen rather than that screen — it keeps configuration for one Process together and reduces the risk of associating an input with the wrong Process.
Configure Process Inputs
Open the Configuration application and navigate to Process Configuration \> Processes.
Select the Process that will use the inputs.
In the Process Input section, click Edit.
Enter the number of Process Inputs to create and click Add.
For each input:
Object Specification — select the object whose records you want to retrieve.
Filter — select the Filter that controls which records are loaded. If no suitable Filter exists, create one first. See Filters. The Filter can reference Process Parameters to make the selection dynamic at runtime.
Location or Name — enter the named range in the Process Logic workbook where the object data will be written. This must exactly match the named range defined in the workbook, including capitalisation.
Heading Location — optional. If you want the object's attribute names written as column headings in the workbook (useful for the Calculation Log), enter the named range for that heading area. Allow two rows: one for attribute names and one for unit labels. Leave blank if headings are not required.
Include Modification Dates — set to True if you want the hidden EU_CREATED_AT and EU_MODIFIED_AT attributes appended to each record. The object must have Filter on Modification Dates enabled for this to work. See Filters for details.
Enter an Audit Comment explaining the purpose of the inputs.
Click Save and Refresh.
How inputs work at runtime
When the Process runs, each configured input is retrieved from the database in turn. The Filter is applied, and the resulting records are written to the named range specified in the Location or Name field. The workbook then has access to that data in the cells you designed it to use.
Each input operates independently and can draw from different objects with different filters. The inputs are not ordered relative to each other — the order in which they are loaded into the workbook is determined by the named ranges, not the input configuration sequence.
Important notes
All attributes of the selected object are written to the workbook in the order they are defined in the object specification - so if an object has 12 attributes, 12 columns will be produced. The named range must be sized to accommodate this; if it is too small and overflow protection is not enabled, data will be truncated without warning.
If you change the attribute structure of an object — adding, removing, or reordering attributes — any Process Input that loads that object will be affected. Review dependent Processes before making structural changes to objects. See Assess the Impact of Attribute Changes.