UPDATE: pete zerger was kind enough to point out that sometimes i don't make sense, and i missed a very obvious point in the documentation. since the post itself is still useful, i didn't just scrap it. :) instead, i added an addendum. if you've been working with opalis long enough, you might will find that there are moments when hacks are required to get you from one point to the next point. i've been experimenting a lot with nested workflows. it's like evolving from inline scripting to scripting with functions and/or subs. i discovered that when using trigger policy to run a nested workflow, a bizarre thing happens. even if the nested workflow executes with an error, the status returned by the calling trigger policy object is "success". it didn't make sense at first until i realized that by all accounts, the trigger policy did execute successfully. well, there's a problem with this. if it comes back as success, even though some
notes, ramblings, contemplations, transmutations, and otherwise ... on management and directory miscellanea.