workflow states one step behind
fnikola - April 23, 2009 - 17:52
| Project: | Workflow-ng |
| Version: | 5.x-2.2 |
| Component: | State Machines |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Description
It seems like the workflow states are one step behind – when I save the enrollment form node the current state is not the current state – it is the current state from one step past.
[node:workflow-current-state-name]
[node:workflow-old-state-name]
For example if the enrollment form was changed from “pending” to “approved” to “rejected” it is being reflected as the following in the log when trying to create workflow rules:
new: “approved”
old: “pending”
I am logging the old and current states to the log to see this behavior.