Within the Rules Engine, the existing Approvals Consumer enabled granular structures around Inbox/Outbox approvals within the ActiveControl workflow, based around assignment to User Roles within the Windows GUI configuration. Test Queue signoffs within ActiveControl have always been different to Inbox/Outbox approvals, in the sense that the assignment of Testers is done at an individual Business Task level, rather than as a configuration activity performed via authorised Administrators.

Over the years, many Basis Technologies customers have highlighted that the assignment of Testers to Business Tasks was often a highly repetitive exercise, since it was generally always the same people performing certain testing within their organisation. For example, many customers have dedicated Testers in particular systems (eg Regression Test Team) or specific Testers that perform the validation on particular types of changes (eg Finance Testers, Supply Chain Testers etc).

As such, ActiveControl 8.50 introduces a new Testing Consumer (via new configuration table /BTI/TE_RE_TSTER) as part of the Rules Engine, to help automate the assignment of Testers. At the time of saving a Business Task (either a brand new Business Task, or one that has recently been changed), the Testing consumer will process any rule conditions that have been setup, and automatically assign Testers based on them being part of the corresponding User Roles within ActiveControl.

Figure: New /BTI/TE_RE_TSTER consumer table as part of the Rules Engine.

Configuration Steps

More information on the Tester Consumer can be found in this online Change Note.

Some example configuration can be found in seperate Knowledge Articles:

(i) Assign specific Testers to all Business Tasks.
(ii) Assign specific Testers based on specific Business Task [Group].
(iii) Assign Testers to all Business Tasks based on an ActiveControl Project user role assignment.

p(banner important). Please note that the Tester consumer only covers the assignment of Testers, but NOT the removal of Testers as well. If a Tester is removed from a User Role, they will not be automatically removed as Testers from any Business Tasks that they were previously automatically added to due to being assigned to the User Role. Removing a Tester from a Business Task needs to be done manually, either within individual Business Tasks or by using the backend utility report /BTI/TE_RMASS_TESTERS.


Was this helpful?

Yes No
You indicated this topic was not helpful to you ...
Could you please leave a comment telling us why? Thank you!
Thanks for your feedback.

Post your comment on this topic.

Post Comment