com.ibm.commerce.marketing.commands.elements

Class CustomerFilterOrderTargetTaskCmdImpl

  • All Implemented Interfaces:
    CustomerFilterOrderTargetTaskCmd, MarketingCampaignElementTaskCmd, com.ibm.websphere.cache.Sizeable, com.ibm.websphere.command.CacheableCommand, com.ibm.websphere.command.Command, com.ibm.websphere.command.CommandCaller, com.ibm.websphere.command.TargetableCommand, java.io.Serializable


    public class CustomerFilterOrderTargetTaskCmdImpl
    extends CustomerFilterOrderTargetBase
    implements CustomerFilterOrderTargetTaskCmd
    This command evaluates if the products contained within a shopping cart were added to the cart within the specified dates, and are within the specified dollar amount and product quantity. This class evaluates if products were purchased within the specified dates, and are within the specified dollar amount and product quantity.
    See Also:
    Serialized Form
    • Field Detail

      • COPYRIGHT

        public static final java.lang.String COPYRIGHT
        IBM copyright notice field.
        See Also:
        Constant Field Values
      • CLASSNAME

        public static final java.lang.String CLASSNAME
        The name of this class.
        See Also:
        Constant Field Values
    • Constructor Detail

      • CustomerFilterOrderTargetTaskCmdImpl

        public CustomerFilterOrderTargetTaskCmdImpl()
    • Method Detail

      • performExecute

        public void performExecute()
        This method evaluates the total value of a shopping cart and the quantity of order items that were added to the cart within the specified dates, and are within the specified dollar amount and product quantity. This method evaluates the purchase history and the quantity of orders purchased within the specified dates, and are within the specified dollar amount and product quantity. The following parameters need to be provided in the task command parameters:
        • type Specify "sc" to check the user's shopping cart, or specify "ph" to check the user's purchase history.
        • containsOperator The indicator for whether the customer's behavior should have, or should not have the data being checked. Valid values are: =, !=
        • daysOperator The operator to use when checking if this behavior has occurred within or prior to a number of days. Valid values are: =, <, <=, >, >=. However, from a business point of view, only <= (within) and > (prior) make sense. There is a special case for the purchase history target to specify that only a specific number of previous orders should be checked. In that scenario the daysOperator is equal to previousOrders, and daysValue is the number of previous orders to consider. The other date parameters are not valid when previousOrders is used.
        • daysValue When has this behavior has occurred; within or prior to the specified number of days.
        • dateOperator1 The operator to use when checking if this behavior has occurred on, before, after or between a specified date. Valid values are: =, <, <=, >, >=.
        • dateValue1 When has this behavior has occurred; on, before, after, or between the specified date.
        • dateOperator2 The operator to use when checking if this behavior has occurred on, before, after or between a specified date. Valid values are: =, <, <=, >, >=.
        • dateValue2 When has this behavior has occurred; on, before, after, or between the specified date.
        • amountOperator1 The operator to use when checking the total value or the user's orders. The orders can be the current shopping cart, or the user's purchase history. Valid values are: =, <, <=, >, >=.
        • amountValue1 The value to check against the total value of the user's orders.
        • amountOperator2 The operator to use when checking the total value or the user's orders. The orders can be the current shopping cart, or the user's purchase history. Valid values are: =, <, <=, >, >=.
        • amountValue2 The value to check against the total value of the user's orders.
        • amountCurrency The currency of the specified amount values in which to compare.
        • quantityOperator1 The operator to use when checking the quantity of the user's orders. The number of unique orders items are checked in the current shopping cart, and the number of orders are checked in the user's purchase history. Valid values are: =, <, <=, >, >=.
        • quantityValue1 The number to check against the quantity of the user's orders.
        • quantityOperator2 The operator to use when checking the quantity of the user's orders. The number of unique orders items are checked in the current shopping cart, and the number of orders are checked in the user's purchase history. Valid values are: =, <, <=, >, >=.
        • quantityValue2 The number to check against the quantity of the user's orders.
        This method sets the task command return value to true if the user's orders match the specified criteria, otherwise it sets the task command return value to false.
        Specified by:
        performExecute in interface com.ibm.websphere.command.TargetableCommand
        Overrides:
        performExecute in class MarketingCampaignElementTaskCmdImpl
      • validateParameters

        public java.util.List validateParameters(java.util.Map elementParameters)
        This method validates that all the required name value pairs have been set for the campaign element. It checks for the existence of one of the following: days, date1, amountValue1, quantityValue1.
        Specified by:
        validateParameters in interface MarketingCampaignElementTaskCmd
        Overrides:
        validateParameters in class MarketingCampaignElementTaskCmdImpl
        Parameters:
        elementParameters - The name value pairs for this element.
        Returns:
        This method returns a list of ApplicationError exceptions that contains any validation errors. The list may be empty or be null.