Workflow

Changes for version 0.32_5 - 2008-11-13

Fixed regular expression in t/TestDBUtil.pm, we see alot of failing tests because the root directory did not necessarily match the expected. The new regex is a bit more loose. The branch itself (t_vs_struct) demonstrates the problem.
- See also failing tests at:
- http://www.cpantesters.org/show/Workflow.html#Workflow-0.32_4

Added List::MoreUtils to requirements, we use this for test, I have moved the test related modules to the build_requires section in Build.PL, so List::MoreUtils is not mistaken for an application level module
Some of the new tests distributed with 0.32_3 fail. We are looking at actions returned as an array, but since they originate from a hash, the order is not given as assumed in the test.
- Updated the test and bumped up the version of t/TestUtil.pm to 0.02
- Refactored two tests, to use List::MoreUtils all method (asserting presence of numerous actions)

Updated MANIFEST and MANIFEST.SKIP, some stuff was not included
Fixed minor bug in error message in: Workflow::State, reported by Robert Stockdale, RT #38023

This is yet another developer release introducing a more fine grained control of the auto commit feature, implemented by Jim Brandt, we are very interested in feedback on this release, so please consider joining the mailing list or send feedback to jonasbn@cpan.org directly.
The auto_commit feature is however still defaulting to enabled to respect backwards compatibility and the control is experimental, hence the developer release
- The example application in eg/ seemed to have some issues, these have been addressed also
  - Updated: eg/ticket/App/Condition/IsWorker.pm eg/ticket/ticket.pl lib/Workflow.pm lib/Workflow/Persister/DBI.pm lib/Workflow/Factory.pm lib/Workflow/Persister.pm
  - Added: t/persister_dbi_sqlite.t t/TestDBUtil.pm

This is a developer release introducing typed condition, implemented by Jim Brandt, we are very interested in feedback on this release, so please consider joining the mailing list or send feedback to jonasbn@cpan.org directly.
Typed conditions makes it possible for different workflows to hold unique methods for workflow steps even with names colliding.
- Example workflow foo and bar can have a condition baz, but baz are two different implementations in foo and bar respectively
  - Updated: t/cached_conditions.t t/factory.t t/state.t t/TestUtil.t t/condition.t t/workflow_type.t t/config.t t/workflow.t
    - Workflow Workflow::Factory Workflow::Config Workflow::Config::XML Workflow::Config::Perl Workflow::Action Workflow::State Workflow::Condition Workflow::Persister::DBI Workflow::History Workflow::Persister::SPOPS
  - Introduced t/state_perl.t t/TestApp/Action/TicketCreateType.pm t/TestApp/Condition/HasUserType.pm t/workflow_action_type.perl t/workflow_action_type.xml t/workflow_condition_type.perl t/workflow_condition_type.xml t/workflow_persister.perl t/workflow_persister.xml t/workflow_type.perl t/workflow_type.xml
This release also holds new tests of persister configurations, there is however always room for more
time_zone parameter can now be passer around for use by the Workflow DateTime objects internally