All, We had one story in which we added a workflow step called electronic_signature_disagreed. The criteria for this story was when someone disagreed to a document, it would make workflow exit. electronic_signature_disagreed was a NoOpParticipant (for logging purposes) and the last step in a workflow path before the process exited.
The follow up story added additional workflow paths after electronic_signature_disagreed. The electronic_signature_disagreed step turned into a Ruote::StorageParticipant and waited there for further instructions. What happened when we deployed was upon receiving a message to proceed from electronic_signature_disagreed to the next step, our code which advanced the workflow to the next step started raising "no such method query for Ruote::NoOpParticipant". I triple checked and electronic_signature_disagreed was indeed defined as a StorageParticipant. This issue was resolved by renaming the electronic_signature_disagreed step to electronic_signature_disagree. Does this sound like a bug in Ruote or expected behavior for changing a Participant implementation? Doug -- 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
