Hi, Cecilia. Sorry for not responding earlier, I was on vacation.
When I did my first steps in ARCM, it was very difficult for me to get an overall picture of how the different components like risk evaluation, control test execution and so on worked. I wasn't able to get the whole picture of who is involved in what process step. I ended up in not using ARCM because I didn't understand how the overall business process worked.
I see a similar issue with the mini workflows. First of all, the corresponding help item is under the "View content" help category, while a typical user would probably look under "Work with content".
Let's take the "Submit change request" workflow. The help page (see attached screenshot) first describes the procedure to START the workflow in an easy to consume list of clicks. So far, so good. However, the remaining part of the help page gives a very technical description of what the process does. What's missing is an easy to consume overview of the implemented process from a business point of view.
Customers report to me that they either can't find the help page or that it doesn't solve the actual problem they have to understand how the mini workflows actually work. This, in turn, leads to rejection of ARIS, as the mini workflow feature is not considered to be adequately documented.
In contrast, when ARCM added the workflow diagrams for the individual components, I (finally) was able to quickly understand the process and participating roles. I frequently use this when I demo ARCM to customers and it resonates very well. Therefore, I would find it extremely useful if the same visualization was included for the mini workflows in the ARIS Connect help files.
Hi, Cecilia. Sorry for not responding earlier, I was on vacation.
When I did my first steps in ARCM, it was very difficult for me to get an overall picture of how the different components like risk evaluation, control test execution and so on worked. I wasn't able to get the whole picture of who is involved in what process step. I ended up in not using ARCM because I didn't understand how the overall business process worked.
I see a similar issue with the mini workflows. First of all, the corresponding help item is under the "View content" help category, while a typical user would probably look under "Work with content".
Let's take the "Submit change request" workflow. The help page (see attached screenshot) first describes the procedure to START the workflow in an easy to consume list of clicks. So far, so good. However, the remaining part of the help page gives a very technical description of what the process does. What's missing is an easy to consume overview of the implemented process from a business point of view.
Customers report to me that they either can't find the help page or that it doesn't solve the actual problem they have to understand how the mini workflows actually work. This, in turn, leads to rejection of ARIS, as the mini workflow feature is not considered to be adequately documented.
In contrast, when ARCM added the workflow diagrams for the individual components, I (finally) was able to quickly understand the process and participating roles. I frequently use this when I demo ARCM to customers and it resonates very well. Therefore, I would find it extremely useful if the same visualization was included for the mini workflows in the ARIS Connect help files.
Hello Jörg, can you please give some more details ,eg why you expect this capability and what problem you want to solve with it? Thank you, Cecilia