Refer to Permissions for any permissions that may be required.
The following is a quick overview of the setup required (with links to details):
Configure data lists and settings that need to be in place before you begin working with Provisionable Object Definitions and Profiles. This includes:
Provider Settings – This is where you add IDI-supported Providers (e.g. Metaswitch or Calix) in your Provisioning application. Versioning is supported such that one carrier may use Calix 1.0 (1.0.31) and another carrier may use Calix 1.0 (1.0.32).
Lists - Lists are one source of data you can use to configure a POD property definition. A List is set to a specific data type (e.g. integer or text) and contains values of that type that you add to the list. When you define a POD property as a List, it makes the field a drop down menu for choosing a value contained within the List. Some Lists are provided as standard, and you can add custom Lists as needed.
Variables - Variables are another data source similar to Lists. Rather than enter values directly, Variables can be used to set property values on PODs based on SKUs assigned to the service.
Safeguard Settings - This is used to limit the items (Allowed Internal IDs) sent in a provisioning request. It is intended to be used in non-production environments to avoid disrupting existing services when you test your provisioning setup.
Global Information – Is a potential data source for populating Profile parameters. Global Information is similar to Extended Data in a Workflow, and may be used where the same value may be used in multiple Profiles.
These elements are available via the MANAGE menu in the Provisioning web application.
Show Picture
Configure Provisionable Object Definitions – This is where you associate the object with one or more SKUs and specify the properties to be sent with a provisioning request for the associated SKU(s).
Configure Profiles – This is where you map PODs to a Provider and provisioning action.
Add provisioning steps in Workflow – This is where you embed Profiles as steps in a Workflow.