nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

How To Create New WCM Workflow?

ninerfan

Hi all,

Really simple question but have not been able to find an answer to this yet. Everytime someone submits content into STAGING it seems to go into this out of the box workflow. Web Site Submission(Submit changes for approval). How was that workflow created (not assigned). In other words in TeamSite there are wft files that are the workflow templates. Where is the template file for the default Web Site Submission workflow that defines the behavior of the workflow and how do I create new workflow templates that will show up as additional options during submits?

Is there a workflow builder tool? A workflow template file? Other?

Thanks.

-Ninerfan

Find more posts tagged with

Comments

davidc

There's are workflow definition file(s). The WCM submit process is in config/alfresco/workflow/submit_processdefinition.xml

Some docs on creating workflow are found at http://wiki.alfresco.com/wiki/Workflow.

ninerfan

Thanks David, I'll check out those files. Unfortunately this wiki link only shows an empty page. http://wiki.alfresco.com/wiki/Workflow.

Do I need some special access to view the workflow wiki?

-Ninerfan

randomman

Unfortunately this wiki link only shows an empty page. http://wiki.alfresco.com/wiki/Workflow.

Do I need some special access to view the workflow wiki?

-Ninerfan

Take the full stop off the end of the link. i.e. http://wiki.alfresco.com/wiki/Workflow

kvc

Please note that if you are creating a custom workflow, please also refer to the default wcm submit process. It serves as a model for any of your custom workflows, specifically by creating special review sandbox to isolate submitted changes sets for preview by reviewers and then by destroy upon commit to staging (and also releasing locks and taking a snapshot of staging).

So, once again, please review. In TeamSite, each task had an explicit notion of taking and releasing locks, and you had a submit task pre-built for the commit action. You did not though have the option of isolating change sets in special review contexts - everything was just referenced from the submitting workflow.

In Alfresco, our default submit process uses a custom action you should re-use to create and destroy those special review contexts. It also explicit handles locking and submit, though as custom actions associated with the end-process task and not part of a pre-built task itself.

You'll find it similar in power (well, hopefully more powerful) but a slightly different model … do review first.

Kevin