This article will walk you through:
- the purpose of the Billing System Update Action.
- use case examples for the Billing System Update Action.
What is the Billing System Update ACTION?
The Orders module allows you to create and begin processing for an order containing services and features. The items contained within the order are not added to the customer’s accounts as part of the order entry process. This is done so that if you have some back and forth with the end subscriber, you can continue to modify the order and not display the items on the account until the order has been finalized.
The Billing System Update action adds the services and features to the customer’s account.
As with most actions, parameters are needed so that the Workflow module can successfully run the action. For the Billing System Update action, the parameters are:
| Name | Description | Default Value | Required |
| CartID | This value represents the CartID that should be used when running the action. This parameter has a default value and it is recommended that users do not modify/override the default value. | @[CartID] | No |
| Service Processing Action | This value represents the group of services that are contained is a split group for service processing actions (aka adds, disconnects, etc.). This parameter has a default value and it is recommended that users do not modify/override the default value. | @[SplitGrouping.ServiceAction] | No |
| Service Catalogs | This value represents the group of services that are contained is a split group for service catalogs (aka service types). This parameter has a default value and it is recommended that users do not modify/override the default value. | @[SplitGrouping.ServiceCatalog] | No |
| Service Items | This value represents the group of services that are contained is a split group for service items (aka services). This parameter has a default value and it is recommended that users do not modify/override the default value. | @[SplitGrouping.ServiceInformationItem] | No |
Using the Billing System Action
The Billing System Update adds the services and features to the customer’s account. We recommend waiting to run this action until the services have been implemented for the customer. We also recommend that this action be later in your process configuration so that you can take advantage of the ability to modify an inflight order. (We define an inflight order as an order that has been submitted but not completed or cancelled).
Workflow Instances That Do Not Contain a Splitter Step
When the Billing System Update action is runs successfully for a workflow instance that does not contain any splitter steps:
- all services and features contained within the order will be added to the customer’s account and;
- the entire order will be locked down, prohibiting further modifications.
Workflow Instances That Contain a Splitter Step
When the Billing System Update action runs successfully for workflow instance that contains a splitter step; the action will:
- only add the services and features associated with the split group to the customer’s account and;
- only lock down the services and features associated with the split group. All other services and features contained within the order will remain editable.
The Orders module has been updated to provide a visual indicator so that you can quickly identify which items are read only vs editable within the order. In the example below, the Hosted PBX and POTS service can still be modified but the Toll-Free service has been locked down and is read only.
