Release, Deploy and Run the Process
- How to release, deploy and run the Process
- How to work on the Tasks
- How to monitor the Process
- Step 1
Before you run the process, ensure that the process is saved and that there are no errors showing in the Design Console.
To run the process, you must first release and then deploy the Business Process project. Releasing a project creates a version or snapshot of the changes.
In the Process Builder, choose Release.
Add a Version Comment if needed and choose Release.
If it is an additional version, choose the type of version, add a Version Comment if needed and choose Release.
What’s going on?
Every time you release, a new version will be created. Versions are incremented automatically based on how you want to store the changes in the repository (that is as major or minor updates or as a patch). Versions use an x.y.z format where x is a major version number, y is minor, and z is the patch number. For instance, if you are releasing your process project for the first time, then the version will start with 1.0.0. The next time you release there will be options to choose from – that is, if the new version is a major, minor, or patch update; version numbers will be automatically updated.
The project released successfully and is ready to be deployed.
If needed, you can refer to the Documentation.
- Step 2
You can deploy Business Process projects from each released version of the project in the Process Builder or through the Lobby. Deploying the project makes it available for others to use it. Bare in mind that you can only deploy a released version of the project.
From the released version of the Business Process project in the Process Builder, choose Deploy.
In this case there are no Variables to set.
What’s going on?
Variables allow you to reuse certain information for a given Business Process project deployment. You use variables to pass parameters to automations. You can create variables in the Process Builder for which you can later set values when deploying the Business Process project.
To Deploy will take a couple of seconds/minutes depending upon how big your project is and how many different skills it has. Any errors during the deployment will be shown in the Design Console.
The project deployed successfully and is now ready for running and monitoring.
Once the deployment is successful, you will see a changed status. You can also see all your deployed and/or released project versions from the project status list next to the project name.
You cannot edit released or deployed projects. To continue working on your project, you need to select the Editable option from the list of released versions.
- Step 3
Now that you have successfully deployed your project, it is time to run the process and see the results.
From the deployed version of the Business Process project in the Process Builder, open the process Get Invoice Details.
Select Invoice Request Form.
Choose the Copy icon aside the Form Link in the Trigger Settings.
Open the Form pasting the Form Link in a browser window.
Fill the Invoice Request Form and choose Submit.
Do not enter any random value or else the Automation will not give any results.
The process is triggered. You can now work on the tasks and monitor the process.
- Step 4
Start in the Lobby and open the My Inbox application by selecting the buttonat the top right corner.
After opening the My Inbox application, you will see on the left-hand side all the tasks listed. Select the task with the invoice number with which you triggered the process.
Move on with one of the actions:
- Approve, Reject, Show Log (to see what has been done so far),
- Claim (to reserve this task for you) or
- Mail (to forward this task via email).
You could also sort, filter or group the tasks at the bottom of the task list with these buttons:
Depending on your selected actions and the information you have provided at the start of the process, the next task would be to Approve the invoice.
- Step 5
Navigate to the Monitor tab and choose Process and Workflow Instances.
Choose Get Invoice Details instance to check the status of the CONTEXT and EXECUTION LOG.
Go to Automation Jobs under Monitor.
You can see the Automation ran successfully:
Notice how the process instance progresses further to the approval step in the business process.
When running a process what actions need to be performed beforehand?: