Important: ParentProcess and SubProcess relationships are only evaluated on the server. When run locally in ISD, CTRL+Spacebar will not display the node IDs or variables across that relationship.
Variable: Variables shared across the Parent and Sub processes without needing a prefix or suffix, simply refer to them with their name. In the below example the email_Header variable is referred to as 'email_Header' in both the SubProcess and ParentProcess.
Node: Node IDs are referenced by the [SubProcessID]_[NodeID] as described in Infor's Document Library. When referencing a subprocess node on the parent process in Javascript, I recommend surrounding the whole thing parentheses, for example (SubProcess8220_nodeGetAccessToken_result).length > 1. The best way to see the naming scheme is to run a flow on the server that has a ParentProcess + SubProcess relationship and then look at the Work Unit's log in Process Server Administrator.
Underscore character: I recommend treating the underscore (_) character as a protected character because the process logs may get confusing if you can't tell the difference between a parent_sub process relationship and just a node/variable in the flow. I had used understand throughout my Node ID names, and it made the log files very confusing.
Example
Main process: Start > SubProcess > Email > End
Subprocess: FromParent > Assign > ToParent
Run order: Start > SubProcess_Assign > Email > End
Flow: The Subprocess start node creates the variable email_Header and then the SubProcess_Assign assigns it a value. The Parent's email node uses the email_Header variable in the email body using <!email_Header>.
