How to move Metric Definition Properties (Method,Schedule,Owner,Approval) down to Metric Level

[ChuanYanF]

Dear experts, 

I am facing a problem where my clients want to be able to define the Metric Properties, Method, Schedule, Data Classification and Approval at the Metrics Level, rather than the Metric Definition Level which the system is practicing currently. Is there a way I can approach this matter? Where I can define all these only when creating a metric?

[Vaisakh Krishna]

Hi,

You can define the data owner and approver at the metric level, but not the other fields. You can also update the Reporting classification field at the Metric level.

What are the use cases that your clients are looking for which requires these fields (other than the ones you can already do which I mentioend above) to be updated on the Metric level?

-Vaisakh

[ChuanYanF]

Hi Vaisakh,

Thanks for your reply, so actually what we are dealing with our client right now is to integrate metrics function into their risk management process, so we decided that we will use the metric definition as a process for all the department in my client's risk management. But for their process across each departments have different data collection method and the frequency and precision. So they wanted to define every tabs below of the metric definition in metrics since a metric definition is mandatory while creating a metric and we cannot just create metric from scratch at the metric level. Currently for my client, the entity is refering to their department

[Di Zhang]

Actually Risk Management provide Risk Indicator for it. 

[Ash70]

Hi Vaisakh

This has not been our experience. If you update the data owner you get the following message on Save:

Data Policy Exception: The following fields are mandatory: Metric definition

Invalid value on Update

We are very keen to know if it is expected behaviour that you can update the data owner on a metric to be different to that of the Metric Definition?