# AccessCertificationStageDefinitionType (Complex Type)

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

Definition of an access certification campaign stage.

Item Summary
Name | Type | Multiplicity | Description
--- | --- | --- | ---
number | property int | [1,1] | Stages are numbered from 1 onwards.
name | property string | [0,1] | Stage name.
description | property string | [0,1] | Stage description.
documentation | property string | [0,1] | Technical documentation for a particular object or construct.
duration | property duration | [0,1] | How long should the stage last?
deadlineRounding | property DeadlineRoundingType | [0,1] | How to round the deadline (if at all)? The default is to 23:59:59 of the computed day.
notifyBeforeDeadline | property duration | [0,-1] | How long before the end of stage should notifications be sent? (Multiple values can be put here.
notifyOnlyWhenNoDecision | property boolean | [0,1] | Send notifications only to people that have not decided yet.
reviewerSpecification | container AccessCertificationReviewerSpecificationType | [0,1] | TODO
outcomeStrategy | property AccessCertificationCaseOutcomeStrategyType | [0,1] | How to determine outcome of the approval process (e.
outcomeIfNoReviewers | property AccessCertificationResponseType | [0,1] | What is the outcome if no reviewers are available? (This is not the same situation as if some reviewers were computed but none of them responded!)
stopReviewOn | property AccessCertificationResponseType | [0,-1] | What decisions stop the case from advancing to the next stage? If neither stopReviewOn nor advanceToNextStageOn is used, a default (defined at the campaign level) is used.
advanceToNextStageOn | property AccessCertificationResponseType | [0,-1] | What decisions make the case to advance to the next stage? If neither stopReviewOn nor advanceToNextStageOn is used, a default (defined at the campaign level) is used.
timedActions | container WorkItemTimedActionsType | [0,-1] | What actions are to be applied to work items when given timer(s) occur.

- ### Items

  - #### number

    Flags: RAM,runtime

    Multiplicity: [1,1]

    Display order:

    Stages are numbered from 1 onwards.

  - #### name

    Flags: RAM,runtime

    Multiplicity: [0,1]

    Display order:

    Stage name.

  - #### description

    Flags: RAM,runtime

    Multiplicity: [0,1]

    Display order:

    Stage description.

  - #### 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.

  - #### duration

    Flags: RAM,runtime

    Multiplicity: [0,1]

    Display order:

    How long should the stage last?

  - #### deadlineRounding

    Flags: RAM,runtime,AVals:3

    Multiplicity: [0,1]

    Display order:

    How to round the deadline (if at all)? The default is to 23:59:59 of the computed day.

  - #### notifyBeforeDeadline

    Flags: RAM,runtime

    Multiplicity: [0,-1]

    Display order:

    How long before the end of stage should notifications be sent? (Multiple values can be put here.)

  - #### notifyOnlyWhenNoDecision

    Flags: RAM,runtime

    Multiplicity: [0,1]

    Display order:

    Send notifications only to people that have not decided yet.

  - #### reviewerSpecification

    Flags: RAM,runtime

    Multiplicity: [0,1]

    Display order:

    TODO

  - #### outcomeStrategy

    Flags: RAM,runtime,AVals:4

    Multiplicity: [0,1]

    Display order:

    How to determine outcome of the approval process (e.g. if multiple reviewers are present)? Default is oneAcceptAccepts.

  - #### outcomeIfNoReviewers

    Flags: RAM,runtime,AVals:6

    Multiplicity: [0,1]

    Display order:

    What is the outcome if no reviewers are available? (This is not the same situation as if some reviewers were computed but none of them responded!)

  - #### stopReviewOn

    Flags: RAM,runtime,AVals:6

    Multiplicity: [0,-1]

    Display order:

    What decisions stop the case from advancing to the next stage? If neither stopReviewOn nor advanceToNextStageOn is used, a default (defined at the campaign level) is used.

  - #### advanceToNextStageOn

    Flags: RAM,runtime,AVals:6

    Multiplicity: [0,-1]

    Display order:

    What decisions make the case to advance to the next stage? If neither stopReviewOn nor advanceToNextStageOn is used, a default (defined at the campaign level) is used.

  - #### timedActions

    Flags: RAM,runtime

    Multiplicity: [0,-1]

    Display order:

    What actions are to be applied to work items when given timer(s) occur. EXPERIMENTAL