Does numerical attribute precedence in MV designer override rules in extension DLL if manual precedence is NOT checked? RRS feed

  • Question

  • Hello all,

    I was doing some reading but I wanted to double check on something. I'm looking at an implementation that has a bunch of logic in the C# extension DLL for import/export flow rules but also has numerical precedence defined in the VM designer for Person > {field name}. In that UI manual precedence is NEVER checked, for any of these attributes.

    Will this mean then that numerical precedence always wins regardless of what the code chose?

    Wednesday, April 17, 2019 3:35 PM

All replies

  • How the attribute is populated in metaverse (c#- advanced flow rules, or direct), where the precedence takes place, is of little relevance. Once it is there the order of precendence (numerical value) plays the role.

    MA with the lowest number, or higher on the UI has higher precedence.

    Nosh Mernacaj, Identity Management Specialist

    Saturday, April 20, 2019 8:27 PM