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 integrated or if it  suffered any change in the data, requesting a new integration.

This hashing technique is applicable to an information segment (hashset), that is, it allows to identify the attributes that make up the hashing key (by ignoring integration requests when the entity suffers changes in attributes that are not a part of the key composition).

All pipelines have a hashing key (defined using user fields) on the source system and a hashing file (defined in format JSON), for the version control. If a physical entity (table) has several pipelines, you must create as many hashing keys as the number of pipelines that come from the table (you can eventually share the hashing file).

Composition of the Pipeline Hashing Key:

1. SourceHash: attribute used to calculate the hash on the source system (calculated every time a reading request is performed);
   
2. TargetHash: attribute used to preserve the hash value on the target system (updated every time a successful integration is performed);
   
3. IsSync: attribute used on the integration lists as a conditional filter (this attribute specifies if the record has been integrated, it is controlled by comparing the values of the attributes “SourceHash” and “TargetHash”);
   

Composition of the Pipeline Hashing File:

1. Algorithm: identifies the hashing algorithm;
   
2. BaseEntity: identifies the base entity (main table);
   
3. LyncEntities: identifies the entities related (including the main entity);
   
4. Attributes: identifies the attributes that make up the hashing key (that is, used for the hash calculation);
   
5. Filter: identifies the conditional filter to be applied for the hash calculation;
   
6. FieldSourceHash: identifies the SourceHash attribute (when ignored, the system assumes SourceHash);
   
7. FieldTargetHash: identifies the TargetHash attribute (when ignored, the system assumes TargetHash);
   
8. FieldSyncHash: identifies the IsSync attribute (when ignored, the system assumes IsSync);
   

The following image presents the conceptual methodology of the hashing supported by the plugin.

The plugin distributes several hashing files examples in: <InstallPath>\VKPlugin\SAMPLES\HASHETS, that you can explore and use when developing your pipelines.

• Related Articles

• 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 – 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 – 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.

• Plugin V10 – Solution – Pipelines

  An integration solution consists of one or several pipelines (integration flows). The solution provided as a base example contains several integration flows, which can be reused and/or customized according to the defined business processes.