Using Revision Labels to Manage the Rule Development Life Cycle
- All environments share a single copy of the Catalog web service and database
- Rule changes can be propagated by assigning labels to rule application revisions in irAuthor or with irSDK
- If elements are shared in development, they are also shared in QA and Production
- Multiple rule authors can edit the same rule application concurrently
- Rule changes can be hot-deployed to the Catalog web service without restarting production application
- Production application is dependent on stability of the shared Catalog web service and database
- Full rule application revision audit trail is available in each environment
Comments
0 comments
Please sign in to leave a comment.