WebApi - Pipeline Hashing Synchronization

WebApi - Pipeline Hashing Synchronization

Valuekeep Integrator 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).

This method allows to synchronize a pipeline's hash, that is, synchronize the hashing of records that have been synchronized successfully, by avoiding later synchronizations, if there are no changes on the hashing attributes.

The method used for that is: POST /api/mytenant/myorganization/integration/pipelines/synchash

Example (Json) for the hashing synchronization of a pipeline.

1.     {

    "BaseEntity": "BusinessCore.Brands",

    "ValueSourceHash": "VALUEKEEP",

    "FieldSourceHash": "User_SourceHash",

    "FieldTargetHash": "User_TargetHash",

    "FieldIsSync": "User_IsSync"    

}

 

Description of the attributes available on the request:

  1. BaseEntity: identifies the base entity (main table);
  2. ValueSourceHash: identifies the hash key value on the source system;
  3. FieldSourceHash: identifies the SourceHash attribute, when ignored, the system assumes: User_SourceHash;
  4. FieldTargetHash: identifies the TargetHash attribute, when ignored, the system assumes: User_TargetHash. This attribute will be used to preserve the synchronized value;
  5. FieldSyncHash: identifies the IsSync attribute, when ignored, the system assumes: User_IsSync. This attribute will be used to control if the record is synchronized (the records are classified for synchronization when the attribute value FieldSourceHash is different from the attribute value FieldTargetHash).
When this method is executed successfully, it returns HttpStatusCode.OK.



    • Related Articles

    • WebApi - Pipeline Hashing Calculation

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

    • WebApi - Auditing Pipeline

      The Valuekeep Integrator conceptually allows to monitor the execution of all pipelines. This feature allows the implementing agent/integrator to control the execution of integration flows and identify irregular situations that require to eventually ...

    • How to set up the pipeline execution (Windows Service)?

      The host is the process runtime than instantiates the Valuekeep Integrator engine (PipelineEngine) to manage the pipeline execution (using a scheduling procedure or using a specific on-demand context). The platform provides a Windows Service ...

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

    • How to customize the pipeline tags for the request URL?

      In Valuekeep, there are "POST" requests, which come from keys, as shown below: The method used to create a follow-up report in a work order is: POST ...