Adobe Campaign Classic Scheduler | Community
Skip to main content
N
nithin2015
January 15, 2020
Solved

Adobe Campaign Classic Scheduler

  • January 15, 2020
  • 2 replies
  • 7128 views

Hello Community,

In this scenario we are trying to pull data from adobe cloud and save it in AWS S3 bucket as a pipe delimited file.

  • In the current situation the Scheduler is just grabbing everything from the DataBase and storing it in the S3 bucket...
  • Every-time it run's, The data transfer has to start from where it has left out and grab from that date onwards.
  • Should the Incremental query has to be linked to a Scheduler in order to define the execution frequency of the workflow, and therefore the query ?
  • How can we do it in a workflow ? 
This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Amit_Kumar

Hi Nitin,

 

You should use scheduler available within the incremental query activity.

If this is not possible for some reasons then you can use scheduler +JS to keep track of the last execution date and a standard query activity to use that execution date from JS in a workflow.

 

Regards,

Amit

2 replies

Amit_Kumar
Amit_KumarAccepted solution
Level 10
January 16, 2020

Hi Nitin,

 

You should use scheduler available within the incremental query activity.

If this is not possible for some reasons then you can use scheduler +JS to keep track of the last execution date and a standard query activity to use that execution date from JS in a workflow.

 

Regards,

Amit

    N
    nithin2015Author
    January 17, 2020

    Hi Amit, But can we determine where it left off and how are we going to store and read that value without doing any coding is their any custom code which we can refer ?

    wasim09
    Adobe Employee
    wasim09Adobe Employee
    Adobe Employee
    January 18, 2020

    Hey Nitin,

    let me reiterate the problem.

    1. let's say customer wants to extract the data from 1st Jan to till now [18th Jan] and first time workflow was ran on 14th hence the data till 14th was exported.

    2. Next time workflow ran on 15th so rather than sending out the data from 1-15 Jan, you want to export the data post 14 Jan[ last execution] but before 15 Jan, right?

    solution:

    create a option with name last run

    once this is created put a scheduler and write a js code to read the option.

    1.schedule to trigger the workflow everyday.

    2. JS code- read option and store last run date and also getCurrentdate() on two separate event variable.

    3.pass the last run date in query activity like : last modified data on or after $datetime(vars/@lastRepDate)

    4. Once done then update the option using code: setOption(vars.optionName, vars.nextRepDate); // added on end activity advanced tab.

     

    wasim

     

    Terms & ConditionsAccessibility statement

    Loading footer...