Question
LTI
IN
Last activity: 5 Jul 2021 5:12 EDT
The case IDs increase everyday by 1000 and users do not have the case IDs in strictly increasing sequence.
The case IDs increase everyday by 1000 and users do not have the case IDs in strictly increasing sequence. Support article link : https://community.pega.com/support/support-articles/case-ids-increase-daily-1000
We are upgrading our current pega application from 7.4V to 8.5V, is the above one is applicable for existing case types or it is applicable for only new case types which we build in upgrade version.
Pegasystems Inc.
ES
You can define the setting for all existing prefixes or just for specific prefixes. On this article on Pega Community you have more details on how to achieve the required outcome: https://community.pega.com/knowledgebase/articles/whats-new-pega-platform/increase-performance-work-id-generation-83
This change was introduced on 8.3 and it is applicable for 8.3 and any higher version. Please be aware that the change was done to improve performance of IDs generation, putting this setting back to 1 will not allow you to get benefit of the improvement on performance.
LTI
IN
@Miguel García Thanks for details.
Can you please advice on below query
In our current upgrade pega version we have DSS: idGenerator/WORK-/batchSize value as 1000 , we have one case type defined for one of complaint process and the prefix is COMP-. So when we create case on two different nodes what is the sequencing of cases it will follow. There is no changes we have made for case type in upgraded version from 7.4V to 8.5V.
Example:
Current we have COMP-4000 case in current system
Once we create case on two notes, it will create COMP-4001 and COMP-4002?
Or COMP-4001 and COMP-5001?
Pegasystems Inc.
ES
@Jitendra B if you keep the setting to any value higher than 1, sequencial order cannot be guaranteed. This example from Pega Help can provide further insight:
Note: When work IDs are generated and the batch size is set to 1000, performance is increased but there might be gaps in the numerical sequence of the IDs. For example consecutively generated work IDs might come out as TASK-1, Task-1001, TASK-2001, TASK-2, TASK-1002, TASK-2002. As more work items are created, IDs are created that fill in the gaps between previous created IDs. If you want fewer gaps in your work IDs, you can set the idGenerator/defaultBatchSize dynamic system setting to 100. This value causes fewer gaps in the work IDs but yields a smaller increase in performance. To eliminate gaps in your work IDs, set the idGenerator/defaultBatchSize dynamic system setting to 1. Note that setting the dynamic system setting to 1 might cause low performance.
LTI
IN
@Miguel García thanks for detailed explanation.
Would you able to confirm this change is applicable for all case type in the upgrade pega application right?
I mean we have around 300 case type in the current application and we are upgrading the pega application from 7.4v to 8.5v.
Just need to understand the same will applicable for all case types if we won't change any settings in the upgrade version.