Create a PreRating Profile

A PreRating profile is a collection of PreRating callout actions and data modify actions. A PreRating action can belong to more than one PreRating profile.

About this task

A PreRating profile can contain:
  • A list of callout actions, where each action defines one of the following types of query:
    • MAP-ATI
    • MAP-SRI
    • MAP-INTERROGATE-SS
    • LDAP
    Note: For MAP call outs, to use selective updates to customize the callout object after it is in the message, you set Info Query Flags to Custom in the callout action. MATRIXX Support recommends that you include only one custom callout action in a PreRating profile. If multiple custom queries are attempted, only the result of the last query is stored.
  • A list of data modify actions, where each action specifies how to manipulate a selected field value in the MtxDiamRoMsg MDC, MtxTcapMsg MDC, MtxLdapRequestExtensionData MDC, or descendant of these MDCs, before the message is passed to rating.
You add PreRating profiles to PreRating generator tables. The profile selected during rating determines:
  • Which MAP call outs are performed.
  • Which LDAP call outs are performed.
  • Which pre-rating data is modified.
You can create an empty PreRating profile (one that does not have any callout or data modify action entries, and for which the Next Logical State field is not set) and add it to a PreRating generator table instead of a SKIP value. When an empty profile is selected during rating due to a decision table, no further PreRating actions are performed.

Procedure

  1. In PreRating, on the Profiles tab, click New Profile.
  2. In Create New PreRating Profile:
    1. In Name, enter a unique name.
    2. (Optional) In Description, enter descriptive information about the item.
    3. (Optional) In External ID, enter any alphanumeric character to serve as a unique ID on this pricing object. The external ID can be used for any reason that is meaningful to your implementation of MATRIXX Engine. External IDs are saved to the pricing configuration file and loaded into the Pricing database.
    4. Click Create.
  3. In Edit PreRating Profile, (if needed) change the general properties (the name, description, or external ID of the item) and click Save.
    Note: Any time you edit the value of a general property, you must click Save for your changes to take effect.
  4. (Optional) In Next Logical State, enter the next logical state value. You can enter any positive value except 0 (zero).
    If the Next Logical State field for the profile selected by the PreRating generator during rating is:
    • Set to a value – The service logic is forced to return to the generator logic to select a follow-on profile, even when all the call outs are answered successfully.
    • Not set – The service logic proceeds to rating if all the call outs are answered successfully.
    Note: The Next Logical State value is stored in the LogicalState field of the MtxDiamRoMsg MDC. The system initially sets the LogicalState field to 0 (zero), and that value is overwritten with the value from the Next Logical State field from the profile selected by the PreRating generator during rating. You can use the LogicalState field in normalizations in profile generator tables to help you to transfer information between calls to the PreRating generator. For more information about using the next logical state, see the discussion about using profiles with next logical state in MATRIXX Call Control Framework Integration
  5. Under Call Out Actions do one of the following:
    • To add an action, click Add Action, and do one of the following:
      • Select the row in the Add Call Out Action table for the action you want to add, and click Add.
      • Click Manage Objects to add a callout action or create a new one. For more information, see the discussion about managing added objects. To filter the list, enter criteria in Search.
      Note: You can add one or more callout actions to a PreRating profile. You must take care that each additional action does not query the same type of data for the same call party. For example, if you add an action to perform a MAP-SRI query for location data for the called party, do not add a subsequent action to perform a MAP-ATI query for location data for the called party. If you add two actions to a profile that query the same data, this could mean that when the MAP callout is performed, a successful result is overwritten with a failed result.
    • To delete an action, click Delete Icon next to the callout action you want to delete, and click Yes to confirm.
    • To change the order in which a callout action is listed in the table, click and drag it to a new position in the list.
  6. Under Data Modify Actions do one of the following:
    • To add an action, click Add Data Modify Action, and do one of the following:
      • Select the row in the Select Data Modify Action table for the action you want to add, and click Select.
      • Click Manage Objects to add a new data modify action or create a new one. For more information, see the discussion about managing added objects. To filter the list, enter criteria in Search.
    • To delete an action, click Delete Icon next to the action you want to delete, and click Yes to confirm.
    • To change the order in which a data modify action is listed in the table, in the ID column, click and drag the action to a new position in the list.
    You can add multiple data modify actions to the profile.
  7. Click Save to save your changes.
    Note: Whenever any sort of validation is run, the system checks the profiles for duplicate action sequences (that is, the same actions in the same order). If two profiles are found with the same action sequence (for example, a profile was created by copying an existing profile, but nothing was updated except the name), a warning displays listing the pair of profiles with this shared sequence so that you can determine if this was intentional.