Why can't we run a Draft Flow in PROD is there any Logic behind from Pega?
Why can't we run a Draft Flow in PROD is there any Logic written in Pega (any DSS) ?
***Updated by moderator: Lochan to add Categories***
**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.
Accepted Solution
Pegasystems Inc.
IN
You are correct pyDraftModeON will not impact Rule availability in anyway and they are completely different.
As for point 2, flow rule never gets discarded in rule resolution based on draft mode On property. It gets picked but execution will be skipped. We have added that logic in flow fua.
Below is the snapshot of the code to help understanding the logic.
Let us know if this helps :)
Pegasystems Inc.
US
Draft mode is only used in lower environments because it allows you to run flows for testing purposes before all of the rules are in place. For example, I can save and run a flow in a development environment before I have finished creating all of the flow actions. In a Production environment, all of the rules need to be in place so the work objects can be processed completely.
Cognizant
IN
Thank you for the quick response. I agreed on the statement that all the rules (i.e Flow action) has to be in Place before sending the Flow to PROD. but just curious to know why it is only not working where PROD level is 5. Is there any System Settings or DSS Pega is currently using for this check ?
Pegasystems Inc.
US
It is not configurable via a system setting or DSS. I see references in the flowMethodBody function that builds the code that reference production level 5.
Cognizant
IN
Guys I am still waiting for the answer, could you please help.
just curious to know why it is only not working where PROD level is 5. Is there any System Settings or DSS Pega is currently using for this check ?
Virtusa
AU
Hi Rakesh,
The property pyDraftModeON is true for flows with Draft mode on. Considering that the production level 5, indicates a production system, with highest security and the system is not allowed to have any kind of experimental flows. The property pzProductionLevel in the pxProcess System Page, holds the production level of the instance.
During rule resolution, as per the step number 3 ( https://docs-previous.pega.com/overview-rule-resolution )
3. Discard rules where Availability = No/Draft
Draft mode rules are discarded for production instances.
Hope this helps.
Regards,
Madhuri
Cognizant
IN
Hi Madhuri,
Thanks for your reply. I have few more doubts which is listed below.
1. Once we set flow in draft mode the Property pyDraftModeON will became true but how the pyRuleAvialable property will get impact ? Ideally Draft Mode on is different than Rule in Draft Mode.
2. If in Rule resolution the Flow rule is getting discarded then it should also get discard for PROD level 4 or 3 as well, but its working fine for PROD level 1-4 but not working for 5.
Accepted Solution
Pegasystems Inc.
IN
You are correct pyDraftModeON will not impact Rule availability in anyway and they are completely different.
As for point 2, flow rule never gets discarded in rule resolution based on draft mode On property. It gets picked but execution will be skipped. We have added that logic in flow fua.
Below is the snapshot of the code to help understanding the logic.
Let us know if this helps :)
