Create an Object State Update Profile

Create an object state update profile to extend, limit, or adjust the date/time value of the custom MDC field of an offer owner (Subscriber/Group/Device object).

Before you begin

You must have the Pricing User Domain role to create an object state update profile.

Procedure

  1. In Object State Update Profiles, click New Object State Update Profile.
  2. In Create New Object State Update 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 Offer Owner Container, select the container for the offer owner (Subscriber/Group/Device object) that contains the custom MDC field where the date/time value is stored.
  4. In Offer Owner Date/Time Field, select the custom MDC field where the date/time value is stored.
  5. In Start Date/Time, use the date picker to select the date on which the object becomes active in the Pricing database and is first available for use, or enter the date in the format YYYY-MM-DD. Optionally, enter a time for when the object becomes active. The default start date/time is 2000–01–01 00:00:00. If applicable, the range in which the start date/time must fall is listed. For example:
    • Select a date on or before 2021–12–01.
    • Select a date on or after 2020–01–27.
    • Select a date between 2000–01–02 and 2021–10–04.
    Note: If you are creating a new revision of this object, the start date/time must be after the start date/time of the preceding revision and before the start date/time of the next revision. If you are making a copy of this object, the start date/time is not copied. The new object is the first revision, so it has the default start date/time of 2000–01–01 00:00:00.
  6. In Extension Type, select the time from which to extend the date/time field value. Select from the following:
    • from_existing_time — Extends the date/time value from the current value in the custom date/time MDC field.
    • from_now — Extends the date/time value from the current date and time (now).
    • optimal — Extends from the existing object date/time field value if it is not in the past. Otherwise, extend from the current time (now). This option optimizes the date/time field extension.
    • optimal_offer_end_time — Extends the date/time value to the offer end time (plus some configured delay) if it is greater than the current date/time value. For example, if the offer end time plus the delay is greater than the current date/time field value, then the new date/time field value is equal to the offer end time plus the delay. Otherwise, the date/time field value is not modified.
    • optimal_cycle_end_time — Extends the date/time value to the cycle end time (plus some configured delay) if it is greater than the current date/time value. For example, if the cycle end time plus the delay is greater than the current date/time field value, then the new date/time field value is equal to the cycle end time plus the delay. Otherwise, the date/time field value is not modified.
    • optimal_before_offer_end_time — Extends the date/time value to some time units before the offer end time if the new date/time value is greater than the current date/time value. For example, if the offer end time minus the extension count is greater than the current date/time field value, then the new date/time field value is the offer end time minus the extension count. Otherwise, the date/time field value is not modified.
    • optimal_before_cycle_end_time — Extends the date/time value to some time units before the cycle end time if the new date/time value is greater than the current date/time value. For example, if the cycle end time minus the extension count is greater than the current date/time field value, then the new date/time field value is the cycle end time minus the extension count. Otherwise, the date/time field value is not modified.
  7. In Extension Amount:
    • If from_existing_time, from_now, or optimal is selected in Extension Type, enter the number of time units to extend the date/time field value. For example, to extend the date/time field value two weeks, enter 2 and for Extension Units (see step 8),select weeks.
    • If optimal_offer_end_time or optimal_cycle_end_time is selected in Extension Type, enter the number of time units that defines the delay added when extending the date/time field value to either the cycle or offer end time. For example, to add a delay of two weeks, enter 2 and for Extension Units (see step 8), select weeks.
    • If optimal_before_offer_end_time or optimal_before_cycle_end_time is selected in Extension Type, enter the number of time units that defines how long to extend the date/time field value before either the cycle or offer end time. For example, to add a buffer of two weeks, enter 2 and for Extension Units (see step 8), select weeks.
  8. In Extension Units, select the time unit that applies to the extension amount specified from the following:
    • Minutes (default)
    • Hours
    • Days
    • Weeks
    • Months
    • Years
  9. In Limit Amount, enter the number of time units to limit the date/time field value. The new date/time field value cannot be greater than the current time (now) plus the limit amount. For example, to limit the new date/time field value to no greater than now plus 24 months, enter 24 and in the next step, for Limit Units, select months.
  10. In Limit Units, select the time unit that applies to the limit amount specified from the following:
    • Minutes (default)
    • Hours
    • Days
    • Weeks
    • Months
    • Years
  11. In Extension Limit Policy, define the policy for handling extension limits. Choose from the following:
    • allow_limited_extension — Allow the extension up to the specified limit. This is the default.
    • deny_limited_extension — Deny any extension if the specified limit is exceeded.
  12. In Reduction Policy, define the policy to handle reductions in the date/time field value. For example, whether the new date/time value can be less than the current field value. Choose from the following:
    • allow_reduction_up_to_now — Allow the reduction of the current date/time field value up to the current time. This is the default.
    • deny_reduction — Deny any reduction of the current date/time field value.
    Note: The date/time field value can only be reduced down to the current time (now); it cannot be set to the past.
  13. In Time Adjustment Type, select the adjustment type for the time portion of the date/time value in the custom MDC field. Select from the following:
    • no_change — Keep the time setting of the date/time field value. This is the default.
    • end_of_day — Extend to end of the day.
    • absolute_time — Extend to the time specified in this profile. Enter the time in the format hh:mm:ss. The default time is 00:00:00.
  14. Click Save.