Frequently Asked Questions

From
(Difference between revisions)
Jump to: navigation, search
m (/* When a SOAP connection is dropped (due to loss of connectivity for example), how does the customer's SOAP interface get status updated for jobs that have been updated by the PDA's during the outage)
Line 3: Line 3:
 
==== When a SOAP connection is dropped (due to loss of connectivity for example), how does the customer's SOAP interface get status updated for jobs that have been updated by the PDA's during the outage? ====
 
==== When a SOAP connection is dropped (due to loss of connectivity for example), how does the customer's SOAP interface get status updated for jobs that have been updated by the PDA's during the outage? ====
  
There are several ways of doing this.  The first is to wait until connectivity is restablished.  Then, query the EService server for the details of all jobs that are in an open state in the client database.  The job details returned will include all state updates from the PDA from the moment it was created, to the moment requested, with time stamps for every job event.  Simply load the data into the client database.
+
There are several ways of doing this.  The first is to wait until connectivity is re-established.  Then, query the EService server for the details of all jobs that are in an open state in the client database.  The job details returned will include all state updates from the PDA from the moment it was created, to the moment requested, with time stamps for every job event.  Simply load the data into the client database.
  
 
Secondly, you can request the job details of all jobs created or updated between 2 time periods, use the last known good transmission time as the start time, and "now" as the end time, and you will get the job details of all jobs that were updated in that time period.
 
Secondly, you can request the job details of all jobs created or updated between 2 time periods, use the last known good transmission time as the start time, and "now" as the end time, and you will get the job details of all jobs that were updated in that time period.

Revision as of 00:49, 17 June 2005

Listed below are a series of often asked questions and answers. If there is insufficient information provided, or you wish to learn more about the suggested answers, please contact your local sales representative for more information.

Contents

When a SOAP connection is dropped (due to loss of connectivity for example), how does the customer's SOAP interface get status updated for jobs that have been updated by the PDA's during the outage?

There are several ways of doing this. The first is to wait until connectivity is re-established. Then, query the EService server for the details of all jobs that are in an open state in the client database. The job details returned will include all state updates from the PDA from the moment it was created, to the moment requested, with time stamps for every job event. Simply load the data into the client database.

Secondly, you can request the job details of all jobs created or updated between 2 time periods, use the last known good transmission time as the start time, and "now" as the end time, and you will get the job details of all jobs that were updated in that time period.

Thirdly, there is a system for marking jobs as synchronized on EService. If the client SOAP interface is using this system to mark jobs as they receive updates, after the outage, the client interface can simply request all unsynchronized jobs to receive the details of all jobs that have been updated during the connection downtime.

How do I get real time monitoring of jobs and their current state ?

EService / Service+ can be configured to send real time updates of jobs and their states to an external Web Service on a customers' internet server, providing it implements the EService CallBack Interface. A WSDL descriptor file of the interface is available on request.

Can multiple field devices / workers be assigned to the same job ?

There is a one-to-one relationship between an EService / Service+ job, and the field worker to which it is assigned. However, with appropriate setting changes, it is possible to ensure that each job created for the field workers on the same client job, are created with the same external reference for the job. It is then the task of the external application to coordinate the the status and progression of the job as a whole, as the field workers progress their individual tasks.

Can EService / Service+ provide inter organisation Job dispatch ?

This is not a standard feature of the generic version of EService / Service+.

However, limited inter company / Organisation job dispatch functionality can be achieved in the short term if the Organisation is using the SOAP API. Job data can easily be transferred from organisation to organisation, and the resulting status updates can be transferred back to the originating organisation.

A custom application would need to be developed to meet these requirements.

Is there a way of marking certain jobs as invoiced on my system, or marking customer records as exported ?

Each customer, resource, and job record on EService / Service+ server can be marked with any custom data you wish, along with a flag indicating whether your data is synchronized with the server record or not. This is a standard feature of the SOAP API, and further info on the methods involved can be found on the SOAP 3 Documentation page.

Can EService / Service+ have a parent job that child relationships can be created and added to ?

i.e. A main job is created then sub jobs involving additional trades / resources are created under this job. The main job would not be closed until all the sub jobs have completed.

See the answer under #Can multiple field devices / workers be assigned to the same job ?

Further features are under development.

Personal tools
MediaWiki Appliance - Powered by TurnKey Linux