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.
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.
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?
Posted: 3 weeks ago
Posted: 5 Jul 2021 5:03 EDT
Miguel Garcia Alvarez (GARCM)
Principal Service Assurance Advisor
@JithendraB 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.