Importance of Sandbox ruleset::
One of the major problems that Pega projects face with time is build up of test rules within the official business rulesets. If not properly managed these rules could end up in the production environment which is not an ideal situation to have. But can we really stop creating test rules, for me the answer is no, because creating test rules is also an integral part of the iterative development process. So how can we maintain a clean development environment while also allowing the creation of test rules.
The answer is the Sandbox ruleset. By creating a separate ruleset only for test rules it is possible to have a clean development environment while allowing the creation of test rules in development process.
Following are the steps that have to be followed:
Create a sandbox ruleset and version
Update ruleset restrictions in classes to include the sandbox ruleset
Create a separate sandbox application rule and include the sandbox ruleset and put your main application as the Built on Application
Create a sandbox access group and include the sandbox application
Include the sandbox access group as an optional entry in the operator access group list
Now you will get the sandbox application as an optional application rule when you log in as a developer. So next time when you want to create a test rule, switch the application to the sandbox application and use the sandbox rule set to save your test rule.
If your team is not used to this process, it will take some time for them to adjust to this new way of working, but with time you will see better results.
One of the major problems that Pega projects face with time is build up of test rules within the official business rulesets. If not properly managed these rules could end up in the production environment which is not an ideal situation to have. But can we really stop creating test rules, for me the answer is no, because creating test rules is also an integral part of the iterative development process. So how can we maintain a clean development environment while also allowing the creation of test rules.
The answer is the Sandbox ruleset. By creating a separate ruleset only for test rules it is possible to have a clean development environment while allowing the creation of test rules in development process.
Following are the steps that have to be followed:
Create a sandbox ruleset and version
Update ruleset restrictions in classes to include the sandbox ruleset
Create a separate sandbox application rule and include the sandbox ruleset and put your main application as the Built on Application
Create a sandbox access group and include the sandbox application
Include the sandbox access group as an optional entry in the operator access group list
Now you will get the sandbox application as an optional application rule when you log in as a developer. So next time when you want to create a test rule, switch the application to the sandbox application and use the sandbox rule set to save your test rule.
If your team is not used to this process, it will take some time for them to adjust to this new way of working, but with time you will see better results.
well explained. Keep updating
ReplyDeletepega online training bangalore