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: 44.16508

API / Actions / Overview

Overview Cloud CMS provides an action framework that lets you kick off actions that perform processes on your behalf. Actions are units of work that are typically fired off as a result of an event handler or listener. For example, you might register an action that fires when a piece of content is updated or when a workflow task transitions. The Cloud CMS action framework aspires to provide complete units of work that are configured using simple JSON. The units of work are cluster aware and will

Score: 40.489727

API / Policies / Overview

Overview Policies can be used to run custom code or fire off actions when an event, such as creating a content item or associating a content item into the content graph, occurs. Cloud CMS provides a wide array of policies that you can hook your custom logic into. By default, Cloud CMS provides sensible and useful content policy handlers to manage the lifecycle of you content. You can wire in new policy handlers. Policy handlers include scripts and rules. The following types of policies are avail

Score: 38.831444

API / Behaviors / Overview

Overview Cloud CMS lets you wire in behaviors behind your content models so that rules automatically execute when your content is touched. Content editors work with simple forms to create content that conforms to your defined content models. When that content is created, updated or deleted, it automatically triggers policies (or events) which you use to bind in custom behaviors. In this way, the developers can wire up behaviors and the editorial team never needs to know about it. Furthermore, be

Score: 36.4308

API / Conditions / Overview

Overview Conditions provide a way for Rules to evaluate their content and their environment prior to determining whether to proceed with the execution of their Actions. A Condition might be a simple check such as checking to see whether the current content item has a certain property value. But they also might be more complex logic chains consisting of and and or blocks. Cloud CMS provides a number of out-of-the-box Conditions. Scroll down to see a list of available out-of-the-box Conditions and

Score: 33.628433

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: 17.075077

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: 16.818611

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: 11.386799

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