Integrate for keeps

What you'll be learning:

How to make a workflow script update a reference table with integration message data

Integration messages, when they arrive to the Mobilengine Cloud, can trigger dedicated workflow scripts just like form submissions. The most useful and often-used function of Mobilengine Cloud workflow scripts is processing incoming data to update reference tables with. The newPO dacs that you've hard-coded and sent yourself through the web service client ultimately represents a record in the assignments, so why don't you add its contents to assignments when it comes in? That would be really spectacular, and a nice demonstration of your integrating skills, because you have a workflow solution associated with changes to the assignments reference table.

Rocky Jupiter drivers are notified about any change to the reference table that has their name on it to drivers in the Driver Task List dashboard form, so the data in the incoming message would instantly get downloaded to one or more mobile devices, and populate a nicely formatted form.

Leverage your previous development work and awe your clients.

Have a workflow script ready to process incoming messages

Open the workflow script that you associated with the newPO dacs in the previous tutorial, and extend it to insert the contents of the incoming integration message into the relevant columns of the assignments reference table. By now, you probably don't need any guidance to do that, but here's the script nevertheless:

newTask.rfs

server program newTask for dacs newPO
using reftab assignments;
{
    db.assignments.Insert({assignment_id:dacs.newPO.assignmentId,
                          usr:dacs.newPO.driver,
                          client:dacs.newPO.client,
                          load_type:dacs.newPO.loadType,
                          load_address:dacs.newPO.loadAddress,
                          unload_address:dacs.newPO.unloadAddress,
                          due_date:dacs.newPO.dueDate.DtuToDtdb(),
                          status:"Assigned"});
    trace dacs.newPO.admin +
          " assigned a delivery task to " +
          dacs.newPO.driver +
          " at " +
          dacs.Dtu.Format((dtf yyyy "-" MM "-" dd " " HH ":" mm ":" ss o)) +
          ".";
}

There's a trace statement appended to the end that makes use of the admin field of the message, as well as the Dtu property common to all dacs messages, which is the timestamp of when the message was created.

Save the script in your solution folder, and publish your solution to the Cloud.

If you've created a new script file, make sure that you delete traceDacs.rfs - just like in the case of form submissions, a single dacs cannot be associated with more than one workflow script.

Test the incoming integration solution

You must be itching to see if your integration solution is working, right? Open the RockyJupiter.Mobilengine.Client project in Visual Studio, and run it to find out.

If all goes well, your command line informs you that the dacs was transferred, the Dev console → Tasks screen on the Backoffice lists the incoming dacs and the workflow script that it triggered.

Figure 182. The Dev console → Tasks screen logs the successful dacs-triggered script run

The trace statement of the workflow script also does its job, and records the administrator who assigned the new delivery task to the driver.

Figure 183. The workflow script traces the info that you specified in the task log

But most importantly, and awesomest of all, there's a new delivery task in your Driver Task List dashboard form on your mobile device!

Figure 184. There is a new delivery task assigned to Petar Hoyt, our test user

Go ahead and Confirm the new task - it's fully functional, and just as real as all the other ones. So it should be, because it's just as much a part of the assignments reference table where the delivery tasks come from as those other ones. You can check for yourself: export the reference table on the Input data tab of the Backoffice site.

Strangers point and whisper 'It's the Mobilengine Ninja!' when they see you in the street, right? You almost know as much as it's humanly possible about workflow solution development: finish the next tutorial, and your education is complete.

Related links

Implement inbound integration

Send data to client companies via integration

Developer Documentation

Send data to mobile devices via integration

Integrate for keeps