- Get started with theme development
- Gulp Viewport and Developer tools
- Theme development troubleshooting
- Password-protect content for anonymous users
- Advanced content rendering
- Develop Pluggable Placeholders
- Get help with theme development
- Page context
- Blog overview context
- Search context
- Error context
- Supported macros
- Theme guidelines
- Theme properties
- Search and SEO
- Confluence/Viewport macros and features
- (External) files and media
- Integration with other Scroll Add-ons
Integration with third-party software
- Displaying Additional User Information from the User Profile Plugin
- General 3rd party add-on implementation
- Integrating Disqus Comments
- Making Gliffy macros resizable
- Making UI-Expand macro of RefinedToolkit work
- Displaying Viewport Content in an iframe
- Integrate Midoris Archiving Plugin
- Trigger EliteSofts Page View Macro through Scroll Viewport
- Make your app compatible with Scroll Viewport
- Content Management via Page properties
- Context-Sensitive Help
You can integrate Comala Workflows with Scroll Viewport. This gives you the option to only export content that has been approved through every step of a Comala Workflow, and has been published to the final workflow state. This state can be any Comala Workflow state with the final:true parameter, regardless of the state's name. This guide explains how to integrate Comala Workflows and Scroll Viewport, and how to activate this option.
Before you start, you must fulfill the following prerequisites:
- Scroll Viewport (version 2.11.0 or later) must be installed
- Comala Workflows (version 5.9.1 or later) must be installed
- Comala Workflows for Scroll Exporters (version 1.0.5 or later) must be installed (can only be installed after Scroll Viewport and Comala Workflows)
- A Comala Workflow must be configured for the space
Show only content published to the final Comala Worfklow state
Now the additional option Comala Workflows Integration can be activated in the Content tab of the Scroll Viewport Configuration.
If the integration is activated, only content that has been published to the final workflow state will be displayed in the Viewport view. If there's a page that has content in the final state, as well as content in a draft state, your authors will be able to access the draft content via the Confluence view, whereas your readers can only see the final state through the viewport view.
If the internal Confluence search is used, the search results might show pages that are not accessible if a user searches for a term that's used on a draft page (which is the same behavior as if you'd use Comala Workflows in a vanilla Confluence system).
If the user clicks such a result, the page won't be available.
As a workaround - if your space is available without login - you could use an external search implementation instead of using the built-in Confluence search.
The integration does not work in spaces that are managed with Scroll Versions.
If you want to use Comala Workflows in such a scenario, please use the Comala integration for Scroll Versions, follow the Private Master Space Approach, and activate Scroll Viewport in the published spaces.