It sounds like he is wanting to create a virtual "doorbuster". I guess what I was trying to get at is that he is going to have to have some sort of check on userLoginHistory or visits. I was thinking of having an EECA so that when the appropriate entity has a create then a service is ran that goes through the entity and looks at a window of entries and gathers statistics on it. This information will need to be stored somehow so he can use those in his promo rules. Information like this visitor is the nth unique visitor in the the x time frame.
He will need to make entries in the enumeration entity mimicking something like PPIP_PARTY_ID, but instead something like PPIP_VISIT_ATT. Then, in ProductpromoCond he could have an entry inputParamEnumId=PPIP_VISIT_ATT, operatorEnumId=PPC_EQ, and condValue=whatever. He will have to look at ProductPromoWorker.java and see how the framework utilizes all of this stuff. I haven't had time to trace out the code to see if this is logical, but perhaps it will give him a little guidance. -CJ
