Production level and draft mode
Hello!
We change production level from 2 to 5 in system instance and restart the server (including removing extract marker).
However, flows with enabled draft mode are still being executed correctly.
Is this normal behavior? PDN says that draft flows are not allowed on production level 5 systems.
Thanks,
Yuriy Berdnikov
**Moderation Team has archived post**
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.
Pegasystems Inc.
IN
Hi Yuriy, Good Morning!
>>> We change production level from 2 to 5 in system instance and restart the server (including removing extract marker).
could you please confirm the values on clipboard page. A restart should take effect on this change.
- pxProcess.pzProductionLevel = 5
- pxProcess.pxAdminSystem.pyProductionLevel=5 (for double check...)
>>> However, flows with enabled draft mode are still being executed correctly.
they should be ignored.
>>> Is this normal behavior?
No, Draft option enabled flows will be ignored in Production system.
also please refer: https://pdn.pega.com/process/troubleshooting-fail-to-compile-generated-java-for-flows-in-draft-mode-on-production-system
could also please specify PRPC version?
Please share your thoughts/comments, Thank you!
psahukaru
it.ru
RU
Hi, Phani!
Clipboard show production level 5.
also role access is consistent with production level 5.
Problem affects only draft flows.
On another server we got similar problem: system was initially configured with level 5. Level was changed to 2, but draft flows still cannot be executed.
Pega 7.1.8
Pegasystems Inc.
IN
Post - I
>>> We change production level from 2 to 5 in system instance and restart the server
Draft enabled flows are being executed which shouldn't happen.
Post - II
>>> system was initially configured with level 5. Level was changed (from 5) to 2, but draft flows still cannot be executed.
Draft enabled flows should get execute as the product level is 2: development
so it might be either a cache or a timing issue for system to learn the setting.
sorry to ask: can we confirm the value from SMA too? [Production Level 2 (Development)]
Accepted Solution
it.ru
RU
Solution found.
truncate table pr_assembledclasses helps.
thanks!
Highmark Health
IN
Have made DSS as 5 in fieldtypechange/productionlevel even after restart the pzProductionLevel is still showing 2 any idea why?
sberbank
RU
Hello. In Developer portal : Records - > Administration -> System.