Page Comparison

source

Data pool name of the source of the relation, which has to be created. The core template name of this data pool will be saved in the database.

destination

Data pool name of the target of the relation, which has to be created. The core template name of this data pool will be saved in the database.

includeRelationTypeToCompareOfObjects

Valid values:

• true

• false (default at design time) 

Flag indicating if the relation type should be included when searching if the relation already exists. If you want to create multiple relations of different types between two core objects this parameter has to be set to true.

Example: A relation Card → Certificate already exists in the database with the relation type "OldRelation"

Use case 1

1. Input:

   1. includeRelationTypeToCompareOfObjects = true

   2. Relation type = "NewRelation"

2. Expected output:

   1. New relationship (relation type - "NewRelation") added for the relation Card → Certificate

Use case 2

1. Input:

   1. includeRelationTypeToCompareOfObjects = false

   2. Relation type = "NewRelation"

2. Expected output:

   1. No changes as a relation is already found.

exceptionIsThrownIfRelationAlreadyExists

Valid values:

• true (default at design time)

• false

Flag indicating how the application reacts if the relation already exists. If set to "true" then throw Exception, else do nothing.

relationType

Default

Type of the relation. The object relation type must exist or an exception is thrown.

dataPoolName

Data pool name of the object whose relation shall be removed.

secondDataPoolName

-

Only one of these three parameters is allowed to be filled!

Single Drop: Data pool name of the second single object. This object has to be available inside the Process Map.

secondDataPoolNameDropAll

-

Data pool Drop: Name of a Data pool. Relations to all objects belonging to this data pool are removed.

coreTemplateName

-

Core Template Drop: Name of a Core template. Relations to all objects belonging to this template are removed.

objectType

Deprecated. This parameter has the same meaning as coreTemplateName and is only provided for downgrade compatibility.

relationType

-

When configured, only relations of the specified type are removed.

coreTemplateNameList

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

fieldName

Example value:

• ValidTo

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

Example value:

• 30 (see also the description to the right)

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 31^st March 2017. If the offsetInDays is set to 30, the service task will only find the soft token with the beginning of 1^st March 2017.

coreObjectIdListVariableName

-

Example value:

• PcmDpCertificate_Coreobjects

• CoreObject_Ids

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

Meta_CoreObjectState_Field

Example values:

• Meta_CoreObjectState_PstmDpCertificate

• Meta_CoreObjectState_BaseDpEmployee

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.

Meta_CoreObjectState_Value

Example values:

• issued

• active

• etc.

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