Looping on Repeating Component Requests
(Doc ID 503223.1)
Last updated on APRIL 01, 2019
Applies to:Siebel System Software - Version 188.8.131.52  and later
Product Release: V8 (Enterprise), V7 (Enterprise)
Database: Any database
Application Server OS: Any platform
Database Server OS: Any platform
This document was previously published as Siebel SR 38-2052212037.
The customer had created a simple workflow that invokes a simple business service. The business service deletes orphan Activities (where SRA_SR_ID is null).
To run this workflow through a Repeating Component Request (RCR), a Component Job Definition was created for the Workflow Process Manager to invoke the custom workflow.
Then a RCR was created and submitted for the job.
The following behaviour was observed:
- The RCR status goes to Active.
- The workflow seems to run, because any records that meet the deletion criteria is deleted.
- However, the job never reaches status Success and there are no new queued entries for it. Instead it remains in status Active.
- Even after cancelling the RCR, when the status shows Cancelled, the workflow seems to be still running: Whenever a new orphan activity is created, it gets deleted.
The customer had to stop/start the Siebel server to stop the RCR from running.
=> Question: Why was the process running after it completed or cancelled?
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document