| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Thin client and Process Instance state |
« View previous topic :: View next topic » |
| Author |
Message
|
| RJoubert |
 Posted: Thu Jun 06, 2002 11:33 am Post subject: Thin client and Process Instance state |
 |
|
Apprentice
Joined: 30 May 2002
Posts: 43
Location: Buffalo, NY
|
In the thin out-of-the-box application, when it displays work items and determines which buttons to show, it is unable to determine the state of the process instance (ExecutionState_Undefined). Therefore, when I am logged in as the user who the work item is assigned to (not ADMIN), the start button does not show up.
However, when I log into the thick runtime client (as that same user), I am able to start the work item. The thick client is also able to determine the process instance state, since it displays it.
Is this just due to coding shortfalls in the thin client code, or is it actually impossible to access the process instance state using the COM API and ASP/VBScript?
_________________
Rich Joubert
Computer Systems Engineer
Univera HealthCare, an Excellus Company |
|
| Back to top |
|
 |
| steinra |
| Posted: Thu Jun 06, 2002 2:11 pm Post subject: |
|
|
Apprentice
Joined: 23 May 2002
Posts: 28
Location: USA
|
Which "thin" access are you using? The webclient or a different one?
Randy |
|
| Back to top |
|
|
| jmac |
| Posted: Thu Jun 06, 2002 2:19 pm Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
Are you talking about the Java based (JSP) thin client, or the one provided with the COM api?
If you are speaking of the Out of the Box, I assume you are talking JSP based, since the COM api is an extra cost option. You seem to be mixing Process Instance with WorkItem.
Please give a more detailed explanation of your question and perhaps we can assist.
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
| RJoubert |
| Posted: Fri Jun 07, 2002 3:30 am Post subject: |
|
|
Apprentice
Joined: 30 May 2002
Posts: 43
Location: Buffalo, NY
|
I am referring to the thin client that comes with the COM API. More specifically, the Workflow.INC file...in the DoListWIActionButtons method, the workitem state is evaluated. In our case it evaluated to a 1 (Ready state). Within that case, the state of the corresponding process instance is evaluated. In the Runtime client, it shows up as Running and allows us to start the workitem. But, when we printed out the pi.state value in the ASP code (added a response.write in the workflow.inc to show pi.state), it returned a 0, which is ExecutionState_Undefined.
It may just be a bug, but I'd be interested to know if whether or not it is even possible for the COM API to evaluate the state of the process instance.
Thanks.
_________________
Rich Joubert
Computer Systems Engineer
Univera HealthCare, an Excellus Company |
|
| Back to top |
|
|
| steinra |
| Posted: Fri Jun 07, 2002 7:45 am Post subject: |
|
|
Apprentice
Joined: 23 May 2002
Posts: 28
Location: USA
|
I am sorry to say I have not worked with the COM Api yet.
Wish I could help.
Randy |
|
| Back to top |
|
|
| jmac |
| Posted: Fri Jun 07, 2002 8:27 am Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
Questions on the COM api should probably be posted to the IBM MQWF Newsgroup, as I am not aware of a lot of use of this product yet.
_________________
John McDonald
RETIRED |
|
| 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
|
|
|
|
