Last week, RoboMQ launched its last release of Connect iPaaS for 2019. This release was named Michelangelo, after the famed renaissance sculptor and painter of the Sistine Chapel in the Vatican. Michelangelo is the third release to go live this year since the launch of Connect iPaaS in Q1, 2019. It is a major release that added a truckload of features and functionalities, covering core platform capabilities as well as the addition of many new API connectors for leading CRM, SaaS, analytics, databases and IoT applications.
In this blog, we will the cover major additions and functionalities of Connect iPaaS under the following sections:
- -Core platform features
- -New ecosystems or application connectors.
Core Platform Features
Several new features are added to the core Connect iPaaS platform that are available across each of the ecosystems or the application API connectors supported by it. These new features provide major enhancements to the way workflows are designed.
Some of the newly added features like conditionals, selective update and delete (in conjunction with the existing event filter functionality) provide powerful UX constructs that apply complex logic and conditional processing. These capabilities are more typical of BPM (Business Process Management) and BPEL (Business Process Execution Language), which are offered in a simple, intuitive and easy way for a business or a non-technical user.
Conditionals
Conditionals are the expression of selection criteria, or if-then-else logic, applied to actions or tasks in event processing. Previous to this release, Connect iPaaS supported adding selection criteria to event triggers, called a filter. When filters (or selection criteria) are applied to an event trigger, a user can choose which events of interest will be processed down the workflow. Conditionals, on the other hand, are applied individually to each of the actions or tasks that are executed in response to the event trigger. By using conditionals, each of the actions can select which events will be acted upon by that action.
For example, take ServiceNow as an application where a “New Incident” is created. The new incident is the event trigger. We may want to only select the incidents that are related to the value “Network”. This can be done by applying the “Event Filter” that selects incidents where “Category” is equal to “Network” as shown below.
You may want network incidents of “High” urgency to be assigned to an external vendor, which can be done by creating a new incident in the vendor’s PagerDuty system. To do this, you will create an action in the workflow that will apply Conditionals to selectively process ServiceNow incidents of “Network” category that have the “Urgency” field set as “High”.