Versions Compared

Old Version 1

changes.mady.by.user Josefin Klang (Deactivated)

Saved on

compared with

New Version 2

changes.mady.by.user Ann Base (Deactivated)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Minor

This article describes how to configure when to start processes on core objects in Smart ID Identity Manager. This can, for example, be used if you have made a card request for a person, then you should not be able to make another card request for the same person until the first is done.

Step-by-step instruction

Expand
titleConfigure the validator 'Dynamic Search'


Expand
titlePrerequisites

Before you can configure when to start a process, you must have defined a search configuration. Read more here: Set up search configuration in Identity Manager.

If there is a precondition for a process to start that depends on data from inside Identity Manager, and that data can be found via searches, use the 'Dynamic Search' precondition validator. The symbolic name is dynamicSearchProcessStartInterceptor.

The 'Dynamic Search' precondition validator validates the number of results that are found by a configured search. Depending on if the number matches the condition or not, the required action is triggered.

  1. In Identity Manager Admin, go to CoreTemplate (Identities, Cards,...) > State-Tabs > Additional Commands > Precondition.

  2. Configure the parameters:

    ParameterPossible valuesDescription
    SearchConfig<SearchConfig>A search configuration, whose result provides the required data needed to verify the wanted precondition.
    ResultCondition

    < lower than

    = equals

    > greater than

    The condition that is used to validate the number of the result of the search configuration.

    ResultCount <number>The number of entries that the ResultCondition validates against.
    Visibility

    isDisabled

    isEnabled

    isNotVisible

    isVisible

    Action that should be triggered if the condition if fulfilled.

    If the condition is not fulfilled, the opposite of the configured event will be executed:

    Selected conditionCondition fullfilledCondition not fullfilled
    isDisabledProcess disabledProcess enabled
    isEnabledProcess enabledProcess disabled
    isNotVisibleProcess not visibleProcess visible
    isVisibleProcess visibleProcess not visible



  3. Click Save.

Migrate old StartInterceptors

This section describes how to migrate from the old StartInterceptors to the new configuration.

Expand
titleMigrate old StartInterceptors

TypedCoreObjectRelationProcessStartInterceptor & RelatedObjectsInDefinedStateMissingProcessStartInterceptor

Functionality:

  • Checks if a relation to an object of the hard coded CoreTemplateName / CoreTemplateName and State exists.
  • To have a working StartInterceptor, creation of a Subclass is necessary to set a CoreTemplate name

Migration:

  1. Configure a SearchConfig that matches with the Relation-Search and State.
  2. Use 'Dynamic Search' and set the parameters accordingly as described above.

CoreObjectProcessStartInterceptorComposite

Functionality:

  • Combines several hard coded StartInterceptors
  • To have a working StartInterceptor, creation of a Subclass is necessary. List with StartInterceptors to combine needs to be hardcoded inside.

Migration:

  1. Depending on how the combined StartInterceptors are used in combination, a 1 to 1 migration is not possible.


This article includes updates for Smart ID 22.10.2.

Related information