What is the logic behind the WPDS ID generation? When we start a particular job in Workpoint the WPDS format is 1234:WPDS. In IDM we observe the number 1-4 preceding the WPDS ID. Why is that?
Each work Item will be assigned two ID's, Job Id and Activity Id. When any work Item is created, a Workpoint is assigning job Id as well as activity id. Job Id will be same through out the approval process like 1234:WPDS. IDM is not appending 1 into WP ID. Workpoint is appending 1 and it is incremental when one process has sub-process.
Similarly Workpoint is appending 0 into activity Id which is incremental, representing how many iteration done between Approver and requester if any changes request done by approver (Consultant Process is one of the example).
If requester needs to change it, the ID will increment by one. If a value has to be changed it sends back to requester and the value will be changed and increment will go up by 1. Otherwise, it will always be 1. "1 1234:WPDS" is workpoint process definition id generated by IDM where 1234 is the job ID(generated by Workpoint) and 1 is pre-pending by IDM to job ID. Each job has one or more activity and each activity has its own id like 1 4 1621:WPDS is a work item id generated by IDM where 1621 is activity id(generated by Workpoint), 4 is pre-pending to 1621 by IDM and 1 is iteration (it is incremental and generated by workpoint).
Here are all the different valid codes:
WF_OBJECT_TYPE_PROCESS_INST = 1;
WF_OBJECT_TYPE_ACTIVITY = 2;
WF_OBJECT_TYPE_ACTIVITY_INST = 3;
WF_OBJECT_TYPE_WORK_ITEM = 4;
<Please see attached file for image>src="/servlet/servlet.FileDownload?file=0150c000004AKlkAAG" alt="CA04VST1.jpg" width="1506" height="814">