#process references
Dynamic information about Process execution can be obtained with the #process reference.
#process.agent - the Agent's name that runs the Process.
#process.agentGroup - the Agent Group's name in which the Process was run.
#process.environment - the Environment's name in which the Process was run.
#process.executionid - the execution ID of a Process execution instance. See more information below.
#process.id - the unique ID assigned to a Process.
#process.name - the name of the Process.
#process.uri - the URI of the Process.
#process.version - the version number of the Process.
One practical example using #process references is to access a specific Process Instance by using the following URL structure: https://< your site name >.frendsapp.com/ProcessInstance/Instance/< #process.executionid >
Example: https://demosite.frendsapp.com/ProcessInstance/Instance/1b31bbae-dd2a-4876-927e-440dd2e7c992
Example Process
Here is a simple example Process to illustrate the use of #process references in a Process.
In the Process, the first Element initializes a variable with StringBuilder. In the Code Element, an XML message is created using #process references for the message content. The Send message Element sends the message to a demo REST endpoint using the POST method. Configuration details for each of the Elements can be found below.
If you have a Frends Environment and SQL DB in use, it is recommended that you create a similar Process and test it. Learning by doing is often the best way to learn!
Set message variable
Create message
Note how the #process references are used in the Create message Statement
Send message
Web RestRequest Task Frends GitHub page.
Example Process Execution
Study the example execution of the Process below. Focus especially on the message and its content.
Please review the following example execution of the Process provided below, paying particular attention to the message's content.
The next article is Example on How to use #trigger references.