In my current application we are going for prod deployment with both DSS and Toggle ,we have a DSS called EnableOpenBanking=false already being called from an activities precondition then why are we going with toggle as well, my lead said this is the practice we follow, however can someone please explain?
Pega Toggles are used to enable or disable features dynamically in an application without changing the core rule behavior.
Toggles can be used
Gradual rollout of a feature (initially the feature is available for limited users using Toggle)
Quick rollback if a new feature causes issues
Testing new functionality without removing code
Separating old and new behavior cleanly
DSS:
Externalized configuration values
Environment-specific settings
Parameters that are not really “feature flags”
1 Like
Not to confuse matters, but there is also Configuration Sets (released 8.8?) which are commonly used in our apps. I like these because:
- Design time: Can be configured directly into case design and rules (e.g. when rules)
- Run time: Can be “delegated” to business users in a much nicer way than a DSS or toggle.
- Features: These are data instances, that can be managed per environment and also managed at an individual case or application level.
https://docs.pega.com/bundle/platform/page/platform/app-dev/creating-configuration-set.html
You’ll commonly see these in Platform and Pega Customer Service features in place of what we would of used DSS’s for in the past.
Hi @RameshSangili however even DSS can be used right for rollback so I cant see any other difference apart from the fact that in Toggles we can provide access to specific users/operator ID.
Toggles can restrict access to the new functionality to only a subset of users, whereas DSS can be used only in an all-or-nothing way—either all users get access, or none do.
1 Like