| Author |
Message
|
| ajomillar |
 Posted: Thu Dec 11, 2003 1:58 pm Post subject: Implementing manual work item with noop activity |
 |
|
Centurion
Joined: 22 Aug 2003
Posts: 121
Location: Milwaukee, WI
|
| I want to WF XML messages to generate work items in the Ready state. Using a custom web client, the user will click the item to indicate they are working on something (Running state?), then click on the same item to indicate they are completed (Finished). At that point, the item disappears from the worklist. It may sound elementary but I'm having trouble figuring how this is done with a noop activity. I know that the noop activity must be setup with automatic start and stop, but how can I implement this manual activity? |
|
| Back to top |
|
 |
| jmac |
| Posted: Thu Dec 11, 2003 2:47 pm Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
The NOOP activity (FMCINTERNALNOOP) must be defined as Automatic... What is it you are trying to do?
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
| ajomillar |
| Posted: Thu Dec 11, 2003 3:11 pm Post subject: |
|
|
Centurion
Joined: 22 Aug 2003
Posts: 121
Location: Milwaukee, WI
|
| The user has a manual step to perform -- that requires no call to external program. The input data container is exposed to display necessary info to complete the manual work item and that is all. However, we want to be able to show the different states to the user. It's like a todo list. If they step away from the desk, they can pick up later where they left off. |
|
| Back to top |
|
|
| jmac |
| Posted: Thu Dec 11, 2003 3:23 pm Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
It seems to me that you want a "normal" jsp activity. Data is displayed when user checks out... User does something, pushes CheckIn button, MQWF navigates to next activity.
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
| ajomillar |
| Posted: Thu Dec 11, 2003 10:34 pm Post subject: |
|
|
Centurion
Joined: 22 Aug 2003
Posts: 121
Location: Milwaukee, WI
|
Yes, something along those lines...I've not experimented with the API checkIn or checkOut commands yet. When I tested the process (it has a single program activity) in the Workflow Client, it was Ready but then went to InError when I started it. As you noted, the NOOP activity must be defined in Automatic. However, In the scenario you mentioned, could the sequence of states be: Ready --> CheckOut --> CheckIn --> Finished (while defined as Automatic). If this avoids the InError state (and our team's web developer can graphically represent checkIn/checkOut states), then I'm a happy camper  |
|
| Back to top |
|
|
| jmac |
| Posted: Fri Dec 12, 2003 5:54 am Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
I am sorry, but I really do not understand what you are saying.
You have a model w/ 1 activity, make it manual start. Assuming you are using the thin client, when you start an instance, that will show up on the appropriate Worklist (Ready state); Your user "starts" (ChecksOut) the item (assuming you have not written a JSP the IBM code kicks in and generates one for you) the screen is displayed (Running state); User puses "CheckIn" button (Finished state). Unless you told MQWF to save finished activities and instances the instance will now be gone from your worklist and instancelist
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
| ajomillar |
| Posted: Fri Dec 12, 2003 1:03 pm Post subject: |
|
|
Centurion
Joined: 22 Aug 2003
Posts: 121
Location: Milwaukee, WI
|
Sorry about the confusion...your patience is appreciated.
Here's the whole story:
1. WBI Broker is processing messages from a front office system. Rules are applied in a message flow and generates the appropriate WF XML messages.
2. WF XML message creates/starts a process instance. This instance represents specific errors for a particular front-office message. [The process template contains a single step: merely to display the error info by exposing the input data container. However, this is not set in stone. ]
4. The user opens the web client and views these in their worklist.
5. The user places a checkmark next to each work item to indicate they have reviewed or are in process of correcting the error (the "todo list" approach) in the front office system. A graphic will indicate the current state (some items are checked, while others are not).
6. Assuming the new message passes the rules, a new WF XML message will be sent from Broker to terminate the existing process instance. Thus, removing the workitem from the user's worklist.
In this scenario, the user really never "finishes" the work until they perform an action on the front office system to trigger new WF XML messages. In some cases, this will result in simply terminating the process instance; while in others situations, new error info will need to be displayed (Broker will propagate 2 WF XML: terminate existing instance and create/start instance). Does this make sense? |
|
| Back to top |
|
|
| jmac |
| Posted: Fri Dec 12, 2003 1:36 pm Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
I think I now understand what you are doing and it does make sense. The only thing is that you will need to modify the Out of the box worklist to make it function like you are indicating.
GOOD LUCK
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
| ajomillar |
| Posted: Fri Dec 12, 2003 2:24 pm Post subject: |
|
|
Centurion
Joined: 22 Aug 2003
Posts: 121
Location: Milwaukee, WI
|
| We'll give it a try. Thanks for the help. |
|
| Back to top |
|
|
| ajomillar |
| Posted: Fri Dec 19, 2003 8:59 am Post subject: |
|
|
Centurion
Joined: 22 Aug 2003
Posts: 121
Location: Milwaukee, WI
|
| Still working on the manual work item issue...Just wondering if anyone can provide sample FDL for a simply process that doesn't call any programs (similar to NOOP). I'm looking for something that acts like a glorified checklist. I'm trying to implement a simple workflow that involves a single activity (the user manually reviews a record) and have the states transition from Ready to Running. A web client will present the work item and the user will check each Ready item. After marking a checkbox, they hit a submit button and each of the related items are started (API call) then the state changes to Running. |
|
| Back to top |
|
|
|
|
