Found 319 results for "ui workflow"

The search executed in 0.00197183 seconds. That's fast.

Gitana / 3.2 / Guide / Guide / 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

Score: 1.918998

Gitana / 4.0 / Data Engine / 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

Score: 1.918998

Gitana / 3.2 / Guide / Guide / Docker / Maintenance / Health Check / Load Balancers

Health Check / Load Balancers In a production configuration of Cloud CMS, you will want to have a load balancer (LB) in front of both your API and UI clusters. You should have one load balancer for the API cluster and one load balancer for the UI cluster. Each load balancer is responsible for receiving requests from the outside world and efficiently distributing those requests to the N servers that make up each cluster. Load balancers use a number of strategies to try to determine which servers

Score: 1.9106088

Gitana / 4.0 / Self Managed / Maintenance / Health Check / Load Balancers

Health Check / Load Balancers In a production configuration of Cloud CMS, you will want to have a load balancer (LB) in front of both your API and UI clusters. You should have one load balancer for the API cluster and one load balancer for the UI cluster. Each load balancer is responsible for receiving requests from the outside world and efficiently distributing those requests to the N servers that make up each cluster. Load balancers use a number of strategies to try to determine which servers

Score: 1.9106088

Gitana / 3.2 / Guide / Guide / 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: 1.9053417

Gitana / 4.0 / Data Engine / 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: 1.9053417

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

Gitana / 3.2 / Guide / Guide / Workflow / 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: 1.901897

Gitana / 4.0 / Data Engine / Workflow / 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: 1.901897

Gitana / 3.2 / Guide / Guide / 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 lik

Score: 1.8970952

Gitana / 4.0 / Data Engine / 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 lik

Score: 1.8970952

Gitana / 4.0 / Data Engine / Publishing / Overview

Publishing Publishing brings together many parts of Cloud CMS to enable you to manage the lifecycle of your Content. Our Publishing is very configurable to meet your diverse needs. To help get you started we have a simple example showing a Publish and Unpublish mechanism between an Authoring Project and a Live project. When Publishing is enabled in a Project you get: Workflow workflow are meant as a starting point and may meet your needs. If you have more complex requirements you can also define

Score: 1.8863301

Gitana / 3.2 / Guide / Guide / Publishing

Publishing Publishing brings together many parts of Cloud CMS to enable you to manage the lifecycle of your Content. Our Publishing is very configurable to meet your diverse needs. To help get you started we have a simple example showing a Publish and Unpublish mechanism between an Authoring Project and a Live project. When Publishing is enabled in a Project you get: Workflow workflow are meant as a starting point and may meet your needs. If you have more complex requirements you can also define

Score: 1.8766015

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

Gitana / 3.2 / Guide / Guide / UI Developers Guide / Contexts / publishing-manage-subcontext

publishing-manage-subcontext [ { "evaluator": "context-project", "config": { "publishing-manage-subcontext": { "items": [ { "key": "project/publishing", "title": "Publishing", "header": true, "items": [ { "key": "project/publishing/settings", "title": "Settings", "uri": "#/projects/{projectId}/manage/publishing", "iconClass": "fa fa-angle

Score: 1.8519698

Gitana / 4.0 / Developers / User Interface Customization / Contexts / publishing-manage-subcontext

publishing-manage-subcontext [ { "evaluator": "context-project", "config": { "publishing-manage-subcontext": { "items": [ { "key": "project/publishing", "title": "Publishing", "header": true, "items": [ { "key": "project/publishing/settings", "title": "Settings", "uri": "#/projects/{projectId}/manage/publishing", "iconClass": "fa fa-angle

Score: 1.8519698

Gitana / 4.0 / Self Managed / Configuration / Overview

Configuration Antivirus Server API Server Encrypting Properties UI Server

Score: 1.8324399

Editorial Flows

Editorial Flows In Gitana 4.0, we introduced a new feature called Editorial Flows. With Editorial Flows, your editorial teams launch draft workspaces where they work on content items at their own pace. They can write new content, change existing content or delete things in isolation without worrying about how it will affect the main line of content. They are free to work without worry about stepping on each other's toes. They can make changes to the content graph, upload new files, adjust taxono

Score: 1.8306352

Gitana / 3.2 / Guide / Guide / Docker / Configuration

Configuration Antivirus Server API Server Encrypting Properties Support UI Server

Score: 1.829602

Advanced Content Modeling options (example)

Question. If I have the following collections: Categories Products Product_Description_Schemas Each Product is linked to a Category. Each Category is linked to a Product_Description_Schema. The outcome I want to accomplish is that the description schema for Product X I am entering, is defined by the Category it is linked to ( which in turn is defined by the Product_Description_Schema that the Category is linked to ). e.g. Product = Hilton Hotel London, Category = Hotel, Product_Description_Schem

Score: 1.8127044

Gitana / 3.2 / Guide / Guide / Application Server / Services / Flow

Flow Provides API services for browser-side UI application wizards whose configuration is defined in JSON. { "flow": { "enabled": true } }

Score: 1.8044512

Gitana / 4.0 / Developers / Application Server / Services / Flow

Flow Provides API services for browser-side UI application wizards whose configuration is defined in JSON. { "flow": { "enabled": true } }

Score: 1.8044512

CMS editor Locking

There are two levels of locking which usually come into play in a scenario like this. One is a "UI lock" which is taken out when a user begins editing something within the user interface. This lock is released when they finished editing (either by hitting save or canceling). The other lock is a "data lock" which is a transactional lock taken out when the write of multiple documents begins. This is a transactional lock in the sense that it blocks other write operations against those documents and

Score: 1.7930949

Gitana / 3.2 / Guide / Guide / UI Developers Guide / Contexts / registrations

registrations [ { "config": { "registrations": { "menus": [ { "scope": "platform", "key": "account-context", "text": "Account" }, { "scope": "platform", "key": "archive-subcontext", "text": "Archive" }, { "scope": "platform", "key": "vault-subcontext", "text": "Vault" }, { "scope": "platfo

Score: 1.7882693

Gitana / 4.0 / Developers / User Interface Customization / Contexts / registrations

registrations [ { "config": { "registrations": { "menus": [ { "scope": "platform", "key": "account-context", "text": "Account" }, { "scope": "platform", "key": "archive-subcontext", "text": "Archive" }, { "scope": "platform", "key": "vault-subcontext", "text": "Vault" }, { "scope": "platfo

Score: 1.7882693