1. Implementing Subscription Management
  2. Set Up User Statuses and User Transitions for Subscriptions

Set Up User Statuses and User Transitions for Subscriptions

A subscription has predefined statuses that characterize its life cycle. In addition, you can define user statuses and their transitions.

For example, as a subscription specialist, you may want to pass the subscription for a more thorough review by the appropriate team, such as Legal, Financial, and Accounts. You can do this using the user statuses and transitions that you define.

To define user and status transitions:

  1. Define user statuses and their transitions using the Manage Subscription User Statuses and Transitions task.

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

  2. Use the Event Models tasks from the Subscription Configuration work area to create new events and actions for the business object oracle.apps.subscriptionManagementsubscriptionService.view.SubscriptionsVO. You need to be in active sandbox to edit an existing event model.

    1. Add a new state associated with the new user status, to the appropriate event model. The action associated with the Entry event of the new state is then set to update the user status code to the new user status.

    2. Add any other possible events for this new state.

    3. Link to the existing state by adding a new event for the Draft state, so that your new status is available for a subscription in the Draft status.

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

  4. Save this new state-based event model and specify the condition that can use it. For subscriptions of the specified condition, the user statuses and transitions that you create are available as Actions menu items. You can use these action menu items to pass a subscription between teams for review, before submitting the subscription for approval.

User statuses and transitions apply only to subscriptions that fulfill the conditions defined in the Event Model.