Two Different Applications having same work object prefix id
We are upgrading an application from our V6.2 to V7.1.5 . But the application we are upgrading has the same case ID prefix as one of our existing application in V7.1.5 . So after the upgradation both applications are getting the next case ID from the same sequence number which is not an expected behaviour. Is there any other way we can change this applications to follow their individual sequences instead of a common one despite of the same Prefix.
Pegasystems Inc.
IN
Hi Sowmya,
Thanks for posting on PSC.
Try saving "GenerateID" an OOTB activity in application-specific ruleset and then configure your IDPrefix.
This link has example with a usecase to customise this activity:- https://pdn.pega.com/community/pega-product-support/question/unique-identifier
Hope it helps, kindly notify by marking this post as answered if it does.
Regards,
Asif
Pegasystems Inc.
US
Hi Sowmya,
As per my understanding you have the application1 with prefix say C-100 in Pega v6.2, now you are upgrading this environment1 from v6.2 to v7.1.5. Now the environment1 will be upgraded to Pega v7.1.5 and your application1 will continue with the prefix C-101 for the new work object.
So how the second application with same prefix C- comes into your environment1?
Regards
Mahesh
Cts
US
Hi Mahesh,
In Pega v7.1.5 already there is a different application which is having the same prefix C-. So if we are moving our v6.2 application to v7.1.5 there is an issue as it holds same prefix.
Thanks,
Sowmya
Pegasystems Inc.
US
Hi Sowmya,
If you are talking about the Case prefixes then its just a design problem i would say. In Pega if you have multiple cases with same prefixes then the sequence number will be used by both the cases during work objects creation. So now i see the below option to you for this design problem:
- Import the Case1 which is available in lower environment into the higher environment.
- Now change the Case1 prefix with unique prefix in the application after import.
- Leave the old work objects of the Case1 with the same old prefix which doesn't has any significance in the processing.
- With this process you can create the new work objects with unique prefix in the higher environment.
Hope this might help you to solve this design problem.
Regards
Mahesh
Cts
US
Hi Mahesh,
Without updating prefix id is there any other way we can achieve this by customizing pc_data_uniqueid table which is been referred from GenerateID activity.
Thanks,
Sowmya
Pegasystems Inc.
US
I am not pretty clear how you are going to customize this activity with the business logic, if you think it is feasible to your requirement you can have a try. But you need to be very careful in implementing your business logic as it might effect the overall application.