RK

Hi all,

I have a very big and complex EPC. There are 2 or 3 connections between objects which are very long, crossing the whole EPC. I was wondering if it is possible to use a kind of jump mark and not a "line" to display this connection? It would be much better to keep track of the big picture.

Thanks in advance,

Raiko

 

by Frank Weyand
Posted on Thu, 01/23/2014 - 17:08

Hi,

did you try to use the "relations" in the property components of the object?

If you've got an object selected, you can have a look on all connections. Find the right one, select the other object, context menu, "Go to"...

In the following example, if you choose this menu entry, the tool will select the function.

Bye,

Frank

0
by R Kutzner Author
Posted on Mon, 01/27/2014 - 12:00

In reply to by Frank Weyand

Hi Frank,

Thanks a lot for your very quick response. For modeling this is a very good solution. We do the publishing via ARIS-WebPublisher. I need this "jump-mark" instead of a direct connection within the Publisher. The user should not see the connector because it is a way long to scroll down the whole process.

Maybe you have an idea?

All the best,

Raiko

0
by M. Zschuckelt
Posted on Mon, 01/27/2014 - 15:41

Hi Raiko,

just an idea: Make an occurrence copy of the object you are targeting with your "long" connection and place it next to the object, where the connection originates. This would be your jump mark.

A user could select that, go to the occurrences tab, select the other occurrence in the same model and use "go to".

However I admit this is not a very nice solution, since your target object is likely to be a join rule object without any self-explanatory name and from the point-of-view of a semantic check on occurrence-level the model will become invalid.

Another idea: To enhance readability of the model, stick some notes near the origin of the long connection giving a hint, what the target is (or the intention of the long loop back).

Yet another idea (not a technical solution, but a style-guide): Avoid such gigantic EPCs and split them up in smaller logical pieces interconnected using process interfaces. The human brain is incapable of holding more than 7 pieces of information in "RAM" at the same time anyway. Giving it smaller chunks of information helps gaining insight and supports the human way of memorizing things.

Regards, M. Zschuckelt

0
by R Kutzner Author
Posted on Mon, 01/27/2014 - 17:40

In reply to by M. Zschuckelt

Hi,

you are absolutely right with your last suggestion :) Unfortunately, at the moment it is difficult to change something in short term.

I like your workaround with the notes. At least, we could improve the readability a bit.

 

0

Featured achievement

Rookie
Say hello to the ARIS Community! Personalize your community experience by following forums or tags, liking a post or uploading a profile picture.
Recent Unlocks
  • Profile picture for user freddy
  • Profile picture for user mikhubb
  • Profile picture for user harryratia
  • DC
  • ВА
  • PacMan

Leaderboard

|
icon-arrow-down icon-arrow-cerulean-left icon-arrow-cerulean-right icon-arrow-down icon-arrow-left icon-arrow-right icon-arrow icon-back icon-close icon-comments icon-correct-answer icon-tick icon-download icon-facebook icon-flag icon-google-plus icon-hamburger icon-in icon-info icon-instagram icon-login-true icon-login icon-mail-notification icon-mail icon-mortarboard icon-newsletter icon-notification icon-pinterest icon-plus icon-rss icon-search icon-share icon-shield icon-snapchat icon-star icon-tutorials icon-twitter icon-universities icon-videos icon-views icon-whatsapp icon-xing icon-youtube icon-jobs icon-heart icon-heart2 aris-express bpm-glossary help-intro help-design Process_Mining_Icon help-publishing help-administration help-dashboarding help-archive help-risk icon-knowledge icon-question icon-events icon-message icon-more icon-pencil forum-icon icon-lock