Search Results

API / Workflow / Overview

Overview In explaining workflow, let's first take a look at the following things: Workflow Models Workflow Instances Workflow Tasks Workflow Payload Resources Workflow Comments Workflow History Item Workflow Events Workflow Event Handlers A workflow model is a definition of a workflow consisting of a full set of instructions on how content should be routed between participants or activities on its way toward completion. A workflow model is kind of like a blueprint describing the sequence of step

Score: 51.130974

UI Guide / Workflow / Overview

Overview Cloud CMS provides an enterprise workflow engine that lets teams work together via coordinated tasks. A workflow is a customizable business process that you define and describes a series of steps and activities to be performed by your team members. Workflows are generally used to control the lifecycle state (approval and rejection) of one or more content items or documents. With workflow in place, documents are routed from user to user. Users optionally receive notifications via email a

Score: 19.294107

API / Workflow Handlers / Email

Email Type: email This handler sends an email to a recipient. It fires the sendEmail action and accepts a standard configuration object for that action type. The config for this handler can be as simple as: { "templateKey": "abc" } Where abc is the key of an Email Template content node in your repository. This will work just as shown above for workflows that are launched with the runtime globals for repositoryId and branchId specified. Otherwise, you will have to provide them, something lik

Score: 17.17629

API / Actions / Create Thumbnail

Create Thumbnail ID: createThumbnail { "title": "Create Thumbnail(s)", "properties": { "attachmentId": { "title": "Attachment ID", "type": "string", "default": "default" }, "thumbnails": { "type": "array", "items": { "type": "object" } } } }

Score: 15.301353

API / Workflow Handlers / Web Hook

Web Hook Type: webhook This handler makes an HTTP(S) POST to a remote web service. It automatically passes along any relevant information about the workflow, task or transition so that your web service can get to work. The config for this handler looks like this: { "url": "http://myserver:port/controller" } In addition, you can supply username and password properties in support of Basic authentication to your listener endpoint: { "url": "http://myserver:port/controller", "username":

Score: 13.535199

UI Guide / Workflow / How to Start a Workflow

How to Start a Workflow Note: A Workflow model is defined at Platform level and is available within all projects See workflow video: https://www.cloudcms.com/resources/introduction-to-workflow.html Example Start a workflow from a ‘document’ There are a number ways to start a workflow. Here is just one: open a document Click 'Workflows' and then ‘+Start Workflow’ This will bring up the Start Workflow Form. Complete the fields in the form. Notes: In our example, the Adhoc Workflow, you will need a

Score: 11.448252

API / Content Services / Templates

Templates Cloud CMS supports the usage of templates at various points to generate presentation and output for things like emails, PDFs, web page components and more. Cloud CMS supports two template engines - Handlebars and Freemarker. In general, we recommend using Handlebars since the syntax is a bit easier. This document covers Handlebars and describes helper functions available in Handlebars that make processing simpler. Model Variables The following describes the internal structure of model

Score: 11.091716

API / Workflow Handlers / Add Features

Add Features Type: addFeatures This handler adds features to a node that is part of the workflow's payload. This can be used to apply one or more features to your content instances as they flow through your workflow. The config for this handler is as follows: { "features": [{ "qname": "", "config": { ... optional configuration for the feature } }] } The config is an optional parameter. You can use this handler to add one or more features

Score: 11.087954

API / Workflow Handlers / Copy Node

Copy Node Type: copyNode This handler copies nodes that are part of a workflow's payload to a target folder. The target folder can be identified either by a node ID or a node path. The config for this handler is as follows: { "targetNodeId": "", "targetOffsetPath": "" } If targetOffsetPath is specified, then targetNodeId is the root node to calculate the offset against. If targetNodeId is not provided, the default repository root is used. Here is an example

Score: 11.007748

API / Workflow Handlers / Remove Features

Remove Features Type: removeFeatures This handler removes features from a node that is part of the workflow's payload. This can be used to remove one or more features from your content instances as they flow through your workflow. The config for this handler is as follows: { "features": [{ "qname": "" }] } Each of the features identified by qname will be removed from the documents attached to the workflow payload. Here is an example configuration which assumes tha

Score: 10.960945