Job Req Trigger PA42

 3 Replies
 0 Subscribed to this topic
 52 Subscribed to this forum
Sort:
Author
Messages
Roger French
Veteran Member
Posts: 549
Veteran Member

    Trying for some input from others here.

    We currently have PA42 set up so when a job req is created a new processflow/work unit will be triggered.

    For another reason, I'm trying to design a process where I have a processflow which will create a new job req in PA42 using the AGS call. But, I don't want it to create a new (second) work unit from that PA42. Is there any way I can set up or call the PA42 from a processflow where it does NOT create a new work unit? I thought about creating a copy of the PA42 and using that (and removing the trigger parameters/service, etc. from it) to do the job.

    Thanks in advance,

    Roger

    David Williams
    Veteran Member
    Posts: 1127
    Veteran Member
      You might be able to create a QuickPaint copy of PA42 in jobdef and have your AGS call hit that form instead. I would think though if you have ProcessFlow enabled that your form copy would more than likely trigger PF too.
      Another option is to build your flow to check the WF-RM-ID on the WorkUnit and if it was created by Lawson then approve the job req right away and end your flow. It will create that extra WorkUnit, but it won't tie up your job req and it's a lot easier than custom programming.
      David Williams
      Gary Davies
      Veteran Member
      Posts: 248
      Veteran Member

        PA42 only triggers a workunit for job req's in a WFINPROG status. Create a new status for your PF created reqs (like PFINPROG).  If you need them to be in WFINPROG status that add a second AGS call to change the status to WFINPROG with the hidden field FROM-WORKFLOW set to Y.  When that field is Y it does not create a workunit on a Change only.

        Gary Davies
        Veteran Member
        Posts: 248
        Veteran Member

          PA42 only triggers a workunit for job req's in a WFINPROG status. Create a new status for your PF created reqs (like PFINPROG).  If you need them to be in WFINPROG status that add a second AGS call to change the status to WFINPROG with the hidden field FROM-WORKFLOW set to Y.  When that field is Y it does not create a workunit on a Change only.

          Gary Davies

          www.automated-workflow.com