Skip to main content
Skip table of contents

Provisioning Task Post Processing

Definition

Provisioning Task Post Processing Definition configures the settings used to launch the provisioning processing task.

.

Configuration

You can access the Provisioning Task Post Processing Definition configuration :

  • by clicking on "Synchronization" → "Post-Provisioning Tasks"

  • by clicking on "System" → "Configurations"->”Synchronization Service” and perform an import/export.

Properties

Property Name

Type

Mandatory

Description

reportDefinition

-

NO

The report post processing task definition (see Provisioning Task Report Definition)

Provisioning Task Report Definition

Provisioning Task Report Definition configures the settings used to launch the report post processing task.

Property Name

Type

Mandatory

Description

errorPublicationDefinition

-

NO

The error report post processing task definition (see Provisioning Task Error Publication Definition)

reportPublicationDefinition

-

NO

The summary report post processing task definition (see Provisioning Task Report Publication Definition)

Provisioning Task Error Publication Definition

Provisioning Task Error Publication Definition configures the settings used to launch the error report post processing task.

Property Name

Type

Mandatory

Description

Values (default value in bold)

errorDetails

Enum

NO

The list of error details that will be displayed in the error report.

SHADOW_OBJECT_ID, IDM_OBJECT_ID, ERROR_STEP, ERROR_CODE, ERROR_LABEL, ERROR_DESCRIPTION

reportRelativeFilePath

String

NO

The relative path to the error report file. May be null, its default value becomes then: {original_filename}-errors-{timestamp}.

This relative path is appended to the root directory under which all report files must be located.

The root directory is defined by the configuration property: domino.sync.task-report-root-dir. When running in multi-tenancy mode, the tenant name is always appended to the root directory, such as: /{root-directory}/{tenant}.

The file path is "configurable" via placeholders whose values are dynamically substituted. Available placeholders are:

  • {original_filename}: the complete path to the original CSV file (minus the file extension)

  • {timestamp}: a timestamp of millisecond precision formatted as follows: yyyyMMddHHmmssSSS

  • {tenant}: the current tenant

The original file extension is preserved. An example of such a relative path could be: import-errors/{original_filename}-{timestamp}. In the case, the import-errors sub directory will be automatically created.

-

Error details available values

Name

Example

ERROR_STEP

IDM_REQUEST_EXECUTION

ERROR_CODE

KIT-C0100021

ERROR_LABEL

AGGREGATE_ALREADY_EXISTS

ERROR_DESCRIPTION

An Aggregate 'Identity' with id '3219' already exists!

ERROR_DETAILS

The attribute is mandatory: it must have a value!

ERROR_DATE

2018-04-01T17:17:28.298Z

ERROR_LOG_TRACKING_ID

d9c1fc9c-1af6-4440-875e-5dd81882a6ea

APP_ID

SRHM

SHADOW_KIND

ACCOUNT

SHADOW_ID

0c14aed5-1307-4078-9943-33736929b311

SHADOW_OBJECT_ID

I3245

SHADOW_OBJECT_CLASS

__ACCOUNT__

IDM_OBJECT_KIND

IDENTITY

IDM_OBJECT_ID

P324734

IDM_OBJECT_TYPE

employee

A default "standard" error formatting is applied if none is explicitly configured.

Provisioning Task Report Publication Definition

Provisioning Task Report Publication Definition configures the settings used to launch the summary report post processing task.

Properties

Property Name

Type

Mandatory

Description

Values

reportActors

-

NO

The set of the report notification actors.
Their 'role' attribute must correspond to those expected by DOMINO_SYNC_REPORT_PUBLICATION Notification Event Type.
If defined, it overrides the default recipients configured in the "global Settings"

Available 'role' are :

  • domino_task_report_sender

  • domino_task_report_replyto

  • domino_task_report_recipient

If configured with Global Settings, their corresponding keys are :

  • domino.task.report.sender

  • domino.task.report.replyto

  • domino.task.report.recipient

XML
<reportActors>
  <reportActor>
      <email>administrator@memority.com</email>
      <language>en</language>
      <role>domino_task_report_recipient</role>
   </reportActor>
</reportActors>

attachErrorReport

Boolean

NO

Whether the error report is attached or not to the summary.

true,false

Example

Here is a simple XML representation of a Provisioning Task Post Processing Definition.

Provisioning Task Post Processing Definition
XML
<dmn:ProvisioningTaskPostProcessingDefinition id="postProcessingTask">
    <name>postProcessingTask</name>
    <description>Description of postProcessingTask</description>
    <reportDefinition>
        <errorPublicationDefinition>
            <errorDetails>
                <errorDetail>ERROR_CODE</errorDetail>
                <errorDetail>ERROR_LABEL</errorDetail>
            </errorDetails>
            <reportFilePath>{original_directory}/{original_filename}-errors-{timestamp}</reportFilePath>
        </errorPublicationDefinition>
        <reportPublicationDefinition>
            <attachErrorReport>true</attachErrorReport>
       <notificationDefinitionIds>
                <notificationDefinitionId>report_publication_test</notificationDefinitionId>
        </notificationDefinitionIds>
            <reportActors>
                <reportActor>
                    <email>tenant_administrator@memority.com</email>
                    <language>en</language>
                    <role>domino_task_report_recipient</role>
                </reportActor>
            </reportActors>
        </reportPublicationDefinition>
    </reportDefinition>
</ProvisioningTaskPostProcessingDefinition>

Read Next

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.