# RecordPolicyActionType (Complex Type)

### Namespace: http://midpoint.evolveum.com/xml/ns/public/common/common-3

Supertype: PolicyActionType
TODO

Item Summary
Name | Type | Multiplicity | Description
--- | --- | --- | ---
name | property string | [0,1] | Name for the action.
description | property string | [0,1] | Free-form description (e.
documentation | property string | [0,1] | Technical documentation for a particular object or construct.
condition | property ExpressionType | [0,1] | When should this action be applied? Not supported for policy rules targeted at activities.
policyRules | property TriggeredPolicyRulesStorageStrategyType | [0,1] | How much information about triggered policy rules should be stored? EXPERIMENTAL

- ### Items

  - #### name

    Flags: RAM,runtime

    Multiplicity: [0,1]

    Display order:

    Name for the action. It is used for logging and other diagnostic purposes.

  - #### description

    Flags: RAM,runtime

    Multiplicity: [0,1]

    Display order:

    Free-form description (e.g. comments about the action purpose)

  - #### documentation

    Flags: RAM,runtime

    Multiplicity: [0,1]

    Display order:

    Technical documentation for a particular object or construct.

    The purpose of this element is to document system configuration and behavior. The documentation will not be presented to end users. In fact, it will probably not be presented at all in midPoint user interface. This documentation element is supposed to be a part of the technical documentation of midPoint deployment. The tools than generate deployment configuration will look for these elements and combine them to compiled documentation document.

    AsciiDoc formatting is assumed for this element. Any leading or trailing whitespace is skipped. Indentation equivalent to he indentation of the first non-blank line of text is also skipped.

  - #### condition

    Flags: RAM,runtime

    Multiplicity: [0,1]

    Display order:

    When should this action be applied? Not supported for policy rules targeted at activities. (TODO specify more precisely)

  - #### policyRules

    Flags: RAM,runtime,AVals:3

    Multiplicity: [0,1]

    Display order:

    How much information about triggered policy rules should be stored? EXPERIMENTAL