WebServices

Webservices provides fast, reliable, and secure communication of facility information between the system and 3rd party systems. This includes new requests and updates coming into the system as well as outbound updates to external systems.

The update request process allows for updates to existing work requests via an XML document sent via Webservices. This section covers the process for assignments on an update, failure messages, and what must be in place from 3rd party systems. This is not meant to be an all inclusive guide for implementation; contact your super administrator for additional details.

Process for Assignments on an UPDATE

  1. Receipt of an update XML document with a method = Reassign
  2. The system will try to match the Employee External ID (EEID) on a reassign from external systems. The following are successful and unsuccessful matches.

    1. Unsuccessful match of the EEID from the external system within 360Facility:

      • EEID is blank and the method=Reassign
      • EEID matches more than one EEID in 360Facility
    1. Successful match of the EEID within the external System occurs with unique match of EEID
  3. Validate Employee can be assigned based on these rules.
    1. Active user within the system
    2. Location of the request does not match the location of the user
    3. Type/Subtype Combination doesn't match the user's type/subType via the Activity Group
  4. Update the history record to write a standard record for reassigned

Failure Messages

Failure messages will dead letter and emails will be sent via dead letter queues. Information will contain:

  • Work Request Number
  • Error Code: Pre-defined list to match the above (will be standard)
  • Error Description: Pre-defined list to match the above (will be standard)

External System Changes

  1. Reliable software to receive and send XML documents and process acknowledgments and declines.
  2. Ensure EEID from the external system are loaded within the system
  3. Format and work through configuration of the XML document
  4. Ability to accept errors from 360Facility (equivalent of the dead letter Queue)
  5. Train users on procedures to re-process errors that they receive