ARIS - SHARE YOUR IDEAS
Use case is for a customer that has only the basic ARCM roll out and issues from Connect. Their users are creating issues but some issues needs to be removed/not visible and it is complicated to deactivate issues once they are already created and in the owner inbox. The admin user receives request to delete some of them and it is complicated to do it in bulk as there are always conditions not met to deactivate. I would be interesting for an admin user to be able to delete them. Also when it is a test issue, it is polluting the data.
I support this request and would like to expand it by the following: Please also provide more "deactivation" capabilities to admin users for other objects/workflows:
Deactivate control tests, not only in status "new/open" but also in various "finished" status, within (pre-defined, temporary) limits; or ensuring the legitimation of the deactivation by a reviewer loop, with comment, to keep it auditable. Use case: In rare cases, the tester is making a mistake, or may be subsequently convinced that the test result should be corrected. In these cases it may be helpful to deactivate the control test and add a new control test with revised result. Alternatively, it would help to send all control tests through a review loop (not only "ineffective"), and automatically close the review loop as "accepted" if the reviewer does not react within x days (x to be defined in the system preferences).
Deactivate control executions, similar to the above. Currently, it is only possible to deactivate in status "new".
Add comment to deactivation. When deactivating an object, the user is currently asked if he/she is sure. In this step it should be mandatory to add a comment. This could help in case of future audits or other investigation.
Of course, all deactivation activities must be properly logged and reported (which is already implemented). In my oppinion, a comment of the user deactivating the object must be added in any case (mandatory).
We are on the way to bring more capabilities into portal, managerial tasks (also for issue management) are still in the backlog list.