On Thu, Jun 16, 2011 at 07:19:17AM -0700, eric smith wrote: > > Back story > I have a process below used for contract approval. Once the contract > is submitted it goes to an attorney and then to two approvers who are > both required. The two approvers need to be able to submit questions > back to the attorney or two each other. If a question is submitted > then we need to send a email to all parties with the current "thread" > for the discussion. When a workitem is created we send emails to the > participants with the ide to access the workitem. We don’t want to > change the workitem untill we have captured the approval, so that we > do not have to issue them a new token to access the workitem. > > I can see several ways that we might approach the problem, but they > all seem like we are fighting the ruote pattern. > > 1.) When create the comment we need to a propagate the comment to all > workitems ( should we use a process variable for this ?) > 2.) When we spawn a "comment" email for each participant what should > we use to fire the event if we don’t want to proceed a given workitem. > ( listen or cron, etc )
Hello Eric, what about separating the comments from the workitems ? Your workitem could reference to the thread resource. You could pass the workitems as some kind of access token and let the real commenting work happen in the thread/email system. Best regards, -- John Mettraux - http://jmettraux.wordpress.com -- you received this message because you are subscribed to the "ruote users" group. to post : send email to [email protected] to unsubscribe : send email to [email protected] more options : http://groups.google.com/group/openwferu-users?hl=en
