Skip to Main Content

APEX

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Task Definition Expiry and Workflow

Jay Campos2 days ago — edited 45 hours ago

Hello,

I came across the following in the documentation and am attempting to understand and see how I can proceed.

Business wants 2 days expiration policy to appear but the task could still remain indefinitely.

Tasks have been created via workflow. I just have normal connections from task to task.

Overall, how do I ensure tasks are not deleted when using workflows? End goal is to determine if tasks within workflows could remain indefinitely.

From below it seems like I just do a timeout connection in workflow?

Or if I just have task definition “Due on Type” set to None, while using it in a workflow context, would the tasks not be deleted, no matter how long they are in the queue/waiting for approval?

Thanks,

Jay

From the documentation :
At runtime, if the task fails to complete by the due date, the expiration policy in the task definition activates, and the task is automatically renewed or expired accordingly.

If the expiration policy in the task definition is NONE, the task still expires because it is a workflow-generated task, and cannot remain active while governed by workflow timeout.

Once the task expires, control goes back to the workflow engine, and follows the timeout connection in the workflow model. If there is no timeout connection, the workflow transitions to a faulted state.

Comments
Post Details
Added 2 days ago
1 comment
56 views