Question
Vodafone Hungary
IN
Last activity: 8 May 2024 12:08 EDT
Automation of Campaign Run without scheduling
Dear Team ,
We are running the daily campaigns as a BAU after the Beaver Data flow run. There are 5 campaigns which will run on a daily basis. So we are planning to automate the campaign run without scheduling . Because if campaigns are scheduled , if first campaign got delayed the second campaign will start in-between. So to avoid that we need a help where if I trigger the campaign and if first campaign gets completed and then the second campaign have to start similarly until it gets completed. Can you please help here because team is working on day-night.
Thanks in advance
Hari
Accepted Solution
Updated: 8 May 2024 12:08 EDT
Pegasystems Inc.
GB
To create automated sequential execution of campaigns, you can customize the activity that is executed after every Multi-Channel and Outbound Campaign Run. This activity can be overridden in the implementation layer to trigger the next campaign after the completion of the previous one. However, it's important to be careful not to impact the execution lifecycle of the run. Please note that any commits in the call chain of this activity may impact the lock on the primary page. If performing operations that require a commit, make sure to re-acquire the lock on the primary page by doing an Obj-Refresh-And-Lock at the end of this activity.
You can automate the sequential execution of campaigns by using a campaign listener. This can be achieved by customizing the activity that is executed after every Multi-Channel and Outbound Campaign Run. This activity can be overridden in the implementation layer to trigger the next campaign after the completion of the previous one. However, it's important to be careful not to impact the execution lifecycle of the run. Please note that any commits in the call chain of this activity may impact the lock on the primary page. If performing operations that require a commit, make sure to re-acquire the lock on the primary page by doing an Obj-Refresh-And-Lock at the end of this activity.
⚠ This is a GenAI-powered tool. All generated answers require validation against the provided references.
To create automated sequential execution of campaigns, you can customize the activity that is executed after every Multi-Channel and Outbound Campaign Run. This activity can be overridden in the implementation layer to trigger the next campaign after the completion of the previous one. However, it's important to be careful not to impact the execution lifecycle of the run. Please note that any commits in the call chain of this activity may impact the lock on the primary page. If performing operations that require a commit, make sure to re-acquire the lock on the primary page by doing an Obj-Refresh-And-Lock at the end of this activity.
You can automate the sequential execution of campaigns by using a campaign listener. This can be achieved by customizing the activity that is executed after every Multi-Channel and Outbound Campaign Run. This activity can be overridden in the implementation layer to trigger the next campaign after the completion of the previous one. However, it's important to be careful not to impact the execution lifecycle of the run. Please note that any commits in the call chain of this activity may impact the lock on the primary page. If performing operations that require a commit, make sure to re-acquire the lock on the primary page by doing an Obj-Refresh-And-Lock at the end of this activity.
⚠ This is a GenAI-powered tool. All generated answers require validation against the provided references.
campaign listener to trigger action before or after a campaign execution
EclatPrime
IN
We are looking for a similar process where we want to automate the campaign runs with the help of an API call.
Is there a solution to this question?
Accepted Solution
Updated: 8 May 2024 12:08 EDT
Pegasystems Inc.
GB
To create automated sequential execution of campaigns, you can customize the activity that is executed after every Multi-Channel and Outbound Campaign Run. This activity can be overridden in the implementation layer to trigger the next campaign after the completion of the previous one. However, it's important to be careful not to impact the execution lifecycle of the run. Please note that any commits in the call chain of this activity may impact the lock on the primary page. If performing operations that require a commit, make sure to re-acquire the lock on the primary page by doing an Obj-Refresh-And-Lock at the end of this activity.
You can automate the sequential execution of campaigns by using a campaign listener. This can be achieved by customizing the activity that is executed after every Multi-Channel and Outbound Campaign Run. This activity can be overridden in the implementation layer to trigger the next campaign after the completion of the previous one. However, it's important to be careful not to impact the execution lifecycle of the run. Please note that any commits in the call chain of this activity may impact the lock on the primary page. If performing operations that require a commit, make sure to re-acquire the lock on the primary page by doing an Obj-Refresh-And-Lock at the end of this activity.
⚠ This is a GenAI-powered tool. All generated answers require validation against the provided references.
To create automated sequential execution of campaigns, you can customize the activity that is executed after every Multi-Channel and Outbound Campaign Run. This activity can be overridden in the implementation layer to trigger the next campaign after the completion of the previous one. However, it's important to be careful not to impact the execution lifecycle of the run. Please note that any commits in the call chain of this activity may impact the lock on the primary page. If performing operations that require a commit, make sure to re-acquire the lock on the primary page by doing an Obj-Refresh-And-Lock at the end of this activity.
You can automate the sequential execution of campaigns by using a campaign listener. This can be achieved by customizing the activity that is executed after every Multi-Channel and Outbound Campaign Run. This activity can be overridden in the implementation layer to trigger the next campaign after the completion of the previous one. However, it's important to be careful not to impact the execution lifecycle of the run. Please note that any commits in the call chain of this activity may impact the lock on the primary page. If performing operations that require a commit, make sure to re-acquire the lock on the primary page by doing an Obj-Refresh-And-Lock at the end of this activity.
⚠ This is a GenAI-powered tool. All generated answers require validation against the provided references.
campaign listener to trigger action before or after a campaign execution