Once the Approve or Reject action is selected a browser window will open confirming the action taken (the user may have to enter their Lawson userid and password).
Email Inbasket Dispatch
By referencing two of my previous posts - Email HTML Content and Inbasket Action I was able to design the email below so that approvers can view and select the Action they want to take on a ProcessFlow task.
Once the Approve or Reject action is selected a browser window will open confirming the action taken (the user may have to enter their Lawson userid and password).
Once the Approve or Reject action is selected a browser window will open confirming the action taken (the user may have to enter their Lawson userid and password).
Design Studio Portal Page DME
Have you used the Checkbox on your Portal page DME to allow users to select records? A recent client asked me to design a portal page that would display PO agreements that are going to expire during the current month and allow users to select which ones to extend an additional month.
That was fairly easy to do until they asked me to include a button that would allow them to select all of the displayed records. After playing a bit, here's what I came up with.
That was fairly easy to do until they asked me to include a button that would allow them to select all of the displayed records. After playing a bit, here's what I came up with.
Email HTML Content
ProcessFlow 9 allows the use HTML Content in the Email node.
That means you can use HTML code to format the look of your email. I decided to test this by creating the HTML code within my MsgBuilder and referencing that in my Email with the HTML Content flag checked.
That means you can use HTML code to format the look of your email. I decided to test this by creating the HTML code within my MsgBuilder and referencing that in my Email with the HTML Content flag checked.
Number of WorkUnits Displayed
Thanks to Jeff Bolding for bringing this to my attention. If you would like to display more than the standard 10 WorkUnits in your Inbasket you can Add a User Preference value (yes, you have to do this for each user).
You can use always create a flow to Query all of your Users and a WebRun to add this setting to each one:
Web Program: bpm/userPrefForm.do
Post String: method=Add&id=davidwil&systemName=INBASKET&fieldName=NBRWORKUNITS&description=Number of WorkUnits Displayed&fieldValue=20
Inbasket Action
I've had a couple of clients who were reviewing lines of items (requisition or invoice cost messages) and wanted to work individual lines by exception (reject line 3 of 20) but then take the same action for the remaining lines (approve).
I've done this before by processing the action for all of the remaining lines and then closing the remaining open WorkUnits but if you have another level of approval needed then you have to pass those lines of items to another flow... or you can do the following:
Use a Query to get the remaining WorkUnit, Process Id and UA Id's and then use a WebRun to send the Action to the remaining lines. Using this method is a lot easier.
Web program: bpm/Inbasket
Post String:
FUNCTION=dispatch&WORKUNIT=133&TASK=Level1&APPRODLINE=LAW9WRK&RDUSER=lawson&PROCID=133&PROCNAME=rqapproval_V04&ACTID=UA112&ACTNAME=Level1&ACTION=Approve
I've done this before by processing the action for all of the remaining lines and then closing the remaining open WorkUnits but if you have another level of approval needed then you have to pass those lines of items to another flow... or you can do the following:
Use a Query to get the remaining WorkUnit, Process Id and UA Id's and then use a WebRun to send the Action to the remaining lines. Using this method is a lot easier.
Web program: bpm/Inbasket
Post String:
FUNCTION=dispatch&WORKUNIT=133&TASK=Level1&APPRODLINE=LAW9WRK&RDUSER=lawson&PROCID=133&PROCNAME=rqapproval_V04&ACTID=UA112&ACTNAME=Level1&ACTION=Approve
ProcessFlow Admin for non-PF people
My client doesn't have a ProcessFlow Admin yet so they needed a way for Purchasing to update the Approver setup without going into the ProcessFlow Admin Tool.
We modified the WFWK.2 form to make it easier to submit one of two flows to either replace an Approver or to add vacation coverage for an Approver.
In one the user can enter the Id of an Approver who is gone and the Id of the person replacing them. The flow will look up all of the Tasks of the old approver and the category filtering for each task and delete these from them and add them to the new approver. The flow also updates Lawson Security (Resource Update node) with the email of the new approver and sets the WFUser flag to "1" so the Inbasket will display.
The 2nd option is for vacation coverage. The user will enter the Id of the person going on vacation and the person covering for them. The flow will build the Task/Category Filter as needed for the coverage approver with the start and stop dates of the vacationer.
If, however, the coverage approver is already an approver then you know that you can't add the same Task a 2nd time (if the Approver is "Level1" you can't add a 2nd "Level1" with start and stop dates). To account for this we built the flow so that it would add the category filter items to the existing ones and create a new "Vacation" Inbasket Task.
Once the vacationing approver is back the coverage approver will go into this Vacation Inbasket and select "End Coverage". The flow will then remove the category filter items from their existing ones and remove the Vacation Task from their Inbasket.
We modified the WFWK.2 form to make it easier to submit one of two flows to either replace an Approver or to add vacation coverage for an Approver.
In one the user can enter the Id of an Approver who is gone and the Id of the person replacing them. The flow will look up all of the Tasks of the old approver and the category filtering for each task and delete these from them and add them to the new approver. The flow also updates Lawson Security (Resource Update node) with the email of the new approver and sets the WFUser flag to "1" so the Inbasket will display.
The 2nd option is for vacation coverage. The user will enter the Id of the person going on vacation and the person covering for them. The flow will build the Task/Category Filter as needed for the coverage approver with the start and stop dates of the vacationer.
If, however, the coverage approver is already an approver then you know that you can't add the same Task a 2nd time (if the Approver is "Level1" you can't add a 2nd "Level1" with start and stop dates). To account for this we built the flow so that it would add the category filter items to the existing ones and create a new "Vacation" Inbasket Task.
Once the vacationing approver is back the coverage approver will go into this Vacation Inbasket and select "End Coverage". The flow will then remove the category filter items from their existing ones and remove the Vacation Task from their Inbasket.
Subscribe to:
Posts (Atom)