Plugin V10 – Pipelines – Mappers
- A service integration solution must be able to easily define data bidirectional transformations, from their native representation to other formats, more adequate for the process integration, such as: XML, JSON.
- The PRIMAVERA V10 – Valuekeep Integration plugin, offers a transformation process (format JSON) with the purpose of mapping the data from the source system to be issued to the target system. This mapping technique uses a Data Dictionary, preserving the original data and the transformed data.
- In order to optimize the integration processes, the plugin offers on the installation folder – <InstallPath>\VKPlugin\SAMPLES\MAPPERS – a set of mappers (json files) that can be used when implementing the integration services.
- The syntax and semantics applied is common to both systems and is defined in a model context and easy to interpret.
Related Articles
Plugin V10 - Pipelines – Overview
The pipelines examples distributed by the plugin PRIMAVERA v10 – Valuekeep Integration, available on – <InstallPath>\VKPlugin\SAMPLES – adopt a configuration based on the methodology Reader-Mapper-Writter, as shown on the following message.
Plugin V10 – Pipelines – Auditing
The PRIMAVERA V10 - Valuekeep Integrator plugin conceptually makes available through information categories, using lists, the possibility of monitoring the execution of all pipelines. This functionality allows the implementer / integrator to control ...
Plugin V10 – Pipelines – Reader
The readers available on the PRIMAVERA V10 – Valuekeep Integration plugin has the goal of providing the systems (PRIMAVERA ERP V10 and Valuekeep) with mechanisms that reduce the number of requests and allow the implementer/integrator to easily ...
Plugin V10 – Pipelines – Hashing
The plugin PRIMAVERA V10 – Valuekeep Integration adopts a version control based on a hashing system. Each pipeline has a version control, that is, it has a hashing key that allows to identify if the information subset (hashset) has still not been ...
Plugin V10 – Solution – Pipelines
An integration solution is made up of one or several pipelines (integration flows). The solution made available as a base example has several integration flows, which can be reused and/or customized according to the business processes defined.