We have an enhancement Request regarding the “Wait” functionality that is used in Offer Flows. Currently this value can only be a constant value ( 2days, 3 hours, etc…). However depending on conditions this period should be a variable. Instead we are forced to manage wait periods via implementing decision tables, which may become quite challenging.
We have the following use case:
Customer has an NBO strategy that prioritize offers that is manually run by business users sometime between 9am and 11am.
There are 2 channels. Call Center and Email.
When pyChannel = Call Center, Customer want’s to create a list via “Generic Treatment” as soon as the flow is triggered.
When pyChannel = Email, Customer want’s to send emails however NOT anytime before 11am.
To fulfill this requirement we built the following Offer Flow.
Since the NBO Strategy can start anytime between 9am and 11am, we cannot set a constant wait period for email Treatment to make sure that it starts at 11am sharp. We used a decision table to calculate the “CurrentTime – NBO Run Time” to identify the wait period. (Just made 30 minute gaps for the sake of the example). If NBO is run at 9am, we wait for 2 hours before sending emails. If NBO runs at 10:30am, we wait for 30 minutes before sending emails.
If the wait period could be either an expression or a constant value, we could assign the wait period on the run. Something like:
**Moderation Team has archived post**
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.