Using notify action files

Use this Forum to post tips and techniques for using LongReach. Please explain in detail. This Forum is managed by the LongReach user community. LANSA cannot guarantee the accuracy of any information posted to this Forum.
Post Reply
Posts: 67
Joined: Fri Dec 09, 2011 7:52 am

Using notify action files

Post by alick » Mon Jun 18, 2012 4:55 pm

A .notify file allows a business to deliver a list of notification messages to the LongReach end user.

A backend server program could generate a notify file which contains a list of possible notifications an end user might need to complete a work order.

If you create a file with the .notify extension and use the following JSON format, the end user can open this file and tap the table entry to send the selected notification message to the backend server message queue.

Only the value of the message property is sent to the message queue.

To make the message machine readable and you could prefix a task/job number and a status code. ie. 0123456-COMPLETED

For example the Task.notify could contain the following JSON data.


"title":"Work Order 124",
{"id":"task1","title":"The task has not been completed as parts are required","subtitle":"You need to order the parts through the BPCS system","message":"0123456-PARTS"},
{"id":"task1","title":"The task has not been completed and another site visit is required","subtitle":"You need to contact your manager for scheduling","message":"0123456-REVISIT"},
{"id":"task1","title":"The task has been completed","message":"0123456-COMPLETED"}

The id property is used to locate the notify message queue specified in the httpd.xml. Special substitution values allow dynamic merging of client data.


<notify id='task1' queue='/QSYS.LIB/DEVJSM.LIB/NOTIFY1.DTAQ' data='{ID},{NAME},MSG-{MESSAGE}'/>

Post Reply