Author |
Message
|
ajomillar |
Posted: Wed Dec 17, 2003 9:43 am Post subject: dynamic assignment problem |
|
|
 Centurion
Joined: 22 Aug 2003 Posts: 121 Location: Milwaukee, WI
|
I'm running MQWF 3.4 SP3 on a PC where my user id is the administrator. The same user is registered in WF in the admin role. To test the process, I send WF XML messages to the EXEXMLINPUTQ. I use WF "fat" client as well.
The process has a single program activity that dynamically assigns the work to a user based on a container value (a user defined element is mapped to _ACTIVITY_INFO.People). The user exists in Runtime. While the work item appears on my userid worklist, the work item never appears on the intended user's worklist. In the WF client, I have to transfer the work item to the user -- just to get it on their worklist. Is there something I should check to make this work? |
|
Back to top |
|
 |
Ratan |
Posted: Wed Dec 17, 2003 9:57 am Post subject: |
|
|
 Grand Master
Joined: 18 Jul 2002 Posts: 1245
|
Quote: |
The process has a single program activity that dynamically assigns the work to a user based on a container value |
.
Where are you doing the user assignement?
Is it from Process start node to the activity input container? _________________ -Ratan |
|
Back to top |
|
 |
ajomillar |
Posted: Wed Dec 17, 2003 10:13 am Post subject: |
|
|
 Centurion
Joined: 22 Aug 2003 Posts: 121 Location: Milwaukee, WI
|
Yes. From the source node (origin data structure) to the activity input container (target d/s), I map from an element in _STRUCT called "officeid" to the _ACTIVITY_INFO.People. Our userbase consist of offices, so I use their office id number as virtual users. I assume the WF XML MQMD.UserIdentifier is the process starter, but why doesn't the work item get assigned to the intended user? |
|
Back to top |
|
 |
Ratan |
Posted: Wed Dec 17, 2003 10:20 am Post subject: |
|
|
 Grand Master
Joined: 18 Jul 2002 Posts: 1245
|
Did you select "Staff from predefined members" on staff 1 page? _________________ -Ratan |
|
Back to top |
|
 |
ajomillar |
Posted: Wed Dec 17, 2003 10:50 am Post subject: |
|
|
 Centurion
Joined: 22 Aug 2003 Posts: 121 Location: Milwaukee, WI
|
No. "Dynamic assignment from page 2" is selected. In the Staff 2 tab, I selected "Office" (that's the virtual user) in "Member of roles from container." |
|
Back to top |
|
 |
jmac |
Posted: Wed Dec 17, 2003 11:00 am Post subject: |
|
|
 Jedi Knight
Joined: 27 Jun 2001 Posts: 3081 Location: EmeriCon, LLC
|
Post the FDL for the process AND the Roles/Persons involved, and maybe I can spot your problem _________________ John McDonald
RETIRED |
|
Back to top |
|
 |
ajomillar |
Posted: Wed Dec 17, 2003 11:03 am Post subject: |
|
|
 Centurion
Joined: 22 Aug 2003 Posts: 121 Location: Milwaukee, WI
|
Here's the FDL with process and user:
Code: |
CODEPAGE 1252
FM_RELEASE V3R4 0
/*
* PERSONs
*/
PERSON '1234'
DESCRIPTION ""
AUTHORIZED_FOR PROCESS_CATEGORY 'EMWF'
PASSWORD %8C988E2A0862D59FCEE489F9562D195E
IS_NOT_ABSENT
DO NOT RESET_ABSENT
GROUP 'FMCGRP'
SYSTEM 'FMCSYS'
END '1234'
/*
* PROCESSes
*/
/*
* PROCESS CustomerIseError_v1
*/
PROCESS 'CustomerIseError_v1' ( 'CustomerError', 'Default Data Structure' )
CATEGORY 'EMWF'
DO NOT PROMPT_AT_PROCESS_START
WINDOW VIEW_REFERENCE_POINT XPOS 0 YPOS 162
WINDOW SHOW ALL CONNECTORS
WINDOW SHOW NO CONDITIONS
SOURCE 1 XPOS -700 YPOS 300
PROGRAM_ACTIVITY 'CustomerError' ( 'CustomerError', 'Default Data Structure' )
DESCRIPTION "CustomerError"
START MANUAL WHEN AT_LEAST_ONE CONNECTOR TRUE
EXIT AUTOMATIC
LAYOUT XPOS -200 YPOS 300
NAME_POSITION XPOS -200 YPOS 225
PRIORITY DEFINED_IN INPUT_CONTAINER
DONE_BY MEMBER OF ROLE TAKEN_FROM 'Office'
PROGRAM 'NShowCustomerError'
SYNCHRONIZATION NESTED
END 'CustomerError'
DATA
FROM SOURCE 1 TO 'CustomerError'
MAP 'Office' TO '_ACTIVITY_INFO.People'
MAP '_STRUCT' TO '_STRUCT'
END 'CustomerIseError_v1'
|
|
|
Back to top |
|
 |
jmac |
Posted: Wed Dec 17, 2003 11:11 am Post subject: |
|
|
 Jedi Knight
Joined: 27 Jun 2001 Posts: 3081 Location: EmeriCon, LLC
|
There is no need for you to move Office to _ACTIVITY_INFO.People based on the way your FDL is defined, but I don't think it is hurting anything.
Are you saying that the Value in Office is "1234" in the input container of the "CustomerError" activity? Check this using the ThinClient Monitor. If that is the case then there must be a bug, and it's probably time for you to open a PMR _________________ John McDonald
RETIRED |
|
Back to top |
|
 |
Ratan |
Posted: Wed Dec 17, 2003 11:18 am Post subject: |
|
|
 Grand Master
Joined: 18 Jul 2002 Posts: 1245
|
If the value in office is '1234', isnt it wrong? '1234' is a person while the activity is defined to be done by member of role '1234'. _________________ -Ratan |
|
Back to top |
|
 |
ajomillar |
Posted: Wed Dec 17, 2003 11:24 am Post subject: |
|
|
 Centurion
Joined: 22 Aug 2003 Posts: 121 Location: Milwaukee, WI
|
Yes, the value in Office is 1234 from the input container. I don't know what the ThinClient Monitor is. When I open the Workflow fat client, and monitor the process instance, I open the activity properties to view the Staff tab...On the worklist of me, Process Administrator: me. Everything else appears OK with the FDL? If so, then I'll open a PMR on this one. Thx! |
|
Back to top |
|
 |
jmac |
Posted: Wed Dec 17, 2003 11:32 am Post subject: |
|
|
 Jedi Knight
Joined: 27 Jun 2001 Posts: 3081 Location: EmeriCon, LLC
|
Look at what Ratan is saying.... You should be specifying Done by Person from container, not Role from container. I didnt catch that when I looked at it, thats why its so great to have Ratan around  _________________ John McDonald
RETIRED |
|
Back to top |
|
 |
ajomillar |
Posted: Wed Dec 17, 2003 11:40 am Post subject: |
|
|
 Centurion
Joined: 22 Aug 2003 Posts: 121 Location: Milwaukee, WI
|
Ratan -- you are correct. Office doesn't define a role, just a person. My oversight...I selected Office in the "People from container" from program activity's Staff 1 setting, then put the WF XML to the queue. Now, the work item is assigned to the correct user. I just checked the client and the owner is 1234. Thx, jmac, for the insights and assistance. |
|
Back to top |
|
 |
|