When building processes in Creatio, we may need to integrate
the necessary data logic with other available built-in system processes.
Normally an admin might need to go to the system administration area, find the
necessary system feature, and run it to achieve the desired result. Behind the
scenes, this will likely kick off a built-in business process. If you tried to
call such an internal process directly, it might be challenging to determine
how exactly to call that process and what settings/parameters it needs to
As an example, we can look at the security rights initialization for an object. We have a specific situation where some Activities are missing their Owners being participants on their activity records. So, we want to build a business process that first adds the owners as participants on their activities. Then, someone needs to run the “Update record permissions” admin feature so the built-in access rights are added. Normally we do this part using the Object Permissions area.
It would be very nice if we can eliminate the manual work
for the admin by adding the “Update record permissions” step to a business
process, so that it can be made to run automatically off hours at a
Below is how the business process could look. The first step adds the necessary participant records via a standard “Add data” element. The second step needs to call the built in “Object record rights actualization” with the correct parameters so it runs correctly ONLY for Activity records.
To find the necessary settings for the sub process “Activity
record rights actualization”, lets first navigate to the Object permissions
area in Creatio.
Next hit F12 and turn on the developer tools, which will
then show the browser activity performed when a specific action is triggered. The
objective here is to turn on the browser based logging and capture the
necessary information so we have the correct settings for our business process.
Now perform the “Update record permissions” operation for the Activity object and you will see the actual processing being initiated in the Payload tab.
Notice how the schemaName indicates the name of the internal
process that is being launched. This is the same process we must call for our
need. Also, there is a parameter indicating which object this operation is
being performed for. This is the Activity object, but note that it is
referenced by its internal schema UID (ending with ‘9f89’).
Next we need to apply these same settings to our process as indicated below. Note that the developer tools in the previous step show the internal codes, while the sub process settings show a more verbose name, so they look slightly different but internally refer to the same thing.
Once the settings are properly configured and integrated into the desired process, it should run automatically without any user intervention.