What you'll be learning about:
Getting outside data into the Cloud
If Rocky Jupiter already have a purchase order processing workflow in place, one that registers new delivery tasks in the company databse, it is really a waste of resources to have a separate New Task webform that administrators fill in and submit to make the delivery tasks appear on drivers' mobile devices. A more efficient way would be to have any new delivery task get pushed from the Rocky Jupiter ERP to the Mobilengine Cloud (and the mobile devices that synchronize with it) automatically, as soon as a new purchase order for a delivery arrives to the Rocky Jupiter system. That is exactly what you'll be doing in this tutorial.
Let's review the steps involved:
-
Set up a custom data package definition that specifies the structure of the XML messages that carry the delivery task data
-
Set up and configure an inbound integration endpoint on the Cloud to handle the inbound data traffic
-
Set up and customize a WDX protocol-compliant web service client that passes the integration messages to the inbound endpoint
-
Make the workflow script that was associated with the New Task webform, and that inserts new delivery tasks into the
assignmentsreference table process the incoming integration messages instead of form submissions
In the next section, you'll be introduced to the custom schema language that defines
the XML messages that an integration solution passes to and fro, and specifies their
workflow script representation.