I'm currently evaluating the Galaxia Workflow Engine - which appears to me as the "lightest" yet "most powerfull" engine available out there as Open Source (congratulations guys - in order to make it my company's core workflow management system.
Now, I haven't been able to find any information on how to deal with 'expiration'-set activities (though this seems to have been provisioned in the source code and the administration GUI). More to the point:
- How do they get executed "operator-independantly" ?
- SPECIFICALLY, is there an *existing* PHP script I shall add to my server's CRON ?
- OR Should I make my own ?
- IF SO, where is the most appropriate "entry point" to trigger the execution of the expired activity ?
EDITED is "galaxia_execute_activity" (which in turn "fopen"s tiki-g-run-activity.php) the best candidate ?
- ALSO, how do I handle activity decision in the PHP code (for "switch" activities) in case of an "automatically-expired/ended" activity (is there some flag that indicates this situation or shall I "hack" the _REQUEST variable to "guess" it) ?
EDITED if "galaxia_execute_activity" is the way to go, is the "auto" variable the flag I'm looking for ?
Automatic handling of expired activities is one of my key requirement ? Any clues on how to handle this with Galaxia (1.9.5) would be very much appreciated !
Thanks for your help ! (and "Bravo" again for your work)