Plugin V10 – Pipelines – Lists

Plugin V10 – Pipelines – Lists

In the scope of integration, readers use the resources of the lists in order to define and segment the information applicable to the business process. As a tool for easy use and monitoring of business processes, the plugin adopted the application lists as a transversal reading technique, enhancing the performance of the services.

The plugin provides the following readers that should be used depending on feasibility and technique applied.

  1. ListReader: uses a list based on an information category. The information transmitted is restricted exclusively to that provided by the list, including the filters applied;

  1. AdhocListReader: uses a list based on a query, enhancing integration. The transmitted information is restricted exclusively to the information provided by the list;

  1. FullListReader: uses a list based on an information category. The transmitted information corresponds to a get request from the entity, that is, the list is only used to get the subset (conditional filter);

  1. FullAdhocListReader: uses a list based on a query, enhancing integration. The transmitted information corresponds to a get request from the entity, i.e. the list is only used to obtain the subset (conditional filter).


In order to enhance the performance of the services, the lists should include conditional filtering based on versioning control (hashing field)

The plugin distributes several sample application lists in: <InstallPath>\VKPlugin\SAMPLES\V10LISTS\PRIMAVERA10_VALUEKEEP3, which you can explore and use in developing your pipelines.



    • Related Articles

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