Prev
Next
Forums Integration / Customization IPA/ProcessFlow

Make PF less clicky

 5 Replies
 0 Subscribed to this topic
 52 Subscribed to this forum
Sort:
Author
Messages
mcissell
Basic Member
Posts: 7
Basic Member
7/21/2008 9:00 PM

    One of the major complaints that we have recieved from users is that PF is very 'clicky' in that users have to click into a workunit, click approve, go back to list, click another one etc...is there a way to have a summary page so users mass approve without clicking into every invoice/JE?

    Thanks,

    marty

    John Henley
    Posts: 3353
    7/22/2008 8:56 PM
      Re: Make PF less clicky (9962387b-5f7e-4656-91cf-785a6988e47b) <!-- Converted from text/plain format -->

      That's certainly an interesting idea, might be able to do something with Design Studio or something to show more concise pages.

      Alternatively, if your users are just routinely approving everything, why not just build some rules into your ProcessFlows to approve within reasonable limits, etc.?
      John Henley

      Thanks for using the LawsonGuru.com forums!
      John
      David Williams
      Veteran Member
      Posts: 1127
      Veteran Member
      7/23/2008 8:44 AM

        John is right - you could do this with Design Studio.  If you don't have Design Studio then you might want to look at something I've been playing with, including the approve/reject links within the body of the email notification sent to the approvers. 

        I've put this in place for one of my clients (not live yet) and they seem to like the option.  The only down side, as of right now you still have to log into Lawson for the Inbasket.do action to work.

        http://consultdavidw.blog...basket-dispatch.html

        David Williams
        mcissell
        Basic Member
        Posts: 7
        Basic Member
        8/25/2008 10:25 PM

          Thanks I will take a look at design studio and what you sent...

          mcissell
          Basic Member
          Posts: 7
          Basic Member
          9/1/2008 5:15 PM

            David, 

            I've looked at your blog and attempted to send the webrun code for the inbasket and I've gotten the following message returned:

            WORKDISPATCH wun="26187" returnmsg="Work Object not found for workUnit = 26187processId = 26187 activtyId = UserAction2880" msgtype="Warning" />

            so I think I'm not entering all of the information outlined in your blog...is TASK the same as the task that I assign to a user so they see the queue in their inbasket?  and is ACTNAME the same as the name of the useraction that I see when I am working in ProcessFlow?

            Thanks very much, if I can get this to work it would be a tremendous help,

            Marty

            David Williams
            Veteran Member
            Posts: 1127
            Veteran Member
            9/1/2008 5:27 PM
              Can you email me the HTML link you created? I can't tell from this what may or may not be missing. The WorkUnit is still pending, correct? There has to be something in the queue for this to work.

              ConsultDavidW@gmail.com
              David Williams