User Statuses and Transitions

A contract has predefined statuses that characterize its lifecycle. In addition, you can define user statuses and their transitions.

For example, as contract manager you may want to pass the contract for a more thorough review of its sections by the appropriate team such as Legal, Financial, and Accounts. You can do this using the user statuses and transitions that you defined.

Defining User Statuses and Transitions

Define these user statuses and their transitions using the contract setup task of Manage User Statuses and Transitions and save your changes.

Note: While defining user statuses, ensure that you select the Allow Assignment check box for each of the user transitions. This enables you to assign the contract to named assignees during a user transition.

Setting Up The State-Based Event Model

Use the Event Models setup task to create new events and actions for the business object, oracle.apps.contracts.coreAuthoring.contractService.view.ContractHeaderVO.

Set these events up for each To and From state of the user transition. For seeded states you can select from available events and actions. An example of an action could be a groovy script.

Save this new State based event model and specify the condition or contract type that can use this. For contracts of the specified condition, the user statuses and transitions that you created are available as Action menu items. You can use these action menu items to pass a contract between teams for review before submitting the contract for approval.

Note:

• User statuses and transitions apply only to contracts that satisfy the condition defined in the Event Model. They can't be used for contract templates.

• To create new events and actions, Oracle recommends you to use the existing event model instead of creating a new one.

This figure shows the user statuses and their transitions: