ProcessFlow WebRun job parameters

 4 Replies
 0 Subscribed to this topic
 52 Subscribed to this forum
Sort:
Author
Messages
Joe Haveman
Advanced Member
Posts: 31
Advanced Member

    I am looking to run a saved job by jobname/username.  This I can do.  For example....

    FUNC=run&JOB=TFBDIMPMIG&USER=sisco\pfadmin

    What I want to know is if you can add more URL parameters that would override the saved parameters in the named job.  For example, I have a job, AR580, that requires some dates before you can save the job.  What I want to be able to do is override a particular field.

    The Ctrl+Shift+O says the field is GL-DATE with id _f75.  So, can I do this?

    FUNC=run&JOB=TFBDIMPMIG&USER=sisco\pfadmin&GL-DATE=newdate

    or

    FUNC=run&JOB=TFBDIMPMIG&USER=sisco\pfadmin&_f75=newdate

    Any ideas?  Thanks in advance.

    David Williams
    Veteran Member
    Posts: 1127
    Veteran Member
      What I've done in the past is quick and easy - just update your job parameters via an AGS call before running it.
      David Williams
      Joe Haveman
      Advanced Member
      Posts: 31
      Advanced Member

        Thanks, David.

        What I really have is a 6-step multi-step job.  When setting up the multistep job, I have to save parameters just like a single job, for example, the AR580.

        Do you know how to do an AGS call to update the parameters in one of the jobs of the multistep job?  It's not like you create named jobs and then sequence the named jobs.  You simply reference the screens and supply parameters.

        Do you know how to update the parameters in a multistep job "on the fly" using PF?

        (What I'm trying to avoid is having to call the 6 named jobs individually.  If I don't know when a job is finished, then I won't know when to fire off the next job.  I know they fire fast and that webrun is asynchronous.)

        David Williams
        Veteran Member
        Posts: 1127
        Veteran Member
          I don't think you can update a multistep job that way but if I get a chance to play, I'll try.
          If you have to break out your reports into seperate WebRuns you can add &WAIT=true to the end of your jobrun command and the report you're running will finish before moving on to the next job.
          David Williams
          Joe Haveman
          Advanced Member
          Posts: 31
          Advanced Member

            That's perfect.  I'll try that and see the results I get.  I think I have tried the &WAIT=true and it didn't work.

            WILL DEFINITELY TRY AGAIN!

            So, my plan for now is to create the 6 jobs as named jobs, update them in PF using a transaction object and then run the 6 webrun's with &WAIT=true.

            This will answer all of my concerns for now.  Let me know if you had nothing better to do and was able to parameterize a webrun with dynamic fields.

            Thanks.