Is there an order of precendence for Property Patterns?
If I set a property pattern at a level lower than another property pattern is set what happens?
Will one work and the other won't?
Hello,
No.
Nothing will change.
There can be multiple Property Patterns effective for an object and they will all work. However, in Adaxes 2019.2 and older, if there are multiple Property Patterns effective for an object and specifying a constraint for the same property, neither of the patterns will work, but only for the particular property. In Adaxes 2020.1, this happens only if the very same options (e.g. Default value) are set in the constraints. If Property Patterns have different options (e.g. Property is required in one pattern and Default value in another one) in a constraint for a property, both will work.
Hi team, I would like to update allowed values of a property pattern and found this script: https://www.adaxes.com/script-repository/add-new-allowed-property-value-to-a- ... multiple new values? I tried already a foreach around it, but not working properly :/
I'm troubleshooting a weird issue with the "Create User" form and the business rules behind it. The error that's being returned is that the "Company" property doesn't ... a hard time understanding why this one value would fail. Thoughts? Thank you, -Todd
Hello, We encoutered an issue with Adaxes in default configuration. We are mainly using Adaxes for its REST API, to automate identity lifecycle with our HRIS. We tried to update ... got enforced even on an API REST attribute change? If so how to disable it?
How can I check or run reports on an entire Property Pattern to ensure integrity? I know I can run a check on an individual property, but this is really inefficient since I have already defined a Property Pattern for a specific object to abide by.
Hello, I am trying to create a custom command that handles the process of converting a user account for a temp to a FTE. This needs to: 1. move the user to a new OU. 2. change ... to "xxx" OU Set 2: Always --Modify the user: set employee type to...... etc.