General Intro

BECS Dynamic Packaged Integration (BDPI) is general enabling one step integration with unlimited amount of user enterprise systems from ERPs like SAP, IBM Maximo or IFS via DMS (SharePoint, OpenText, Documentum, ….) up to IoT, Spatial or GIS systems (ESRI, AutoDesk, Hexagon, …). Learn more about BDPI here and at "Mastering in BDPI" section here. The Step-by-step guide how to implement BDPI into your app is available in Downloads section at the bottom of this page.

Section structure

In this section you can find all needed knowledge in following structure:

• General principle of BDPI adaptation
• General structure of BDPI interaction
• Supported types of BDPI interactions
• Interactions in detail​​​​​​​​​​​​​​​​​​​​​
  • Read the property data
  • ​​​​​​​Read multiline data
  • ​​​​​​​Read Grid TAB Names
  • Execute User Query
  • Read attributes for Query Builder
  • Read Value List for selected attribute
  • Read IoT TAB Names
  • Read IoT Data
• Security
• Real Postman for you to test
• Downloads

​​​​​​​General principle of BECS Dynamic (BDPI) adaptation

BECS Dynamic Integration is invented to offer universal integration gateway for your product to any of possible user systems. This platform is designed with focus on 3 major principles:

• ​​​​​​​​​​​​​​​​​​​​​Principle “one EndPoint for all”
  • Be visible from side of your product as one and only same EndPoint independently of required integration
• Principle “one BECS implementation forever”
  • Save time and money on side of your product by “one implementation for all integrations” = do not require any changes on your side for any featured user integrations
• Principle “always fresh data without saving on your side”
  • Serve data “on fly” = give to your product only fresh data without need of saving them on side of your product

Thanks to all of those principles is implementation of BECS Dynamic in your product very simple and BECS will massively enhance your integration capabilities once for all.

• ​​​​​​​​​​​​​​General schema of execution

Integration with your product will be working as shown on following schema:

General structure of BDPI interaction

There is expected to have 2 major flows implemented:

​​​​​​​Supported types of BDPI interactions

Major interactions

BDPI supports 3 major interactions:

• ​​​​​​​Input attributes in detail:

• ​​​​​​​Output json to receive

• BECS EndPoint to call:

• ​​​​​​​Input json to use

In a call is needed to provide following json:

{

   "returnAsXML":false,

   "projectName":"PS_D_DISPATCHER",

   "projectVariables":[

      {

         "name":"CODE",

         "value":"0x30000001d11"

      },

      {

         "name":"EventType",

         "value":"GRID"

      },

      {

         "name":"TabName",

         "value":"SharePoint"

      },

      {

         "name":"organizationID",

         "value":"fab9774b-b338-4cc2-a6c9-458bdf7f966a"

      },

      {

         "name":"iModelID",

         "value":"a9ac27e8-793e-434c-9365-da069eac0ddb"

      }

   ]

}​​​​​​​

• Output json to receive

For reading all existing TAB Names for your featured Multiline data read you can use exactly the same call as described in previous section “Read multiline data”, just use blank TabName in input json (because in truth you do not know the TAB Name until reading them):

• ​​​​​​​Output json to receive

• BECS EndPoint to call:

• ​​​​​​​Input json to use

In a call is needed to provide following json:

{

   "returnAsXML":false,

   "projectName":"PS_D_SEARCH_OBJECTS",

   "projectVariables":[

      {

         "name":"condition",

         "value":"<conditions><condition><field>Manufacturer of asset</field><value>A*</value></condition><coloredBy>Year of construction</coloredBy></conditions>"

      },

      {

         "name":"iModelID",

         "value":"b8c32999-e571-468b-9584-85cd1ae97369"

      },

      {

         "name":"organizationID",

         "value":"72adad30-c07c-465d-a1fe-2f2dfac950a4"

      }

   ]

}

• ​​​​​​​CONDITION attribute in input json

This input attribute is used for definition of user query, where query is always defined in following structure:

<condition>

<field>Manufacturer of asset</field>

<value>A*</value>

</condition>

Every condition has operator “EQUAL” only and between conditions is only “AND” operator.

• ​​​​​​​COLORED BY section in input json

BDPI supports one attribute selection for colouring of output in format:

<coloredBy>Year of construction</coloredBy>

• ​​​​​​​Output json to receive

BDPI sends payload in following structure:​​​​​​​