When you get started with your Multiplay Subscription Management org, the workflows are configured to use the abstraction framework by default. However, if you want to use the same workflows on a different product model, if you want to extend the product model, or if you want to modify the workflows or create new workflows that use the abstraction framework, then you will need to update or extend the abstraction framework.
This feature is part of the Communications Cloud managed package.
-
To use the provided workflows with your own product model:
-
Ensure that the products, attributes, or fields for which you want to enter metadata already exist in your org. The Target name you enter in the custom metadata must match the attribute, product, or field name in your product model. Attributes must be related to the specified product.
-
Update the custom metadata to add or update your products, attributes, or fields. You can create new custom metadata records directly in your org, or you can enter the custom metadata records in a spreadsheet and then upload the data into your org using an upload tool. See Use Custom Metadata to Represent Your Product Model and Update the Custom Metadata for Your Product Model.
-
Refresh the cache. Use the option to clear the API response for the abstraction framework.
-
-
To extend the product model:
-
Create the required products, attributes, and fields in your org.
-
Enter the custom metadata for the new products, attributes, and fields. If you are making extensive updates, it might be easiest to enter the custom metadata for your current product model in a spreadsheet. You can then upload the data into your org using an upload tool.
-
Refresh the cache. Use the option to clear the metadata cache and API response for the abstraction framework.
-
If required, update the workflow components to support the new product model. This might be required if, for example, a workflow is expecting an attribute but in your product model the appropriate target would be a product. If you add new rows to the custom metadata table, you might need to update workflows that use an integration key to identify a target. In many cases, after updating the custom metadata to represent your product model, workflows can be used without making any changes in the core components.
-
For examples of extending the product model, see Modify an Existing Product Attribute in Multiplay Subscription Management (Managed Package) and Add an Attribute on an Existing Product in Multiplay Subscription Management (Managed Package).
-
-
To modify workflows or create new workflows that use the abstraction framework to interact with your product model:
-
Understand the abstraction framework Abstraction Framework Methods and Patterns, and Options for the Abstraction Framework.
-
Make any changes to your product model, as required.
-
Ensure that the custom metadata for your product model is in place and up to date. If you modified the product model, the custom metadata must be updated to point to the updated products, attributes, or fields.
-
Create or modify the required core components.
-
Use the abstraction framework methods, run options, and options to get information about the target and post the required updates.
-
- Modify an Existing Product Attribute in Multiplay Subscription Management (Managed Package)
Consider a scenario where you want to use most of the existing product model as it is, but you need to make a change in one of the product attributes. For example, let's say you want to change an attribute of the mobile services used in the Manage Features workflow. - Add an Attribute on an Existing Product in Multiplay Subscription Management (Managed Package)
Consider a scenario where you want to use most of the existing product model as it is, but you need to add an attribute on one of the existing products. For example, let's say you want to add an attribute to the mobile services used in the Manage Features workflow.