Frequently Asked Questions (FAQ)

Get answers to these common questions about the Communications Cloud TM Forum APIs.

  • How can we create attribute categories?

    Use a default Attribute Category, which is pre-created and configured for use with TMF620 (assuming there is no hard-coding).

  • With respect to the price, how do we support cases such as attribute-based pricing? How does it relate to the payload?

    Attribute-based pricing is not handled by TMF620 specification. It requires custom extensions to support it.

  • Are there any extension points in TMF620 to add additional functionality (for example, support additional objects and fields in Salesforce)?

    Users can configure TMF fields to the customer desired fields by using Data Maptors for the corresponding API. Additionally, IP provides the flexibility for the customer to have their own implementation of the API method. With the custom metadata they can also change the VIP that they want to use for serving an API. We have also exposed the interfaces for certain resources to replace the business logic of the API methods.

  • For a product specification or offering, a customer has characteristics of datatype picklist. How can the customer figure out from the TMF 620 GET API on what's the selected value?

    The isDefault attribute is set to true for the selected value in the productSpecCharacteristicValue node within the response for TMF 620 GET API.

  • Are there any licenses required to use the Notification Framework?

    Notification framework is included as part of the Communications Cloud base Stock-Keeping Unit (SKU).

  • Which components must be configured by the customer to use the Outbound Notification Framework?

    The customer must configure the following components of the Notification Framework.

    • Resource (Object) API Name: The unique identifier of a specific entity within the system that triggers a notification. It links the notification to the resource, ensuring that any related events, updates, or actions trigger the appropriate notifications to designated users or systems.
    • Resource (Object) Field API Names: The API names of specific fields within the resource or object that, when modified, trigger a notification.
    • Integration Provider Definition: Defines the necessary details for connecting with external applications that will process the notifications, such as Mule APIs.
    • Change Event Type: Refers to the type of change that triggers a notification to customers. This could include actions such as the creation, update, or deletion of data related to a specific object. For more information see TMF Outbound Notifications Framework

  • Can customers configure CDC events based on selected fields of a given object within the Notification Framework?

    Yes, the Integration Provider Definition Mapping object allows customers to select the object and its fields. This configuration is applicable only for the update change event type.

  • Can customers configure the Notification Framework to trigger notifications based on specific change event types such as create, update, or delete related to a specific object?

    Yes, Customers can configure the Notification Framework to trigger notifications based on specific types of change events such as create, update, or delete related to a specific object.

  • Given Salesforce’s default limit of generating CDC events for only five entities, does this restriction also apply when customers use the Notification Framework?

    No, the CDC entity limit of five entities does not apply to the Notification Framework.

  • Are there any limits on the number of events that can be subscribed to via the Notification Framework?

    No, the number of CDC events limit does not apply to the Notification Framework.

  • Does the Notification Framework support triggering CDC events for all standard and related entities, if applicable? Are there any usage limitations?

    The Notification Framework is designed to support notifications for change events on all custom objects defined in a Salesforce org, as well as a subset of standard objects, as specified in the Change Event Object Support. For specific scenarios, we recommend consulting with your Salesforce account team to discuss any additional license requirements and ensure the solution is optimized for your use case.

  • Can customers enable notifications in the Notification Framework for custom objects?

    Yes, the Notification Framework supports the registration of custom objects.

  • Are outbound notifications triggered when changes such as updates, deletions, or additions are made to related objects?

    Currently, we support this functionality for notifications on changes to the Related Party Object for a given Contact. The Related Party Object is mapped to the AccountContactRelation (ACR) Object in Salesforce. An outbound TMF 632 notification is triggered from ACR in the these scenarios:

    • A new account is associated with a given contact.
    • An existing account for a given contact is updated.