Mon, 2020-05-25 10:00
I am currently an administrator of ARIS 7.1 and I am finding that one of the common errors when users are modellling relates to them not completing the mandatory fields on certain objects. Is there a way of configuring ARIS to make these mandatory attributes (defined by us) more clear to modellers?
Tags: script
You can use macro for this.
Setup a custom macro on <close model > or <save model> events and check for the relevant attributes that are mandatory.
Hello
I have taken a look in the Evaluation area where I can see the macros that have been set up under Automation for 'Model Saved' and 'Model Closed'. I cannot however see where I can define the attributes. Am I looking in the right area?
Usually the task of checking attributes is done interactively by means of semantic checks.
In the admin module of ABArchitect > Evaluation you will find pre-defined rule types and profiles (groups of selected rules). As an example there is a profile "Mandatory semantic checks" (pls see its description) that can be executed by a corresponding macro in the category "Automation".
So if the pre-defined rules for checking model or object attributes suit your purpose, create your own profile and call this profile from your own macro.
For more specific semantic checks rules you would need to write your own scripts, for a source of inspiration see here
Could you please explain more, what attributes (specify attribute group, attribute name) you want to make mandatory? Give atleast one example for your scenario.
I think her problem is a bit different. She wants to automate this task that NO ONE SHOULD BE ALLOWED to leave "mandatory attributes" empty. If someone leaves them blank then ARIS should cry and not let them save the model.
Yes this is correct Adnan that is exactly what I want to do
Randeep,
Given the process of process modeling I would proceed cautiously with this approach. There are many times where modelers go in and do quick modeling and don't populate the attributes. I would be afraid to implement this in any organization where you want to encourage the use of ARIS as a friendly tool. I do not know what the lifecycle for model/object creation until first release is for your organization, everywhere I have seen can have 3 months to over 1 year. As many of the attributes are not necessary prior to publication we cannot expect them to be updated at creation (if this were implemented I for one would just put in dummy data, which I feel is probably worse than no info)
A solution we have implemented successfully is to create a report that brings up a form for attribute data entry. If attribute is populated the info is there, if no data then it is blank. This makes it easy for users to see all mandatory attributes on one simple to use screen. Our version even reads from an excel file where we keep some elements which have formatting constraints. When the user leaves this report it indicates any mandatory attributes which have not been populated.
I recognize this did not answer your question, but I would really ask "What are you trying to accomplish?" What is the issue that is making this a problem you want to solve? Models and objects in the db without attributes populated? Is that an issue, if so why?
rgds
donald
Helllo Donald
I agree, we do not want to make it more difficult too model.
The idea is that prior to submitting models for review, which as you say may be weeks/months after first creation, the modellers have an easy self-check to make sure any new objects will pass the review (which requires mandatory fields prior to promotion to production). If this can be accomplished easily bby e.g colour coding some of the attribute fields, then that would be ideal.
Do check this post....
Initially, i developed script to change the color of objects that do not meet the criteria but found it too obtrusive......
http://www.ariscommunity.com/users/sadnan/2010-07-28-macro-validation-mandatory-attributes