Agent/service's access groups pointing to multiple applications

We have application in 7.1.9 and facing issue in supporting testing of multiple releases where each release will have different application version and for testing of both apps parallel we need to point the agent and services access group to the required application. Now we toggle as and when needed.

Ex- Application has 2 version 04.22 and 04.23 where 04.22 is for release date 1 and 04.23 is for relsase date 2
How can we handle to point the Access group of agent/services to support testing of multiple releases at a time.


Keep up to date on this post and subscribe to comments

September 13, 2019 - 3:27pm


That's a good question. I don't know of a better way to do what you are doing. Potentially, if you want to limit the testing of one version for everyone on the system, you could set the major-minor-patch version in the application definition, which would get all your agents/services, but it would also mean that you can't have some users testing version 4.22 and others test 4.23. I'm trying to think of ways to be able to work in parallel, but anything I come up with has a host of side effects/additional problems. Probably the easiest thing to do would be to create an activity or data transform or similar tool to programatically update all the rules that you want to edit, so at least you can be sure that everything is running against the same codebase.