ARIS - SHARE YOUR IDEAS
As system administrators, we often use the Attribute Wizard to bulk update attributes in our database. However, this results in us showing as the Last user on the models and the Last change attribute also getting updated, which is not what we want.
It would be great if there was an option in the attribute wizard for administrators to tick to update the attributes "no touch" (e.g. not update the Last user and Last change attributes).
I understand, but for some customers it is vital to even track the slightest changes, no matter who or what is changing the model. I also understand that Cameron's initial pain point is users reaching out to the CoE because the CoE is listed as the last user.
In order to pick this up, I need further information from Cameron as requested in one of my previous comments.
@Philip Hake, it is not that uncommon what Cameron describes. There are companies which have scripts running which use the last updated date for certain reports. And when that date gets updated by something as an attribute change by a CoE those reports get affected. So I certainly support this development.
Hi Cameron,
thank you for elaborating. I agree that the bulk update through CoE is a common use case. Generally hiding (not logging) who or what (even automations / reports) made changes to a model is rather uncommon. Still, I understand that it can be quite annoying the receive all the queries, although you are not responsible for the model. The issue with the queries, is that related to viewers in your portal or even designers/admins in the design client / repository?
Thanks,
Philip
Hi Philip,
As I am sure many organisations that use ARIS do, we have a CoE team that are the custodians of the our ARIS toolset. Quite often we need to bulk update attributes on our models (following the introduction of a new attribute, or a change being required to an existing attribute) - therefore the attribute wizard is very useful for this.
However, the CoE team are not the modellers on any of our models. Therefore, updating the model attributes leaves one of the CoE team as the 'Last user', which then leads to queries about the process being directed to the CoE team, rather than the appropriate modeller. It also results in the 'Last change' attribute being updated across a large number of models, which is misleading as the model content has not changed.
Thanks
Cameron
Hi Cameron,
thank you for sharing your idea. Could you elaborate on why you want to hide who changed the attributes? Looking forward to hearing from you.
Regards,
Philip