Question
Achmea Interne Diensten NV
NL
Last activity: 28 Feb 2020 4:41 EST
How to properly migrate toggles?
We are currently using PRPC 7.3
Before this release we were using a combination of when rules and dynamic system settings in activities to toggle functionality.
This release i decided to try using the toggle manager. I created a toggle from the toggle manager landing page in designer studio and created an associated when rule. Everything seemed to work fine on DEV, but after our migration to the test environment the toggle does not appear on the toggle landing page. The generated when rule does still exist.
Do new toggles need to be made per environment? Or do they need to be placed in a ruleset that is kept unlocked across all environments? Or is this some other solution i am overlooking?
Any help would be appreciated!
Accepted Solution
Updated: 28 Feb 2020 4:41 EST
Corporation Service Company
US
Toggle is an instance of Data-Admin-Toggle class.
For migrating any data instance, it depends on how you are migrating/deploying the changes to higher environments.
1) you can always include the list of toggles with pzInsKeys to be deployed to higher environment in the Rule-Admin-Product(Product) rule. You can get the keys from the table "pr_data_toggle"
2) As you are associating a toggle with the ruleset, it can be shipped to higher environments by including the ruleset in the Product rule. need to uncheck "Exclude-Non Versioned rules"
3) If you are packaging entire application, the associated records can be selected for deployment