|
-
Enhancement to add a workflow that runs after an RBPM Resource has been requested. - The IDM RBPM server has added functionality where it will run a Provisioning Request Definition workflow if the Resource has been configured to do so.
This same workflow shall run upon resource assignment or revocation, after any approval steps (if included). It is expected this workflow will go through the work in provisioning/deprovisioning what this resource represents to the user, either through a user action or some automated means, such as a REST activity. This workflow will then use the resource bind activity to indicate whether the provisioning/deprovisioning was successful or not.
This workflow can be configured using the RBPM Resource editor, on the Provisioning tab. Note one can select Workflows of process type "Resource Provisioning" only.
As part of the 4.5 User Application Driver update, we will be shipping an example example workflow that can be used, or copied and modified.
Figure 1: Resource Provisioning setup
-
Fix for 'java.lang.StackOverflowError' during workflow looping - In this release, a new property has been added to the Condition Activity to avoid the 'java.lang.StackOverflowError' which was would occur in a workflow that had a loop with many iterations. Setting the new "Safe looping?" to true avoids the problem by running each iteration in a separate thread. Note each iteration will still execute serially. This is supported on server version 4.5 and above.
As way of illustration, consider the following workflow. Before the change, if there were a lot of tasks and we iterated too many times, the workflow would have ended with a fatal 'java.lang.StackOverflowError'. By setting the "Safe Looping?" to true, the workflow will complete.
Figure 2: Condition Activity Safe Looping
|