GEL Integration Processes

A GEL integration process is a way to automate repetitive steps that would otherwise be performed manually using 
Classic PPM
. A process can act on any object type. The process includes a series of steps that result in a completed end point. A process has a start step (required), an end step (required), and one or more intermediate steps. Each step included in the process performs one or more actions that moves the process toward its completion. The following process actions are available:
    . Performed by a user in the user interface.
    . Completed by a 
    Classic PPM
     system action.
    . Completed by running a job that is either scheduled or started manually from the user interface.
    Custom action
    . Available for normal process steps that include custom GEL code. These GEL snippets use tag libraries to interact with various data sources and data destinations.
You can disconnect integration processes from any specific object. This flexibility allows you to do the following steps:
  • Schedule integration processes in 
    Classic PPM
  • Initiate integration processes in real time in one of these ways:
    • Manually from the user interface.
    • Using a XOG web service request.
From a background job, real-time integrations enable external applications to send data proactively. The request starts an integration process and then passes the incoming data.
 For performance reasons, the XOG web service request does not initiate integration processes for all objects. The objects that can have integration processes that the XOG web service initiates are projects and incidents.
Integration Process Checklist
Use this checklist to set up and run integration processes:
  1. Create the process.
  2. (Optional) Create groups to represent larger segments of the process.
  3. Create start, intermediate, and finish steps.
  4. Include actions on steps. GEL can be used through Custom Actions.
  5. Connect the steps with splits and joins.
  6. Validate the process. For more information about this step, see 
  7. Use the web service API to start the process, and then register the web service request to invoke the process.
    • Web service requests do not need to conform to any product API. They need only be valid SOAP requests.
    • The external application maps incoming SOAP message with a process.
    • The SOAP listener servlet responds to incoming web service requests.
    • The Catalog Listener and the Ad-Hoc Query listener are built-in listeners. You can register subsequent listeners in the database using an XPath expression, a target namespace, or both to match the listener to an incoming service request.
The following image describes the XOG realtime integration:
Image describing XOG Realtime Integration
Image describing XOG Realtime Integration
The following image describes the XOX scheduled or manual process:
Image describing XOG Scheduled or Manual Process
Image describing XOG Scheduled or Manual Process