Feature Request - Easy enable / disable of Validation Rules or Validation Rule collections

Is your feature request related to a problem? Please describe.

I would like to create validation rules in Pulse to easily identify processes that contain functionality that is not available in v12 e.g. ExecuteCommand, SaveDataAll. I would also like to be able to add specific validation rules where I find a specific issue while testing V12. I am able to add these rules, but in order to only identify the processes that contain these issues I need to disable all the other validation rules individually.

Describe the solution you'd like

I would like to be able to do one of two things, or both.

1. Select the validation rules on mass, e.g. a tick box for all elements

   

2. Have collections of validation rules, so that when running the validation, either through Arc+ or Pulse, the user can select which collection of validation rules to use e.g. "v12 exceptions", "Pulse default".

Describe alternatives you've considered

Selecting the 47 default validation rules individually and disabling them.

Additional context

Using the validation rules for identifying v12 changes could become very valuable for companies that have a larger number of processes and want to migrate to v12 in the coming years. Combined with the ease of opening the processes in Arc and the changes being tracking in Pulse, being able to easily select the validation rules you want to apply could be a very useful feature.

Hi Roy,

Being able to enable/disable rules is a good enhancement, thanks for this.

Regarding validation rules for v12, we are planning to add these rules by default inside Pulse in one of the upcoming releases ##4820.

Cheers,

Vincent

Hi @vviau,

Thanks. Being able to display only the V12 issues separate to the other default validation rules would be good. Running the default validation rules often shows up lots of items, many of which aren't an issue in most models (it's good to know about them, but not big issues). Getting a list of just the v12 issues will be really beneficial.

Just to be clear, the validation rules can already be disabled, but individually rule-by-rule. This is to enable / disable in bulk.

As I think about it. It would probably be better to have a validation category if possible, like in the test hub, so that results are as expected if multiple people are using Pulse on different TM1 databases.

added documentation enhancement labels

This is a really useful suggestion, thanks @R.B ! I came here to suggest the same ;)

@vviau I'd also add it would be useful to import / export sets of validation rules. This way we can easily make collections of rules available to customers (like the v12 rules) by releasing an exported file.