• Search Forums
    Advanced Search Topics Posts
Prev
Next
Forums User Experience Lawson Design Studio

Accessing Inbasket Variables

 4 Replies
 0 Subscribed to this topic
 12 Subscribed to this forum
Sort:
Author
Messages
Vito Amatulli
Advanced Member Send Private Message
Posts: 33
Advanced Member
7/26/2009 10:01 PM

I am faily new to Design Studio and I am trying to figure out how to access Inbasket variables.  I put the portal in debuig mode and was able to determinre the variables that are being returned.

I have attached the XML that is returned.

I can access all variables under the WUVARIABLE tag by using the page.paramters method. I am trying to access the wun=19580 variable in the WORKDETAIL
or the the WORrKUNIT variable in the FOLDRADDURL tag. Any suggestions?


Attachments
David Williams
Veteran Member Send Private Message
Posts: 1127
Veteran Member
7/26/2009 10:28 PM
You can use a DME to access the WUVARIABLE table and get the variables you want.
David Williams
Vito Amatulli
Advanced Member Send Private Message
Posts: 33
Advanced Member
7/27/2009 1:22 PM
I am trying to get the workunit number from the Inbasket and pass it to a Portal Page so I present the user with a custom screen that will allow certain power users to re-route to a new inbasket. I was able to do  DME call successfully but how do I pass that value to my custom screen using the Formlet tag

LET id="WFPX" TITLE="JM Family - Change Inbasket" col="0" row="720" height="300" width="800" border="0" scroll="1" zindex="0" ahide="0" refresh="1" src="_PDL=LOGAN&_TKN=WF02.1&_ID=WFPX" interval="0" tp="frmlt"/>
Steven Gray
Advanced Member Send Private Message
Posts: 21
Advanced Member
9/15/2009 5:23 PM
So, for a Portal Page Inbasket, how do you get the WorkUnit? It is visiable in the XML, but does not seem to be part of the values available using page.parameters method.
Steven Gray
Advanced Member Send Private Message
Posts: 21
Advanced Member
2/17/2010 2:25 PM

After further research,

I found the MESSAGEADDURL element as part of the object parent.pfInbasket.curWorkObjDetail, and was able to extract the WORKUNIT using this method. It should work the same for the FOLDERADDURL.  Oddly, I could not locate an element for WORKDETAILS, but I'm sure it's out there somewhere.
 

Here's an edited version of your trace data. 

< INBASKET >
  < WORKDETAILS wun="19580" approdline="DEV50" returnmsg="OK" msgtype="normal" >
    < FOLDERADDURL >< CDATA [ /bpm/inbasket?FUNCTION=workdetail&RDUSER=ipsesy1
       &WORKUNIT=19580&APPRODLINE=DEV50&UPTYPE=FLD&UPDTACTION=A&FLDNAME=&FLDURL= ] >
    < MESSAGEADDURL >< CDATA [ /bpm/inbasket?FUNCTION=workdetail&RDUSER=ipsesy1
     &WORKUNIT=19580&APPRODLINE=DEV50&UPTYPE=MSG&UPDTACTION=A&MSGID=&MSGCONTENT= ] >
 

// get MESSAGEADDURL node value
var vElements = parent.pfInbasket.curWorkObjDetail.getElementsByTagName("MESSAGEADDURL");
vMesssageAddUrl = vElements[0].firstChild.nodeValue;
// extract WorkUnit parm using a portal method
vWorkUnit = portalWnd.getVarFromString("WORKUNIT",vMesssageAddUrl);
alert("WorkUnit is " + vWorkUnit);