CycleService

The CycleService REST API can be used to submit a task of activity processing from OIPA user interface or any third-party system to Cycle Agent. When a user sends a SubmitTask request to the Cycle Service, all the activities with an Effective Date less than or equal to the current system date are submitted to the Cycle Agent for processing.

Activity Type Codes

This service supports the activity types such as, Type Code 01 - Natural and Type Code 04 - Redo that are in Pending status.

Note: The other activity types such as Type code 02- reversal and Type Code 03 - Undo, are not supported by SubmitTask request for Cycle processing. This includes the activity status such as, Shadowed, Pending Shadowed, NUV Pending, Gain/Loss Pending, Queued, and Requirements Pending.

Process Flow

When a user submits a request for activity processing from OIPA user interface or a third-party system to the Cycle Agent, the CycleService REST service call is invoked and handles the communication between OIPA and Cycle. When the service is triggered, the system creates an entry in the AsCycle table and returns a CycleGUID as response.

Note: For security, the system implements role-based authorization to process the activities