Thanks @Steve for flagging this, for some reason I missed this post. My answers are inline (I have also updated the help article) :
- Add: A new record will be created using the data you supply. If another record exists with the same primary key, that record will be updated and used.
a. Where will this record be created? You never reference table?
This record will be created (or updated if an existing record with the id already exists) in the table configured as the input table(entity) in the process that is being called.
b. What about returned results? How do you use those variables as input?
Assuming in this case you are referring to a prior “Call process” step in this process (lets say “Call process 1”) whose return values you would like to use as inputs to the current “Call process” step (lets say “Call process 2”). If so the format you will use in the current step input field would be [Call process 1].[Approval] assuming Approval is one of the “Return values” step in the process that is being called via “Call process 1”.
- Lookup: The record will be retrieved using the primary key. Any additional columns will be used to update the record.
a. Primary key from where and to where?
Primary key for the row of table (t1) that is the input table(entity) of the process (p2) that is being called in this step of the current process (p1). The key can be an expression that refers to any column of the row of the table that is the input entity to the current process (p1).
b. What happens to columns which you don’t specify?
If the row was successfully looked up (assuming a valid key was specified) then if any columns are specified, they are used to update that row. If no columns are specified, that row is only looked up and no updates are performed.