Model Connected to Itself

Hi,

As I can see from your screen your opened model 'Data warehouse...' has two superior models, it could happen when two superior models have the same occurence that goes (has assignment) to the same model. E.g., you have a model variant for "EI landscape...". It is not a good case (some reports could work incorrectly), but it seems it is not a system issue, but modeling/user.
 

If I'm not right, then more information is required (first,  I'd check the models' folders to undertend if those models are copies or not). 

Thanks for the reply. Further information. We don't use Variants, and I confirmed that neither of the EI Landscape Models mistakenly have had a Variant created. Both the EI Landscape Models are valid in that 1 is our Baseline (locked down) Model and 1 is a Working Copy where a User is making changes to then be promoted to the Baseline. Each of the EI Landscape Models have a valid Assignment on a Relationship in the Model that points to the DWR Interface Model which again is correct and reflected properly in the Connected Models listing of the DWR Interface Model details.

So, that all looks good. It is still that I cannot determine why or how the DWR Interface Model shows itself as a Connected Model (circular reference).

Anyway, thanks again for the reply. I will keep watching the post for a few more days before opening a support ticket. If it goes that far once I get a reason why and a solution, I will post that here for everyone to see. 

Hi Michael,

I am exclusively modelling with the Browser interface (Cloud or Connect). From my point of view without knowing the internal implementation details of the tools, the browser interface does know connected models only based on variants. Having no variants "Connections" are between objects and "Assignments" are between object and model. In ARIS Architect&Designer indeed I see in the property "connected models" of model X  the model Y when model X is called via an object of model Y (that's the assignment in the browser interface). Then I could produce a loop calling X fom Y and vice versa (does not make sense for sure in process modeling). If this is not the case in your environment may it's a bug. 

Interesting here, that the ongoing transfer from desktop to browser interface brings functional changes which are not actively communicated by ARIS (SAG).

Regards

Klemens

Thanks for the reply Klemens. Yes, I definitely can see where you can purposefully set up a "circular reference" via the Assignments, but that is why the situation in our case as you say seems like it might be some kind of bug as we don't have any Assignments (or Variants) in relation to the Models where I do see the circular references.

The other think being that if you purposefully set up the circular reference, you can undo it as well. I don't see any way that I can "undo" the circular references that I am seeing.

Again, thanks for the reply. Likely time for me to create a SAG ticket. I will definitely post any further information here.

I found it!!!

I went into the Models that had the "circular references", and I clicked on every Object and Connection/Relationship and looked to see if there was an Assignment on them, even though there was NO Assignment Icon/Widget showing on the Model. This is actually how I found that there were "Real" Assignments on some Connections/Relationships that pointed to the Same Model (i.e. the circular reference). In the Client or in Connect I was then able to Delete the Assignment and the Circular Reference was fixed/gone.

So, I was able to correct things, but IMHO there is still a bug, and the Assignment Icon/Widget does NOT get Displayed in this type of situation.

Thanks for all the help.

So, I was able to correct things, but IMHO there is still a bug, and the Assignment Icon/Widget does NOT get Displayed in this type of situation.

I tested it, and indeed I can reproduce this behaviour. In the case of an assignment of an object to it's own model the assignment icon is not displayed but the assignment exists technically. That's bug no. one, and that such an assignment is possible at all (should not) is bug no. two.

Klemens

I put together a report to see if we had any other Circular Connected/Assigned Models in our Database and I have attached it here on the chance that it may be helpful to other Aris Community Members.

I haven't done extensive testing, but the report seems to work well enough. Enjoy!!

FYI

Well, it looks like SAG doesn't agree that there is a bug. I replied that I still don't see a Use Case for a Model Connected/Assigned to Itself, but SAG seems to think there is a case even though I could not really pick it out from their explanation.

Below is the SAG response to my Ticket (SI-579662 No Assignment Icon/Widget on Relationship/Connection):

The more detailed description of an object, e. g. the details of a function object can be described in a Function allocation diagram. In this case the model assigned to the object is always contained as central object in the allocation diagram. This allows e. g. 'lean EPCs', and it is relevant in context of the content type configuration (Default set).

Another type is the description of an object on the next level, e.g. a function can be assigned with an EPC model. In this case, there are assignment relationships of the 'is process-oriented superior' connection type from the function object to all functions occurring in the assigned EPC.

Those connections are 'calculated' based only on the assignment (no connection definitions, report functionality can evaluate these connections). The model generation functionality (ARIS Architect) can be used to create a function tree. The functionality creates the connection definitions and their connection occurrences in the function tree.

An assigned model that contains a description on the next lower level should not contain an occurrence of the object to avoid cycles based on the possible assignment relationships.

An overview on the assignment relationships defined for objects in an assigned model can be found in the help, e.g. ARIS Help (connections between Location and organizational elements in an assigned Org chart).

There is a mechanism in ARIS that inserts an occurrence of the object into an assigned model if it is useful. The Excel file attached (Overview on insert flag.xlsx) to the issue gives an overview on these object/model type combinations.

Regarding the 'transmits data to' connection and its assignments:

The Application collaboration diagram can be used in two ways, as overview model to show in a lean way the data exchange between systems and as interface description of such a data transfer (containing data, interface objects and protocols). In the second case it is necessary to have both systems in the assigned model.  Since there can be several interfaces between two systems, the connection is not unique.

There is no bug. Assignment possibilities and the automatic creation of occurrences in assigned diagrams (as defined in the ARIS method) are designed to make modelling easier.

Thank's Michael for forwarding SAGs answer to your bug report. I also do not understand all in detail what they are writing. I fully agree that a further more detailed model (like a FAD) should be assignable from an object. But this was not our bug request. The issue are, (1) that the SAME model can be assigned to an object and (2) WITHOUT displaying the assignment icon (so you do not see that there is a connection).

Interesting the sentence:

An assigned model that contains a description on the next lower level should not contain an occurrence of the object to avoid cycles based on the possible assignment relationships.

What means "should not"? That is, when I understand it right, exactly our point and should technically prohibited.

Regards

Klemens