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.
Configuration
To use this task, configure the following delegate expressing 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 extract custom defined task parameters for a MappedTask from the database and make them available in the task.
Configuration
To use this task, configure the following delegate expressing in your service task:
${createRelationParametrizedJavaDelegate}
The following parameters can be configured in PRIME Designer:
| Parameter | Mandatory | Default value | Description |
|---|---|---|---|
objectRelationDAO |
| Reference to a bean of type IObjectRelationDAO. Used for relation-operations. | |
objectRelationTypeManager |
| Reference to a bean of type IObjectRelationTypeManager. Used to check whether given object relation types (relationTypeToDestination and relationTypeToSource) exist. | |
source |
| Data pool name of the source which relation has be created. The name of the core template of this data pool will be saved in the database. | |
destination |
| Data pool name of the target which relation has be created. The name of the core template of this data pool will be saved in the database. | |
relationTypeToDestination |
| HAS_A | The name of direction from the source to the destination. |
relationTypeToSource |
| CAME_FROM | The name of direction from the destination to the source. |
includeRelationTypeToCompareOfObjects |
| false | Flag indicating if the relation type should be included while comparison of objects. |
exceptionIsThrownIfRelationAlreadyExists |
| true | Flag indicating how the application reacts if relation already exists. If set "true" then throw Exception, else do nothing. |
Description
Use this task to remove existing relations between objects. 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 | Default value | Description |
|---|---|---|---|
dataPoolName |
| Data pool name of the source whose relation shall be removed. | |
destinationType |
| Destination type 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. It is the parametrized version of the functionality, that already exists in a bean configuration. For more information, see ExecuteSearchAndProcessSearchResultsAction.
Configuration
To use this task, configure the following delegate expressing 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 ValidTo field. 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. |