-
Notifications
You must be signed in to change notification settings - Fork 3
Rule
Søren Granfeldt edited this page Jul 1, 2020
·
10 revisions
Each rule define an action that may be taken when a metaverse object is 'touched' or changed. You can have as many rules as you like in this framework for as many object types as you like.
A rule consists of the following elements that are required / allowed -
- Name - Contains a descriptive name for the rule. Required.
- Description - Contains a more elaborate description of what the rule does. Not required.
- Type - A value specifying whether this is a MRE rule ('Default') or an 'External' rule. If no value is specified, the default is MRE rule ('Default'). See Externals for more information on externals.
- ExternalReferenceId - A value referencing the external that is called for this rule. Only required if Type is 'External'.
- ReferenceId - A unique value for rule lookups used for reprovisioning. Not required (reserved for future use).
- TargetManagementAgentName - The name of the Management Agent (MA) that is targeted by the rule.The name must match the name of the MA as seen in the FIM Synchronization Service Manager. This value is required to have a name of an existing MA, even for DeprovisionAll.
- Enabled - This allow for a rule to be enabled or disabled selectivily without disabling provisioning for all rules as you would normally do in FIM. If set to false, the rule is not processed. Allowed value(s) are 'true' or 'false' (case-sensitive)
- SourceObject - This is the class of the metaverse object that this rule pertains to, e.g. person or group (case-sensitive)
- TargetObject - This is the class of the connector space object that this rule pertains to, e.g. user, group, computer. If this is a provisioning rule, this is also the class that would be provisioned to the connector space if conditions are met.
- TargetObjectAdditionalClasses - An optional element that allows you to define additional object classes to add to the new connector space object if supported by the target directory (LDAP servers for example). This can be a static, comma separated list of additional class names, a metaverse attribute containing the classes to add (in the format of #mv:additionalObjectClassesAttributeName#).
- Action - This is the action that MRE should perform against the objects in the connector space if the conditions are met. See details for supported actions
- RenameDnFlow - Deprecated
- Helpers - Allows you to add rule instance helpers
- ConditionalRename - Allows you to specify rename action and conditions (more below)
- Conditions - Allows you to specify conditions for for rule action to take place
- InitialFlows - Allows you to specify flow-once values for provisioning actions.