We had to do something similar on a project that required a dynamic
workflow setup where the client needed to be able to change workflows
at anytime. We had a "Workflow" model that defined different workflows
for things like articles, requests, tickets, or what have you and then
a "WorkflowStep" model that detailed the specific steps that were for
a workflow. An article may start as a draft, then be moved to pending
and finally live.
So, Workflow had many WorkflowStep. From there we made the HABTM table
of "workflow_steps_workflow_steps" which was where we laid out the
allowed steps a current step could go to; draft to pending, pending to
draft, pending to live, etc. It's really not as confusing as it sounds
once you start playing with it. You have to write your code a little
bit differently but yeah, it can be done.
On Nov 15, 6:35 pm, korcan <[EMAIL PROTECTED]> wrote:
> Has anyone ever put logic into a db table? I want to allow a user to
> make a variety of selections for how to handle something and store
> them in the DB, however I want the controller to use this logic when
> the user is logged in.
>
> Anyone ever do this? How would you recommend accomplishing this?
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"CakePHP" group.
To post to this group, send email to cake-php@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/cake-php?hl=en
-~--~~~~--~~--~--~---
