Has anyone found an easy way to make "Go up in hierarchy" work correctly? (In ARIS Connect viewer)
This is needed for navigation, when it can be easier to go up to the parent model and then down to a different sub-process, rather than clicking back a few dozen times to get back to the parent model. But it doesn't work ...
See screen shots below. The up arrow says "go up in hierarchy" which is what we want ... but none of the options presented, are the parent process model.
When you are using classic as configuration set, then Go up in hierachy is using the database folders are kind of hierarchy. Oly with default as active configuration set the hierarchy follows the modeled hierachy. But then there are no more folders shown in the navigation pane of the left, because ARIS is using then only linked models to build up a hierachy.
Thank you for the reply Runè ... do I understand correctly that there is no way to have folders shown in the navigation pane (which is very important for navigating through the folders) and also have "go up in hierarchy" work correctly, at the same time?
In old versions of ARIS Publisher, this "go up in hierarchy" worked based on assignments -- meaning, it would show any model where there is an occurence of an object that has an assignment to the child process. And at the same time, the folders were available for navigation. Why can't this same logic be used in the new and improved ARIS Connect?
I was hoping that this might be improved in the new release, but it still does not work.
Is there any hope of making this work?
It is an important user-friendliness feature. We are trying to deploy ARIS across a large enterprise as our process referential, and we need it to be simple and intuitive so normal people can use it with little or no training. We cannot train our entire audience on how to understand the differences between folders, objects and models; we have a hard enough job getting them to understand the basic concept of proces hierarchy.
I am not sure what you are trying to achieve. Isn't it easier for your audience to either use a group folder structure (using config set classic), or a process hierarchy (using config set default)?
It's of course worth to discuss with Software AG's Professional Services if they could enable the both within the same configuration set, but I doubt that this would then we easy to understand what navigation means.
I was told by a consultant from Professional Services that mixing both styles is possible. I suggest you contact Software AG to get an offer for implementing that configuration.
