| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Transfer Function in Web Client |
« View previous topic :: View next topic » |
| Author |
Message
|
| drgincbia |
 Posted: Tue Dec 23, 2003 7:52 am Post subject: Transfer Function in Web Client |
 |
|
Apprentice
Joined: 23 Dec 2003
Posts: 35
Location: Omaha NE
|
Instead of having a message box pop up to key in a userID for the person to transfer the workitem to, our customer wants to have a drop down list of userID's / names of eligible resources that are authorized to receive the workitem. They would then select from this list for the transfer. This capability is needed from the worklist view and a customer application (jsp). Any suggestions on how to access the data to populate in this list?
_________________
D. Grandia |
|
| Back to top |
|
 |
| jmac |
| Posted: Tue Dec 23, 2003 8:22 am Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
Have a look at the Person object and it will be obvious how to get the names.... HOWEVER, note that if a Person is authorized to ALL other persons there is no way to get the names.
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
| ucbus1 |
| Posted: Fri Dec 26, 2003 6:04 am Post subject: |
|
|
Knight
Joined: 30 Jan 2002
Posts: 560
|
Just to add to what John already mentioned:
(BTW john helped me on this forum for the same problem we wanted to solve)
We have to modify ListViewer.jsp, which can be found at
\Program Files\MQSeries Workflow\cfgs\(Your webclient configuration)\WebClient\webpages\forms.
Check the authorizations for user say ("TESTMGR").
Then get personsAuthorizedFor: for ("TESTMGR").
For each personId in personsAuthorizedFor list get the firstname, lastname, middlename using persistentPerson(personID)
Put each id in Treemap
end for
1.Easiest way to implement the above changes is to modify ListViewer.jsp and restart the "web client" web application, if you are using Websphere. Taking backup of original ListViewer.jsp is strongly recommended.
2. The solution works for users of type "TESTMGR" who has authorization for partial list of users. In the case of "ADMIN" (System administrator) type users who are authorized for "ALL" staff, the solution does not give the list of "ALL" users. This is not the limitation of the solution but this is how the personsAuthorizedFor function in MQWorkflow works. Please see workflow programming guide
PersonsAuthorizedFor()
Returns the persons for whom this person is authorized either explicitly or by being a substitute. If the person is authorized for all other persons, then no person is returned here.
3. The user "TESTMGR" needs to have " AUTHORIZED_FOR STAFF" authority.
This authorization can be set in build time. When defining the person under build time see to that the check box "Staff definition" under "Authorizations" tab is checked. Make sure the exported FDL contains "AUTHORIZED_FOR STAFF".
Also, be aware that the solution is an ineffiecient way of implementation
Thanks |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
