Resource wizard: Object type policies

Last modified 21 Jan 2025 16:24 +01:00

Since 4.9

This functionality is available since version 4.9.

Table of Contents

Configuration of resource wizard panels
How to Use Lifecycle States

Object type policies define default behavior of midPoint based on the concept of object marks. Automatic marking rules and default operation policy can be defined.

Figure 1. Object type policies

Default operation policy defines behavior for operations if the object marks are not explicitly specified. For example, you may need to set the Default operation policy as Unmanaged to make all objects of the object type effectively read-only (outbound behavior will be ignored) during object management migration to midPoint.

Default operation policy is heavily used in Methodology: Group Synchronization

Figure 2. Configuration of default operation policies

Click btn:[Save policies] when done to return to the previous page from which you started the default operation policies editor.

Marking configuration allows to define automatic rules for object marking. Specify mark and its application time and optionally a filter to denote objects which should be marked. Objects will be marked either always - whenever they are processed or at the classification time - when the object is classified by midPoint for the first time.

Figure 3. Configuration of marking

Click btn:[Save marking rules] when done to return to the previous page from which you started the marking editor.

Configuration of resource wizard panels

Some wizard panels are configurable, for more information see Wizard panels.

How to Use Lifecycle States

You can use different lifecycle states for resources, object types, attributes, mappings, synchronization situations, and other aspects of resource configuration. You can use the lifecycle state property for simulations. Resources are created in the Proposed lifecycle state by default, and don’t work in normal deployment before switching the state to Active.

You can use the Proposed lifecycle state to test (simulate) the configuration without causing any damage to your target system data. When the simulation results are satisfactory, you can switch the lifecycle state to Active.

You can set different lifecycle states for various configuration items, which lets you put specific parts of configuration to production incrementally.

For example, after you switch your resource to the Active lifecycle state, you can add new mappings in Proposed lifecycle state first. You can simulate the new mapping safely and switch it to Active when it’s ready.