Description
Use this task to check if a relation between two core objects exists. The names of both data pools have to be provided. 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 expression in your service task:
${checkObjectRelationParametrizedTask}
The following parameters can be configured in PRIME Designer:
| Parameter | Mandatory | Sample Value | Description |
|---|---|---|---|
| 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. |
Description
Use this task to create a relation between two core objects.
Configuration
To use this task, configure the following delegate expression in your service task:
${createRelationParametrizedJavaDelegate}
The following parameters can be configured in PRIME Designer:
| Parameter | Mandatory | Value | Description |
|---|---|---|---|
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 |
|
| Flag indicating if the relation type should be included when searching if the relation already exists. |
exceptionIsThrownIfRelationAlreadyExists |
|
| 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. |
Description
Use this task to remove existing relations between objects. The direction of the relation is not relevant, meaning that source and destination may be exchanged.
For example, if an employee started working with a replacement card while receiving his employee-card, the connection to the re-usable replacement card will be removed.
Configuration
To use this task, configure the following delegate expression in your service task:
${dropRelationsParametrizedTask}
The following parameters can be configured in PRIME Designer:
| Parameter | Mandatory | Value | Description |
|---|---|---|---|
dataPoolName |
| Data pool name of the source whose relation shall be removed. | |
objectType |
| Core template name of the destination whose relation shall be removed. |
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 expression in your service task:
${coreObjectExpiryCheckParameterizedTask}
The following parameters can be configured in PRIME Designer:
| Parameter | Mandatory | Default value | Description |
|---|---|---|---|
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
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. |