ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » Workflow Engines - IBM MQ Workflow & Business Process Choreographer » Updating a workflow container field

Post new topic  Reply to topic
 Updating a workflow container field « View previous topic :: View next topic » 
Author Message
Raffy
PostPosted: Tue Feb 15, 2005 1:41 pm    Post subject: Updating a workflow container field Reply with quote

Newbie

Joined: 01 Feb 2005
Posts: 6

Hi,

Is is possible to change the value of a container field and save it even if the work item's checkout status was canceled? If so, can anyone tell me how?

WF 3.4, AIX 5.2, WebClient

Here's the scenario

- the work item is checked out
- when the jsp is submitted, parameters are sent with the httprequest to update the global container fields
- the global container holds the new values but the work item's container fields still hold the old ones
- the process to save the work item as a draft is to cancel the checkout, which causes the global container values to be dropped.

for the last step, we want the work item's container values to be updated even the checkout was cancelled.

Hope I was able to explain the problem well.

Thanks,

Raffy
Back to top
View user's profile Send private message
jmac
PostPosted: Tue Feb 15, 2005 2:19 pm    Post subject: Reply with quote

Jedi Knight

Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC

What you can do is to checkin the workitem and have it fail its exit condition
_________________
John McDonald
RETIRED
Back to top
View user's profile Send private message Send e-mail Visit poster's website AIM Address Yahoo Messenger MSN Messenger
Raffy
PostPosted: Thu Feb 17, 2005 3:34 pm    Post subject: Reply with quote

Newbie

Joined: 01 Feb 2005
Posts: 6

What I ended up doing is to get the input container of the workItem as a ReadWriteContainer. I updated the fields then did a

wi.forceRestart2(ReadOnlyContainer)

I just wonder why there are no other means of updating the container of a workItem without having to forceRestart it or to check it in.
Back to top
View user's profile Send private message
jmac
PostPosted: Thu Feb 17, 2005 3:42 pm    Post subject: Reply with quote

Jedi Knight

Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC

Raffy wrote:
I just wonder why there are no other means of updating the container of a workItem without having to forceRestart it or to check it in.


Seems perfectly natural to me.... If the activity is in a Ready state (ie no one is working on it) why would you want the input container to change. The only reason is that you have bad data in the input container, and you need to change it, that would be the purpose of the container repair API forceRestart.
_________________
John McDonald
RETIRED
Back to top
View user's profile Send private message Send e-mail Visit poster's website AIM Address Yahoo Messenger MSN Messenger
Raffy
PostPosted: Thu Feb 17, 2005 3:52 pm    Post subject: Reply with quote

Newbie

Joined: 01 Feb 2005
Posts: 6

It might be due to the way we're using workflow. In the midst of working in a workItem, we have screens/processes that use one of the container fields as a key (policy number) to search a db for policy. Now in that workItem, we also have the ability to change the policy (thus the key). By this, we update the policy table with the new policy, but we also want to update the container field with the new policy number (which is the key I was talking about). If we don't update the container field and the user decides to cancel the workItem, then the database will have the new policy number and the workItem will have the old one. The next time the user resumes work on that workItem, he can no longer find the policy since the container field holds a policy no that no longer exists in the db.
Back to top
View user's profile Send private message
jmac
PostPosted: Thu Feb 17, 2005 3:58 pm    Post subject: Reply with quote

Jedi Knight

Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC

OK... So it seems to me that you want to do the forceResart due to the container Repair. I.E. for whatever reason the value in that particular container member must be changed. Now since an update to a container is never logged, it is necessary to do the forceRestart (which is logged). I hope this makes sense to you.

I am still a little confused though since you state
Quote:
In the midst of working in a workItem, we have screens/processes that use one of the container fields as a key (policy number) to search a db for policy
It seems to me that if you are "working" a workitem it must be checked out. So there is definitely something I am missing.... However, as long as you are happy, it doesnt matter
_________________
John McDonald
RETIRED
Back to top
View user's profile Send private message Send e-mail Visit poster's website AIM Address Yahoo Messenger MSN Messenger
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » Workflow Engines - IBM MQ Workflow & Business Process Choreographer » Updating a workflow container field
Jump to:  



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
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.