PG
We use the reports to extract filter information regularly and pull them into PowerBI to get an overview. However, we are running into a problem with our slowly growing set of allowed model and object types: for content governance and quality management purposes, enabling dashboards and search filtering, we want to ensure we can trace where each model and object definition in our database shared across the organization belongs, and have added custom attributes updated via a report script for models, for now. Adding attributes is easy; while relating them to our current set of 34 filter enabled models (and then allowing them in the filter) was a bit tedious, but doable. However, doing the same manually for the ~74 object types permitted by the filter is of course also doable, if even more tedious. Then we'll have to remember to do the same for any new model types, or any new object types enabled by the filter.
I believe the ArisConfiguration report class permits some level of read/write access to the method: but I only find the ability to change names there; whereas the ConfigurationAccessFilter report class does seem to allow you to enable attributes as long as they are supported in the method; therefore, maybe only the filter part can actually be automated? Then we'll probably should fall back to a verification step (using PowerBI or perhaps a method/filter oriented dashboard) to validate that what we view as mandatory attributes have been implemented across the current filter.
Is there anyone who has done something similar or have tips for dealing with the metamodel and filter?
Filter:
- the best is to have a convention database, model the changes and generate the filter (you can use attribute wizard to populate attributes or simple custom script)
- for validation you can use out of the box report: Output filter information
Method:
ARIS Connect - Administration - Configuration - Conventions - you can open an attribute and assign it to models and objects rathern than do it the old way for each object / model.
The convention database doesn't address my problem. Yes, we use filter reports to track version history and analyze method/filter in PowerBI; but that does not permit any modification. We can use it to identify deviations, of course, but that's rather indirect.
What I want is to create a report to automatically go through and ensure a certain set of basic attributes are enabled on all filter enabled model types (and, by extension, on classes of object/symbol types), so we don't have to do it manually.
However, the newer Connect configuration does help reduce the pain somewhat, but it still needs to be done manually whenever a new model or object type is added: I'd like both to cut the tedium and the error rate.
