In this article we will learn how to use one of the K2 blackpearl destination rule – Plan per slot (no destinations).
The K2 blackpearl Plan per slot (no destinations) Destination Rule can be used for activity with server events. K2 User Destinations cannot be configured when plan per slot is used and the server creates one instance per slot. Each instance will have its own activity data fields.
1 – Simple K2 blackparl Workflow process
By using Plan per slot and SmartObject event we will update all inactive users as active and send a notification. In the below image we can see there are 3 inactive users in table.
2 – K2 Destination Users
Select Destination Rule for activity and run in advanced mode, select plan per slot (no destinations) and destination rule has two options:
1) Can select number of slots to be created (static)
3 – Plan per slot
2) Number of slots will be created based on the number of records returned by the Smartobject List Method (Dynamic)
4 – Use SmartObject to determine number of slots
In our case, we have selected the EmployeeInfo.List.ID list field on the Destination Rule Options page and mapped Active property value as false.
This will create a slot for each inactive users
5 – K2 SmartObject loading destination users
In Smartobject Update method Map value for ID as ActivityInstanceDestInstanceData and Active as true.
6 – K2 ActivityInstanceDestinationData
7 – Employee Id from ActivityInstanceDestinationData
This will update all the Inactive users as active and notify the users.
8 – Notify Active Users Only
9 – K2 Notifications
We can set a Succeeding Rule for activity to check whether all slots of the Activity Instance “Active Datafield” is set to True. Once all the instances complete, the succeeding rule executes and thus process moves to completed state.
10 – K2 succeeding rule