Sidebar
en:prozessdefinition:jobs:jobsteps:allgemein:entitytransformer
EntityTransformer
The Job Step EntityTransformer transforms all entities from the source format (set in EntitySelector) to a selected target format. Here, the entitlements (mostly documents) are mapped to the target format using mappings.
| Properties | |
|---|---|
| Name | Description |
| Type | Class name of the jobstep |
| Name | Name for the jobstep that will appears in the job designer |
| Description | Optional description for the jobstep |
| Activate log output | If active, extended output for this jobstep is displayed within the message log. |
| selection strategy | The selection strategy determines which Mapping is applied:\\ \\ByTargetType: This setting searches for a mapping that can convert the current document to the type defined under TargetEntityTypeName.\ \\ByFixedMapping: transforms the document after the mapping entered under MappingName. \\ByPartnersPreference: The mapping is searched from the TypeSet of the trading partner, where the communication direction and the type match the document and if defined, the target type of the mapping matches the TargetEntityTypeName. If no mapping was found via the TypeSet, the system searches for the template partner and if this does not lead to a result, the mapping stored under MappingName is used. \ \\BySystemPartnersPreference: Analogous to ByPartnersPreference only for the system partner. |
| Name of the TargetType | This specification is mandatory for the selection strategy ByTargetType and describes the mapping used for converting the document. The system searches for mappings whose target corresponds to the corresponding type. |
| Name of the mapping | This specification is mandatory for the selection strategy ByFixedMapping and describes the mapping that is used to convert the document. It is also a fallback mapping if no mapping can be found using ByPartnersPreference. |
| Triggering in a transaction | This option should be selected with caution, e.g. only if the EntityTransformer is followed by an EntityMessageCreator and a maximum of one EntityStateSetter. This setting achieves the greatest advantage if many documents are triggered from an incoming document in the mapping. The created messages, attachments, envelopes and documents are then created with the status information in a transaction. And the inserts on the DB can be combined into blocks (bulk inserts). |
Note: The MappingTransformer throws a task if no mapping can be determined with the selected selection strategy. It must be taken into account that the selection is cascaded. For the selection strategies ByPartnersPreference and BySystemPartnersPreference, the TypeSets are always applied first, and the matching mappings are filtered out. If one or more are found here, the first one is chosen. If nothing can be found here, the Transformer will check if a target type is specified. If there is an appropriate mapping for the target type specified here (optional) and the incoming source type, the first hit is used. If a fixed mapping is specified2) then this is used as the last option.
Note: For the processing of multiple entities within a mapping, eBiss offers the MultiEntityTransformer.
The following JobSteps are usually connected to theEntityTransformer
en/prozessdefinition/jobs/jobsteps/allgemein/entitytransformer.txt · Last modified: 2024/06/17 15:47 by 127.0.0.1