I suppose I could make an anchor on every page and then tie the workflow to that, if it would work properly. I'd rather not do it that way, but if it is the only way I'll investigate it. Since you have prior knowledge about the project, I can give you some context:
Remember how I made separate content classes for protected/public content and used page variants to get them to publish to different folders? Well, we need public and protected content to go through different workflows. So, ideally I'd like to be able to tie the workflow to the content class, but since it seems this isn't possible, I could deal with assigning the workflow to each instance of the appropriate content class via RQL. Obviously assigning the workflow at the lst_navigation level will not work, since there are pages of both types underneath nearly every page. Thoughts? On Feb 18, 10:45 am, Jian Huang <[email protected]> wrote: > Hi Casey, > > Workflow is tied to a structural element. Is this structural element > a list or an anchor? If it is a list, can it become an anchor? If it > is lst_navigation, then I have to go back to the drawing board. > > -Jian > > On Feb 18, 10:18 am, Casey Williams <[email protected]> wrote: > > > > > I have a content class that a specific workflow for all of its > > instances. Is there a way to do this? Or even to assign a work flow to > > a specific page rather than a structural element?- Hide quoted text - > > - Show quoted text - -- You received this message because you are subscribed to the Google Groups "RedDot CMS 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/reddot-cms-users?hl=en.
