Using the container method described above would only apply the workflow to page instances connected to that container. The workflow wouldnt be applied to anything else connected to the 'foundation' page..
I did managed to set up a site a while back where workflows were assigned to individual pages.. It was for a local government website - where the site structure didnt reflect the internal management structure of the business. Users would create standalone pages within a separate 'workflow' area of the site (there were 52 different workflows to choose from!!!!!!!!!).. For each workflow, we created individual lists that had a separate workflow preassigned. Once the page went through the approval process, an administrator would then connect up the page within a separate 'live' site structure - which effectively was the site that was published. unfortunately the obvious downsides here were that two separate site structures had to be maintained, and that navigational areas had to be built using the 'list through container' method (not Nav Manager - which relies on the 'primary link' approach).. but it worked!! No real significant performance hits either - approx 1000-2000 pages in the project. On Feb 19, 5:37 am, Casey Williams <[email protected]> wrote: > That depends, would the workflow tied to the con_body recognize a > change to say, the headline, or metadata, or adding a link, etc, and > react appropriately? Or would it just react to changes made to the > page inside the container? > > On Feb 18, 12:16 pm, Jian Huang <[email protected]> wrote: > > > Crazy idea here: > > > We have foundation and content modules, which goes into the con_body > > of the foundation. > > > Assuming contents is entered into a content module page instance > > living inside con_body. Can the workflow be tied to con_body? > > > There is already a retroactively assign workflow plugin to assign > > workflow to structural element in all page instances of a content > > class, but I think your tool might work better since it is more > > familiar to you. > > > -Jian > > > On Feb 18, 11:02 am, Casey Williams <[email protected]> wrote: > > > > 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 -- 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.
