Cannot get MembershipAddWorkflow and MembershipLocked rules to work about mare HOT 6 CLOSED

What are you trying to do with the first rules? You have no transforms or similar. Should be just direct flows?

What does the debug log tell you?

from mare.

Direct flows aren't used because a default value is needed (hence ActionOnNullSource and DefaultValue), and direct flow does not support flow from AD string attribute to metaverse boolean attribute. Transformation isn't necessary when a value is present.

In regards to the debug log, I'll get back to you later.

from mare.

In regards to the debug log. For AD groups that have no value in extensionAttribute1 and extensionAttribute2, the MembershipAddWorkflow and MembershipLocked rules are not triggered at all. There is not a single mention of either rule in the log for such groups.

If I manually set a value to extensionAttribute1 and extensionAttribute2 for an AD group, then the rules are triggered and the values do appear in metaverse.

So in essence, on null source value the rule is skipped. To me, this seems like a bug considering this is the exact scenario ActionOnNullSource and DefaultValue is for, right?

from mare.

The fact that no rule is triggered may be a FIM/MIM thing and not a MARE issue. I've seen this happen for nulls values where Advanced Flow Rules are not triggered when the attributes that it depends on doesnt have value. Try adding the "object-id" as a dependency for the flow rule along with the other attributes. That should trigger the rule.

from mare.

Try adding the as a dependency

I think you lost a word there. :) But yes, including another attribute as data source in addition to extensionAttribute1/2 solved the problem. Thank you.

from mare.

Great. Glad it helped. Please close the issue if solved.

from mare.