Re-route to new User Inbasket

 4 Replies
 0 Subscribed to this topic
 52 Subscribed to this forum
Sort:
Author
Messages
Vito Amatulli
Advanced Member
Posts: 33
Advanced Member
    I am fairly new to Processflow an I am looking for a recommendation on how best to approach this issue. Our Procurement Dept would like to have a Re-Route Action on certain requistions (> $5000,0000).  It  would open up a new form and they could select the user and have the work go to the new user inbasket for approval. I was able to create a customized version of WF02.1 and was trying to lauch the URL from the UserAction Node but I am getting the Exec List cannot exceed 99 characters. I am not sure if that is going to work the way I want it to. Has anyone else come across this issue? Any suggestions would be appreciated 
    Gary Davies
    Veteran Member
    Posts: 248
    Veteran Member
      This is assuming 9.0:

      I have done this for a couple of clients, one that wanted to reroute Invoice approaval, Using Design Studio I created a dropdown list of the available authority codes to reroute and a Reroute action. Within the DS from if they selected a new auth code I called the bpm form to write the new category value. In the flow on the reroute action I reset the oCatValue, sent the new inbasket users an email and went back into the UserAction node. I works great.
      Vito Amatulli
      Advanced Member
      Posts: 33
      Advanced Member
        Gary, thanks for the quick response.  How did you call the DS studio fprm from the User Action? I am struggling with the 99 character limitation of the Exec List. I add a re-route action to the exiting user action node and I am trying toc all the DS form but it the call is too long. Here is the call that I created:

        http://drfulawd1.corpdev1...dex.htm?_URL=LAWFORM|PDL=LOGAN|TKN=WF02.1|ID=WFPX
         
        if you have a sample that you can share with me, that would be great.
        Gary Davies
        Veteran Member
        Posts: 248
        Veteran Member
          I am saying use the Display Exec, not the Exec lists

          Inbasket displays can be html or Design Studio forms. If you are using design Studio you would create a Portal Page that has your custom form as an element, you then would create a custom form with the javascript to update the drop down built within the Script tab.

          You can accomplish the same thing within an html if that is what you are using to display in the inbasket, same principle, within the html create a dropdown list and when it is changed make an http request to the bpm form workUnitVariablesForm.do

          if you are using html then all you put in the Display Exec is the html name (ex. dispPO.htm), it has to reside on the $LAWDIR/bpm/execs directory and be deployed in Websphere (again in 9.0 environment, if you are 8.0.3 it is different). If you do a design studio form you just need to specify the name of the Portal Page created (example poapproval.xml). Processflow knows to look in the Design Studio for the display because the filename ends with .xml

          When you use Exec Lists, that basically executes the html you specify after the action is taken, the problem is that the flow does not wait for whatever you execute to finish before it continues on in the flow. This process is meant for providing additional functionality after the fact (such as adding a comment to a table or creating email content to send a customized notification). Using the Exec list does not fit well with what you are trying to do.

          KHessing
          Basic Member
          Posts: 10
          Basic Member

            I am trying to do this same thing. But in addition, the users are wanting the auth code in table APINVOICE to be updated to the new auth code for auditing purposes. PFI has new capability to update tables but no update permissions on this table. Any thoughts on how I can update table? Thanks much!