Versions Compared

Old Version 3

changes.mady.by.user Ann Base

Saved on

compared with

New Version 4

changes.mady.by.user Ann Base

Saved on

Key

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

...

Expand
titleCore Objects: Check Relation

Description

Use this task to check if a relation between two core objects exists. The names of both data pools have to be provided. It doesn't matter which data pool is used as a source or destination point. The direction of the relation is not relevant, meaning that source and destination may be exchanged.

Configuration

To use this task, configure the following delegate expressing in your service task:

Code Block
${checkObjectRelationParametrizedTask}


The following parameters can be configured in PRIME Designer:

ParameterMandatorySample ValueDescription
sourceDataPoolName

 

The name of the source data pool that is used to check the relation with the destination data pool.

destinationDataPoolName

 The name of the destination data pool that is used to check the relation with the source data pool.
resultVariable

 

The name of the field indicating if a relation between the source and destination data pool exists. Contains either a "true" or "false" value.

"True" means that the objects are related to each other. "False" means that there is no relation between them.


...

Expand
titleCore Objects: Expiry Check

Description

Use this task to find core objects (for example, soft tokens), that will expire within a given time range.

Configuration

To use this task, configure the following delegate expressing in your service task:

Code Block
${coreObjectExpiryCheckParameterizedTask}

 The following parameters can be configured in PRIME Designer:

ParameterMandatoryDefault valueDescription

coreTemplateNameList


Comma separated list of core template names that shall be the base of the search.
fieldName


Name of the data pool field that indicates the expiration date, for example, ValidTo. The data pool must belong to the core template(s) mentioned above.
offsetInDays


The offset in days before the related core objects expire.

The base is the field specified by fieldName, for example ValidTo. If you provide a value for offsetInDays, then logically it is

ValidTo - offsetInDays = dateToFindSofttoken

  • If dateToFindSofttokens is still in the future compared to the currentDate, then the soft token will not be found.
  • If dateToFindSofttokens is equal to the current date or if it is in the past, then the soft tokens will be found.

Example:

Expiry date of a soft token is 31st March 2017. If the offsetInDays is set to 30, the service task will only find the soft token with the beginning of 1st March 2017.

coreObjectIdListVariableName-CoreObject_Ids

Name of the variable containing the core objects that were found during the search. It contains only the core object ids.

Example: PcmDpCertificate_Coreobjects

Meta_CoreObjectState_Field


Name of the data pool field that indicates the state of the core object. The data pool must belong to the core template(s) mentioned above.

Example: Meta_CoreObjectState_PstmDpCertificate or Meta_CoreObjectState_BaseDpEmployee

Meta_CoreObjectState_Value


The actual state that shall be used for filtering the search.

Example: issued, active etc.


...