1. Care to explain the interaction between interactions and operations, for the people who rae not that deep into them (or just forgopt ;-) ) ?
2. while working on this one thing that should be added to the current workflow events api is support for XA transactions: if an event at the end of the workflow ends in ABORT, the db transaction is currently rolled back, but the event handlers that previously executed get no chance to rollback their work
Principal Consultant International Business
Member of the Community Project Board
Bertrand Dunogier
Friday 14 January 2011 5:38:07 am
2) honestly, I can't add much more. I've already spent quite some time on this while it was unplanned, and really won't be able to fit more right now :(
1) which aspect exactly do you wish I elaborate upon here ? Just guide me, I'm a little slow today :)
About point 1: just general info about "operations" will do
- some operations have triggers (and thus can have workflows added to them), while some olthers do not declare triggers. Correct? The list of operations that have triggers is found in workflow.ini
- operations are grouped in modules; the ggsysinfo extension can be used to show all of the operations available on a given install
- operations are declared in a operation_definition.php file inside the module directory; every operation can consist of a series of php methods that will be invoked one after the other (eg. content/publish has 19 php methods in it)
- what are the expected return values for those php methods that are declared as part of oeprations, and how can they "interrupt" the operation?
Principal Consultant International Business
Member of the Community Project Board
You must be logged in to post messages in this topic!
