Manual operations

A manual operation is an operation that requires approval by a manager before it is executed. The following operations can be approved manually:

  • Operations with subscriptions (stopping and deleting). The manual mode for these operations can be configured in an account class (see Creating an account class) and service term (see Creating a service term). When a manual operation is created for a subscription, the subscription gets the Waiting for manual approve status, its Auto-renewal option is turned off, and the Disable the Auto-renew option option is turned on. The platform stores the previous status of the subscription and these options.

    If the manual mode of stopping or deleting is set for a subscription both in an account class and service term, only one manual operation is created.

  • Ordering the first postpaid subscription to a commercial period (see Managing account's permission to use the Postpay model).
  • Operations with application instances (installing, starting, stopping, updating, renewing, and deleting). The manual mode for these operations can be configured for application templates based on the Manual Provisioning plugin (see Creating a connector based on the Manual Provisioning plugin and the Plugin Settings tab in Viewing and updating connector details). When a manual operation is created for an application instance, the linked subscription gets the corresponding "transitional" status (see Viewing the list of subscriptions).
  • Operations with auction domains (auction domain provisioning). In the current version, the support of operations with auction domains is limited.

Late processing of manual operations can cause incorrect working of credit hold, credit limit, billing, activation, stopping, and renewal of subscriptions, and can lead to incurring of debt to a vendor.

In this section: