Pricing, Policy, and Rating

Balances and Meters

• Added the option Report Highest Threshold Breaches Only to balance and meter templates to support a single notification and Event Detail Record (EDR) to be generated when multiple thresholds are crossed on a single balance or meter. For more information, see the discussions about configuring balance and meter template thresholds in My MATRIXX Help.
• Added the options Threshold Cycle Notification Limit and Threshold Cycle Event Limit to balance and meter templates to define how often you want notifications and events for the same threshold to be triggered during a cycle. For more information, see the discussions about configuring balance and meter template thresholds in My MATRIXX Help.
• Notifications and events for a given balance threshold can be triggered multiple times indefinitely. In My MATRIXX you can configure how often you want threshold notifications and events for the same threshold to be triggered during a cycle. For more information, see the discussion about threshold re-triggering in MATRIXX Pricing and Rating.

Catalog Items

• Added the Pricing Provision Policy to catalog items to define the criteria used to find revisions of pricing objects to use during rating. For more information, see the discussion about configuring catalog item general properties in My MATRIXX Help.

Data Modify

• The following MATRIXX data containers (MDCs) are now available for data modify sources and destinations:
  • Mtx5GChargingDataRequest
  • Mtx5GChargingDataResponse
  • Mtx5GSpendingLimitRequest
  • Mtx5GSpendingLimitResponse
  • MtxDiamGxCCMsg
  • MtxDiamSySLMsg
  • MtxPolicySessionExtension

  For more information, see the discussion about data modify actions (DMAs) in My MATRIXX Help.

• For 4G diameter policy messages GxCC and SySL, data modify actions (DMAs) can now read from an MtxPolicySessionObject and any extension and write to the MtxPolicySessionObject extension. For 5G diameter policy message Mtx5GSpendingLimitRequest, DMAs can now read from an MtxPolicySessionObject and any extension and write to the MtxPolicySessionObject extension. For more information, see the discussion about DMAs in My MATRIXX Help.

Discount Scoping

• Discount scoping specifies which charges are applied in the scope of offers, purchased items, and purchased packages. Discounts above the event initiator and discounts in global offers are considered, along with discounts in global offers, for both usage and non-usage operations. For more information, see the discussion about options to apply scope in My MATRIXX Help.

General Ledger Processing

• General Ledger (GL) processing and posting utilities now accept a tenant ID argument so that there can be separate handling of GL data for each tenant (multi-tenancy). For more information, see the discussion about GL utilities in MATRIXX Integration.

Normalizers

• Added the Tier Parameter option to the following normalizers to allow retrieving a balance, MDC field, or group tier (as appropriate for the normalizer) from a tier parameter.
  • Balance Difference
  • Balance Distribution
  • Closed User Group
  • Difference Range

  For more information, see the discussions about each normalizer type in My MATRIXX Help.

• The Phone Number Pattern Match and Zoning normalizers now support importing and exporting normalizer rows and values. For more information, see the discussion about importing and exporting normalizer rows and values in My MATRIXX Help.

Notifications

• You can now add optional information (metadata) per notification in a notification profile that is included in the notification payload (MtxNotificationProfileData). For more information see the discussion about notifications in My MATRIXX Help.
• In addition to notification profiles, now you can create notification profile selectors. Use notification profile selectors to dynamically create different notifications in advance of scheduled subscription and group life cycle state changes. Each scheduled notification can have configurable metadata that is included in the notification.

  You can configure a notification profile selector to include a set of notifications that apply to all tenants or you can select a different profile for each tenant. When filtering by tenant ID, you can specify that some notifications are sent only to specific tenants. Filtered notifications can apply to every prior-to event, on event, or after event profile. For information about creating notification profile selectors, see the discussion about notifications in My MATRIXX Help.

  You can assign notification profile selectors to offer and status life cycles. For information about offer and status life cycle configuration, see the discussions about offer and status life cycles in My MATRIXX Help.

  New pricing validation error codes for notifications in offer and status life cycles include:

  • 57056 — Error if NotificationProfileSelectorId and NotificationProfileId are both set. Only one can bet set at a time.
  • 57057 — Error if referencing an invalid MtxProfileSelector.

Product Offers

• When defining a required balance on a product offer in My MATRIXX, you can select a tier parameter from all parameters set up in pricing.
• A group can purchase a product offer when the Charge Only Required Balances product offer general property is set. When this option is set, if multiple instances of the same offer are purchased in the same group, each offer instance only uses and charges its required balance instances.

  If a subscription belongs to two or more groups, and each group contains one or more instances of the same offer when this option is set, each offer instance only uses and charges its required balance instances.

• It is now possible for Required Balances in product offers to use the Catalog Item Parameter for specifying the balance's tier name. It is now possible for Grant Price components that grant to tier to use the Catalog Item Parameter for specifying the balance's tier name.

For more information, see the discussion about balances in My MATRIXX Help.

Pre-Active Purchased Items

• My MATRIXX provides the following options for when a pre-active purchased item cannot be activated at the specified auto activation time:
  • Use the new MtxStatusConditionAutoActivationTimeFailure offer life cycle status condition to transition the purchased item to an inactive state.
  • Use the new Auto Activation Time Recurring Failure Allowed pricing option to transition the purchased item to a grace or recoverable state to stop further attempts to activate it. This option is selected when configuring product offer and bundle cycle data.

  For more information about offer life cycle status transitions, product offers, and bundles, see My MATRIXX Help.

• The following notification types are available for pre-active purchased item auto-activation by time failure:
  • subscriber_bundle_auto_activation_time_failure
  • group_bundle_auto_activation_time_failure
  • device_bundle_auto_activation_time_failure
  • subscriber_offer_auto_activation_time_failure
  • group_offer_auto_activation_time_failure
  • device_offer_auto_activation_time_failure
  • subscriber_purchase_package_auto_activation_time_failure
  • group_purchase_package_auto_activation_time_failure
  • device_purchase_package_auto_activation_time_failure

  For more information about notification types, see the discussion about notification types in My MATRIXX Help.

• One of the following notifications is generated when scheduled activation fails:
  • MtxBundleAutoActivationTimeFailureNotification
  • MtxOfferAutoActivationTimeFailureNotification
  • MtxPurchasePackageAutoActivationTimeFailureNotification
• The following notifications are generated when recurring failure is allowed and scheduled activation succeeds but recurring processing fails.
  • MtxRecurringFailureNotification
  • MtxPurchasedItemStatusChangeNotification

  For more information about notifications, see the discussion about the MATRIXX notification framework in MATRIXX Integration.

• MtxPurchasedItemActivationFailureEvent is generated when scheduled activation fails.
  The following events are generated when recurring failure is allowed and scheduled activation succeeds but recurring processing fails.

  • MtxPurchasedItemActivationEvent
  • MtxRecurringFailureEvent
  • MtxPurchasedItemStatusChangeEvent

  For more information about events, see the discussion about the MATRIXX event detail records in MATRIXX Integration.

PreRating

• When creating a PreRating LDAP callout action, if you want the LDAP query to override the parameter from the LDAP Gateway query for the LDAP server, you can now enter a string starting with FILTER=. For example, FILTER=(mobile=${0}). For more information about configuring PreRating, see My MATRIXX Help.