Example: Review and release a Revenue hold

A common pattern is to use Workflow to identify contracts that require review, notify an accounting user, and release the hold after an approval step.

1. Start the Workflow from a schedule, event, or manual run.
2. Retrieve the Revenue records that meet the business criteria.
3. Use a condition to keep only records with an active hold and an eligible status.
4. Send the record details to an approver or create a manual approval task.
5. If the approval succeeds, use the Revenue release-hold task.
6. If the approval is rejected, retain the hold and notify the responsible team.
7. Record the result in the Workflow run history or send a completion notification.

Example: Link one Revenue Contract to another

Use case: Combine the source Revenue Contract RC-123 into an existing target Revenue Contract RC-200.

Configure the Link/Delink task as follows:

Operation:       link-rc
Source RC:       RC-123
Target RCs:      RC-200

The internal Workflow test case uses this pattern: Add a Revenue Link/Delink task, select link-rc, and map target_rc_ids.

Run the Workflow, and verify that the contracts are linked.

Expected result: The source Revenue Contract and its hierarchy are added to the target grouping, and Revenue reallocation occurs as applicable.

Holds at the Revenue Contract or performance obligation level can be applied again to the target Revenue Contract.

Example: Delink a performance obligation from a Revenue Contract

Use case: Remove a performance obligation from RC-123 so that it can be reassigned to another Revenue Contract or handled as an orphan transaction.

Configure the task as follows:

Operation:       delink POB
RC:              RC-123
POB:             <POB identifier>

The internal Workflow test case uses rc_id and pob_id for this operation.

After the task runs, verify the performance obligation relationship and any reallocation result in Revenue and in Workflow run history.

Expected result: The performance obligation is delinked, and engine-side reallocation occurs as applicable.

Delinked items can appear as orphan transactions and can later be linked to an existing or new Revenue Contract.

Example: Move a released line to another grouping

A common pattern is:

1. Identify the source line and intended target Revenue Contract or performance obligation.
2. If the source Revenue Contract is posted, unfreeze it before delinking.
3. If the performance obligation has released revenue, defer the revenue before delinking the line.
4. If the line is the performance obligation's lead line, switch the lead line first.
5. Delink the line.
6. Link the orphan line to the target Revenue Contract or performance obligation.
7. Validate the final performance obligation assignment, lead-line relationship, allocation, and accounting impact.

Example: Run a Revenue operation and monitor completion

1. Start the Workflow from a schedule or manual trigger.
2. Run the required Revenue operation, such as a supported allocation, forecast, or file-processing task.
3. Capture the task status and output.
4. Use a condition to branch on success, failure, or an intermediate status.
5. Notify the appropriate team, and include the Revenue record or job identifiers needed for investigation.
6. For failed operations, review the task details and rerun only after you understand the underlying Revenue issue.