Why Boomi Advanced Workflow? Part 3: The Process Call Shape Continue

In our previous blog on Process Call component, we have highlighted on how this component can help reduce the complexity of the integration process. Another useful feature of this component is, it also helps to execute dependent processes in an orderly manner. The following scenario will elaborate more on this aspect:


The process needs to sync Netsuite Invoice to Salesforce Closed Won Opportunity


Before the Netsuite Invoice is synced, we need to ensure that the following is synced first:

  • Item
  • Customer

There are many possible ways of achieving this. However, let’s explore the solution where one doesn’t utilise the process call while the other does


Without Process Call
Each process – Item, Customer, is deployed individually

With Process Call
Each process – Item, Customer, is positioned under one main process. Only main process is deployed.


From the scenario above, we can list the obstacles of not using a process called:

  • schedule can only be configured based on the best estimate basis
  • run the risk of the process overlapping each other
  • invoice record failed to be synced as the item/customer record has not been synced yet


Hence, the apparent benefits that we can get from using the process call are:

  • the process schedule can be coordinated accordingly
  • each process can be executed based on the completion of the previous process
  • data record is synced in order