Self-Service Start/Stop/Transfer Overview

Warning:

This topic is only applicable for the integration with Oracle Utilities Digital Self Service.

The Start Stop Transfer Tasks (C1-StartStopTransferTasks) inbound web service is used by the self-service application to support the following start/stop/transfer transactions:
  • New Service
  • Add Service
  • Stop Service
  • Transfer Service
Distinct action method roles represent each type of transaction:
  • Self-Service New Service
  • Self-Service Add Service
  • Self-Service Stop Service
  • Self-Service Transfer Service
At the beginning of the start/stop/transfer process, the action method role is used to identify the type of transaction. It is determined using the Request Mode (Start/Stop/Transfer), the New Customer indicator (Yes/No) and the New Account indicator (Yes/No):
  • If Request Mode is 'Start', the Action Method Role is 'Self-Service New Service' if either the New Customer or the New Account indicator is 'Yes'. If both New Customer and New Account indicators are 'No', Action Method Role is 'Self-Service Add Service'.
  • If Request Mode is 'Stop', the Action Method Role is 'Self-Service Stop Service'
  • If Request Mode is 'Transfer' , the Action Method Role is 'Self-Service Transfer Service'.

Configuration information are maintained using Self-Service Task Type and Customer Service Type. Self-Service Task Type defines the self-service task BO to be used. Customer Service Request Type defines the customer service request BOs used to persist data, and the controls used throughout the transaction. Refer to the "Enhanced Start, Stop, and Transfer Service Configuration Options" section of the digital self-service user guide for more about the controls.

At the beginning of the transaction, configuration information are determined and a self-service start/stop/transfer task is created. The same service task is used for the entire transaction. The service task is used to store the information received from the self-service application and operation processing results. It will remain in Pending status until the transaction is finalized. When the transaction is finalized, the service task is transitioned out of the Pending status and the collected information are persisted.

The following is the expected sequence of IWS operation calls per type of transaction:

New Service
  1. Retrieve Request Type Details
  2. Retrieve Service-Related Customer Details - operation is called if customer exists (Person ID is available).
  3. Service Eligibility
  4. Process Other Person
  5. Clear Other Person
  6. Determine Services To Start
  7. Validate Start SP Selection
  8. Service Questions
  9. Process Services To Start
  10. Deposit Assessment
  11. Start Service Finalization
Add Service
  1. Retrieve Request Type Details
  2. Retrieve Service-Related Customer Details
  3. Service Eligibility
  4. Determine Services To Start
  5. Validate Start SP Selection
  6. Service Questions
  7. Process Services To Start
  8. Deposit Assessment
  9. Start Service Finalization
Stop Service
  1. Retrieve Request Type Details
  2. Retrieve Service-Related Customer Details
  3. Determine Services To Stop
  4. Retrieve Services To Stop
  5. Validate Stop Service Agreement Selection
  6. Service Questions
  7. Process Services To Stop
  8. Stop Service Finalization
Transfer Service
  1. Retrieve Request Type Details
  2. Retrieve Service-Related Customer Details
  3. Service Eligibility
  4. Determine Services To Start
  5. Validate Start SP Selection
  6. Service Questions - operation is called with Question Placement Group is 'Start Service'
  7. Process Services To Start
  8. Deposit Assessment
  9. Determine Services To Stop
  10. Retrieve Services To Stop
  11. Validate Stop Service Agreement Selection
  12. Service Questions - operation is called with Question Placement Group is 'Stop Service'
  13. Process Services To Stop
  14. Transfer Service Finalization