Setting up temporary Approvers

You can do this via the bpm pages, e.g.

http://server/bpm/views/userCategoryViewForm.do
http://server/bpm/views/userTaskViewForm.do

See this post, in which David Williams explains and provides some examples:
https://www.lawsonguru.co...v/topic/Default.aspx

Ineresting.  May take some time for me to wrap my head around that.  But will this work to add 165 new category values to a user/task?  Or do I have to run that WebRun 165 times, each time changing the variables?

You run WebRun 165 times, each time changing the variables?

I see.  And how is that better/faster than using the PF Admin tool?

A quick, down and dirty way to do this would be to run a query for the Category Filter values of the vacationer and use the WebRun to add the same values to the person covering for the vacationer. This is faster than manually keying those values in.

You could automate it vs doing it manually.

We have anticipated this problem before we migrated our environment from 803 to LSF9. What I did was to clone WF12, WF20, WF25 and WF46 into a new 4GL programs that will give my users temporary solutions until I come up with a more permanent solutions. This works well but it's not easy to just clone and compile. There are some tables that are gone in LSF9 and of course the cloning/changing of all the PD/SD libraries involved.

Right now I'm creating a new 4gl programs that will incorporate some calendars when approvers are on vacations. This is just a simple batch program that you enter the approver's RM-ID, date effective and end dates and category filters.

Under the User Task Definition, when you add your task, leave the filter category as No. That would give the CFO access to all requisition locations. If you don't want the person to have access to all location but too many to add manually, you could have your DBA insert the necessary values in the WFUSERCAT table in Logan.

What I did for another client was to create a Design Studio form that they could use to replace Approvers already set up - it would kick off a flow which would add the new Approver, assign the approval Tasks, assign the Category Filter values and then update Lawson Security so the Workflow flag was set to 1. When the Approver was set up it would then delete the filter values from the old Approver, remove their Tasks and change their Workflow flag to 0.

I also gave users the option of creating "Vacation" Approvers (including a start and stop dates). This flow would add the temporary Approver, assign their Tasks (with the start and stop dates) and assign the Category Filter values.

In the case when the temporary Approver already had the same approval Task then the extra Category Filter values would be added to their existing values and they would be assigned a new Task called "Vacation Coverage" - where they could into the Vacation Coverage Task and select the Inbasket Action to "End Vacation Coverage." This flow would remove the additonal Category Filter values and take off the "Vacation Coverage" Task.

And chance you'd be willing to share the .xml process flow file?

Jim
City of Nashua, NH

Email me at David@ConsultDavidW.com or david.williams@bailsllc.com and I'll shoot something over to you.

Thanks.  Sent over email.  Might want to edit those out your last post if possible so they don't get picked up by bots.

As the process Flow Admin, I had no desire to manage tasks at that level so I did the following:

1) Built a new form in Lawson (User ID, Name, Status)
2) Built a flow to update the users (LDAP -> New Lawson form)
3) Created another form called delegations where I lock the users ID and they can select any active user for coverage along with the coverage dates.
4) Updated the approval flow to read the delegations and if found push the approval to a special delegation UA

I've over simplified the steps but the end result is that the approver manages their own delegation. has worked great. (2+ Years and counting)