Found 59 results for "workflow handlers addfeatures"

The search executed in 0.001 seconds

Workflow / Workflow Handlers

Workflow Handlers Add Features Copy Node Email Logger Move Node Remove Features Remove Properties Set Properties Sync Node Web Hook

Score: 43.004807

Workflow

Workflow 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: 41.28139

Deployment / Deployment Handlers

Deployment Handlers A Deployment Handler provides the deployment implementation for a Deployment Target. When Deployment Packages are routed to a Deployment Target, the Deployment Target's "handler" is instantiated to handle the actual connectivity, copy and delivery of the Deployment Package's content. The following Deployment Handlers are available: Branch Deployment Handler File System Deployment Handler FTP Deployment Handler HTTP Deployment Handler Local Deployment Handler Remote Deployment

Score: 23.882143

User Interface / Workflow

Workflow 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: 18.284452

Publishing / Workflow

Workflow Cloud CMS lets you define your own Workflows and choose them for the Publish and Unpublish activities. Each activity like Publish and Unpublish will have a Workflow Model which will have a set of instructions on how the contents should be routed during each activity. The default Workflow models we use for the Publish activity is Simple Publish and for the Unpublish activity is Simple Unpublish. You can add your own Workflows and customize your publish and unpublish activities.

Score: 17.17501

Getting Started / Workflow

Workflow A workflow is a business process that describes a series of activities (from start to finish) that must occur for one or more content items to be approved or rejected. Workflows consist of a workflow model that lays out these activities into a series of tasks. Each task is generally an opportunity for someone on your team to do some work. They may also be automatic tasks that do things like send emails, set content properties, call off to HTTP web hooks and more. As content moves throug

Score: 12.901952

Workflow / 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: 12.105596

Actions / Start Workflow

Start Workflow ID: startWorkflow Starts a workflow with the given node placed into the payload. Configuration Property Type Required Default Description model text true The ID of the workflow model to be used. swimlanes object false Identifies principals to be assigned into workflow swimlanes. The structure is: { "swimlane1": ["domainId1/principalId1"], "swimlane2": ["domainId2/principalId2"] } runtime object false Allows for manual specification of runtime properties including applica

Score: 11.170717

Modules / Bindings / Menus - Workflow Context

Menus - Workflow Context The workflow-context key defines the left-hand menu options for the Workflow pages. To populate the workflow-context section, your configuration snippet should look like this: { "workflow-context": { "items": [] ] } Default Configuration The default UI configuration for the Workflow pages looks a bit like this: { "workflow-context": { "items": [{ "key": "workflow", "title": "Workflow", "order": 1000,

Score: 10.05158

User Interface / 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: 9.9436245

User Interface / Workflow / View/Create a Workflow Model

View/Create a Workflow Model Switch to Platform level Click 'Workflow Models' (left Nav). Note: You will need to have admin or owner permissions to see the Workflow options. If you select a Workflow model you can Deploy, Undeploy, delete a Workflow model View/Edit Workflow Model Click on the Workflow name, eg Adhoc Approval, to view the Workflow Model To view/edit the Workflow click JSON Manage Active Workflow To see active instances of the workflow model click on Workflow option Note: you can s

Score: 9.251213

User Interface / Workflow / View Active/Inactive Workflow

View Active/Inactive Workflow You can view both the Active and Inactive workflow from the Platform and Project levels. The Platform level will show all workflow for all Projects and at Project level it will show all workflow for that Project. Click Workfow Title to open the Workflow Overview page

Score: 9.075186

Deployment

Deployment Cloud CMS Deployment lets you publish content from a source Cloud CMS project branch to one or more destination Deployment Endpoints. These Deployment Endpoints may include Amazon S3 buckets, FTP servers, file system locations and Cloud CMS branches on the same cluster or running in a cluster located in another data center somewhere else in the world. The Deployment process can be triggered manually or automatically. It may run as part of a Publishing process for your content. It may

Score: 6.8354483

Policies

Policies 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: 6.0032225

Docker / Kits

Kits Cloud CMS ships a number of pre-built kits containing Docker configuration files to help you get start. These kits are built from customer feedback to provide the most commonly requested scenarios. They can be used straight away or at the very least can serve as a useful reference. To download the Cloud CMS Docker Kits, please visit our Docker download page. Kits All of the Docker kits utilize Docker and Docker Compose. In each kit, you'll find a docker-compose.yml file which describes the

Score: 4.7815146

Application Server / Installation / Module Installation

Module Installation The Cloud CMS Application Server can also be run as a custom Node.js application. It is available as a Node.js module that you can require() in from npmjs.org. The server features a number of extension points that you can utilize to wire in new functionality or extend the framework. Getting Started Here is a simple example where we start up the Application Server from within a Node.js application: var server = require("cloudcms-server/server"); server.start(); The start() met

Score: 4.6033216

Is there a programmatic way to add more content to workflows?

There is a programmatic way to add more content to workflows once they're in-flight. However, once the workflow is in-flight, the workflow process instance isn't the correct place to add things. Instead, you'd want to add new content to a workflow task. Essentially, a workflow is made up of a series of tasks. When the workflow transitions from one node to another in the workflow model, it instantiates a new task and the task holds the state (and references to documents) for that phase of the wor

Score: 4.5386887

Integrations

Integrations Cloud CMS allows you to connect to external cloud-based services for purposes of things like: external data storage for binary data auto-record updates to dns servers event handling to cloud notification handlers To configure these services, you simply create a service descriptor via the main interface: Service descriptors are declared once and can be re-used multiple times within your platform, across different projects and applications. Service descriptors are encrypted on the ser

Score: 4.5072017

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

Deployment / Deployment Receivers

Deployment Receivers A Deployment Receiver acts as an endpoint for local and remote Deployment Handlers that seek to ship their Deployment Packages to a destination. These are frequently used to move content between data centers or across different parts of the world to solve for latency issues (or to simply move content to the correct side of a DMZ for security reasons or runtime-performance reasons). Cloud CMS lets you create Deployment Receivers from within its user interface. You can create

Score: 4.366164

Using swimlanes in workflow

Workflow swimlanes are assigned the domain-qualified ID of a principal (which can be either a user or a group). If it is set to a user, then a transition of a workflow into that swimlane will result in a task being assigned to a specific user. If it is set to a group, then a transition of a workflow into that swimlane will result in a task being assigned to a group where none of the members of the group are assigned anything. Rather, the task appears in a list of available tasks that any of the

Score: 4.328245

Workflow / 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 w

Score: 4.278507

Workflow / 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 like

Score: 4.278507

Publishing / Content Types

Content Types Cloud CMS lets you customize the Publishing Behavior and the Workflow Per Content Type. You can now Enable/Disable the Preview and Publishing buttons for each Content Type. Customize Publishing Behavior Per Content Type You can disable the Publishing Behavior like Preview button or the Publishing buttons for all the Content types whose content or data you do not want to publish. To Disable the Publishing behaviors of the Content Types: Go to Project Go to Manage Project Go to Publi

Score: 4.277126

What is a pooled task?

A pooled task is a task in your workflow that has a swimlane that consists either of a group or multiple people. Each task in your workflow has a swimlane associated with it. The swimlane determines who will be assigned the task when the task is routed to. If the swimlane consists of a single user, then the task will automatically be assigned. This is the usual case. When a workflow is assigned, it shows up in the "Assigned Tasks" view of your task inbox. However, there will be times when you wi

Score: 4.276694