I am planning an app where I need to have a dynamic lifecycle for a model. Consider an app where the user (admin) can control which states and transitions a lifecycle is to have. Does anyone have a suggestion on how to implement something like that?
Thoughts: - Define states and transitions via info from a separate model that defines states and transitions. This will create new dryml-pages while in production. - Changing the state-transition could make existing records invalid (catch these and allow manual override - or disallow changes that make existing records invalid - or ignore the problem) Other thoughts? ~Ronny -- You received this message because you are subscribed to the Google Groups "Hobo Users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/hobousers?hl=en.
