Found 533 results for "policies node"

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

Gitana / 3.2 / Guide / Guide / Application Server / URL Addressability / Node URLs

Node URLs The Application Server supports retrieval of nodes and node attachments via URLs and takes responsibility for setting headers and cache state for optimal performance. This method is the preferred method for dealing with binary payloads as it ensures compatibility with CDN edge caching. In addition, binary and JSON files that are retrieved from the Cloud CMS API are cached on the Application Server itself so that subsequent requests benefit from having a local copy. A notifications laye

Score: 4.3322725

Gitana / 4.0 / Developers / Application Server / URL Addressability / Node URLs

Node URLs The Application Server supports retrieval of nodes and node attachments via URLs and takes responsibility for setting headers and cache state for optimal performance. This method is the preferred method for dealing with binary payloads as it ensures compatibility with CDN edge caching. In addition, binary and JSON files that are retrieved from the Cloud CMS API are cached on the Application Server itself so that subsequent requests benefit from having a local copy. A notifications laye

Score: 4.3322725

Gitana / 3.2 / Guide / Guide / Actions / Deploy Node

Deploy Node ID: deployNode Deploys or undeploys a node using the deployment system. { "title": "Deploy Node", "properties": { "deploymentStrategyId": { "type": "string", "title": "Deployment Strategy ID" }, "operation": { "type": "string", "title": "Operation", "enum": ["DEPLOY", "UNDEPLOY"] } } } Where: deploymentStrategyId is the ID of the deployment strategy to use operation indicates whet

Score: 4.3056498

Gitana / 4.0 / Data Engine / Behaviors / Actions / Deploy Node

Deploy Node ID: deployNode Deploys or undeploys a node using the deployment system. { "title": "Deploy Node", "properties": { "deploymentStrategyId": { "type": "string", "title": "Deployment Strategy ID" }, "operation": { "type": "string", "title": "Operation", "enum": ["DEPLOY", "UNDEPLOY"] } } } Where: deploymentStrategyId is the ID of the deployment strategy to use operation indicates whet

Score: 4.3056498

Gitana / 3.2 / Guide / Guide / Workflow / Workflow Handlers / Lock Node

Lock Node Type: lockNode This handler lets you lock the nodes that are part of your workflow's payload. There is no config for this workflow handler. Example use: { "type": "lockNode", "config": {} }

Score: 4.228835

Gitana / 3.2 / Guide / Guide / Workflow / Workflow Handlers / Unlock Node

Unlock Node Type: unlockNode This handler lets you unlock the nodes that are part of your workflow's payload. There is no config for this workflow handler. Example use: { "type": "unlockNode", "config": {} }

Score: 4.228835

Gitana / 4.0 / Data Engine / Workflow / Workflow Handlers / Lock Node

Lock Node Type: lockNode This handler lets you lock the nodes that are part of your workflow's payload. There is no config for this workflow handler. Example use: { "type": "lockNode", "config": {} }

Score: 4.228835

Gitana / 4.0 / Data Engine / Workflow / Workflow Handlers / Unlock Node

Unlock Node Type: unlockNode This handler lets you unlock the nodes that are part of your workflow's payload. There is no config for this workflow handler. Example use: { "type": "unlockNode", "config": {} }

Score: 4.228835

Gitana / 3.2 / Guide / Guide / Workflow / Workflow Handlers / Sync Node

Sync Node Type: syncNode This handler "syncs" nodes that are part of a workflow's payload to a target branch. This handler can be used to have workflow payload nodes automatically copied to or deleted from a target branch. The full config for this handler is as follows: { "targetProjectId": "", "targetRepositoryId": "", "targetBranchId": "", "asynchronous": , "includeAllAssociations": , "delete": , "allowWr

Score: 4.140753

Gitana / 4.0 / Data Engine / Workflow / Workflow Handlers / Sync Node

Sync Node Type: syncNode This handler "syncs" nodes that are part of a workflow's payload to a target branch. This handler can be used to have workflow payload nodes automatically copied to or deleted from a target branch. The full config for this handler is as follows: { "targetProjectId": "", "targetRepositoryId": "", "targetBranchId": "", "asynchronous": , "includeAllAssociations": , "delete": , "allowWr

Score: 4.140753

Gitana / 3.2 / Guide / Guide / Application Server / Clustering

Clustering The Cloud CMS Application Server supports running on a single Node process as well as multiple Node processes. Node processes can run on a single server instance or can be spread across multiple server instances behind a load balancer. By default, the Application Server starts up and allocates itself to a single CPU. This is known as single mode. Even if you have a server with more than one CPU on it, the Application Server will still only bind to 1 of those CPUs. When the Application

Score: 4.020285

Gitana / 3.2 / Guide / Guide / Conditions / Node Has Attachment

Node Has Attachment The nodeHasAttachment condition tests whether a node has an attachment with a given attachmentId and optional contentType. It triggers if a matching attachment is found. JSON Schema { "title": "Node Has Attachment", "properties": { "attachmentId": { "type": "string", "title": "Attachment ID", "default": "default" }, "contentType": { "type": "string", "title": "Content Type" }

Score: 3.7638578

Gitana / 4.0 / Data Engine / Behaviors / Conditions / Node Has Attachment

Node Has Attachment The nodeHasAttachment condition tests whether a node has an attachment with a given attachmentId and optional contentType. It triggers if a matching attachment is found. JSON Schema { "title": "Node Has Attachment", "properties": { "attachmentId": { "type": "string", "title": "Attachment ID", "default": "default" }, "contentType": { "type": "string", "title": "Content Type" }

Score: 3.7638578

Gitana / 3.2 / Guide / Guide / Actions / OCR Extract Node

OCR Extract Node This section describes features that are coming in 4.0 ID: ocrExtractNode Runs OCR Extraction against a node. { "title": "OCR Extract Node", "properties": { "serviceId": { "type": "string", "title": "Service ID" } } } Where: serviceId is the ID of an optional OCR Extraction Service to be used If serviceId is not provided, the default OCR Extraction Service for the project will be used (if available). Example { "serviceId":

Score: 3.744357

Gitana / 4.0 / Data Engine / Behaviors / Actions / OCR Extract Node

OCR Extract Node This section describes features that are coming in 4.0 ID: ocrExtractNode Runs OCR Extraction against a node. { "title": "OCR Extract Node", "properties": { "serviceId": { "type": "string", "title": "Service ID" } } } Where: serviceId is the ID of an optional OCR Extraction Service to be used If serviceId is not provided, the default OCR Extraction Service for the project will be used (if available). Example { "serviceId":

Score: 3.744357

Gitana / 3.2 / Guide / Guide / Cookbooks / Node.js Cookbook

Node.js Cookbook Getting Started To get started with the Node.js driver, please visit the Cloud CMS Node.js Driver Page. One thing to keep in mind is that the Node.js driver is based on the JavaScript driver. As such, they're pretty similar. That said, the Node.js driver can do a few important tricks that you can't do in the JavaScript driver. Connecting to Cloud CMS To connect, create a file called gitana.json in your application root. For information on how to acquire this file, please read up

Score: 3.6627746

Gitana / 3.2 / Guide / Guide / Content Modeling / Behaviors

Behaviors 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, b

Score: 3.6027288

Gitana / 4.0 / Data Engine / Content Models / Behaviors

Behaviors 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, b

Score: 3.6027288

Gitana / 3.2 / Guide / Guide / Forms / Fields / File Picker

File Picker ID: file-picker The file-picker field type renders a modal picker for a file. This uses the File Folder service within Cloud CMS to let you browse through folder-based navigation. A breadcrumb is rendered at the top to help users step through the folder hierarchy. Sample configuration: { "type": "file-picker" } As with the node picker, the file picker should be modeled on top of either an object or an array field. The former is used for selection of a single node whereas the lat

Score: 3.4880042

Gitana / 4.0 / Forms / CMS / Fields / File Picker

File Picker ID: file-picker The file-picker field type renders a modal picker for a file. This uses the File Folder service within Cloud CMS to let you browse through folder-based navigation. A breadcrumb is rendered at the top to help users step through the folder hierarchy. Sample configuration: { "type": "file-picker" } As with the node picker, the file picker should be modeled on top of either an object or an array field. The former is used for selection of a single node whereas the lat

Score: 3.4880042

Enterprise Access Policies in Gitana 4.0 (Part 1)

In this article, we'll take a look at Access Policies -- a powerful, new feature in Gitana 4.0 that allows organizations to set up and guarantee compliance with complex, enterprise-wide security requirements. Access Policies build upon the existing access control facilities provided which include per-object ACLs and broader, team-based ACLs. They extend those capabilities by allowing administrators to express access rights in a broad sweeping and prescriptive manner -- one that allows for custom

Score: 3.4489675

Enterprise Access Policies in Gitana 4.0 (Part 2)

In this article, we'll continue our series on Access Policies within Gitana. We'll take a few interesting and more complex examples of how Access Policies may be used to guarantee compliance witih enterprise security requirements. In the previous article, we left off looking at how you can grant access to content using Access Policies that are defined at either a Platform or Project-level. Platform-scoped policies can be written once and applied across all of your Projects. In this way, you can

Score: 3.4475439

Gitana / 3.2 / Guide / Guide / UI Developers Guide / Actions / unassign_access_policy

unassign_access_policy ID: unassign_access_policy This pops up a modal to ask the user if they'd like to unassign the specified Access Policies. Upon confirmation, the Access Policies are unassigned from the target (specified by ref). Sample Code var UI = require("ui"); var actionContext = {}; actionContext.data = [policyId1]; actionContext.ref = node.ref(); // "node://platformId/repositoryId/branchId/nodeId"; UI.startAction(observableHolder, "unassign_access_policy", actionContext, function(er

Score: 3.3982425

Gitana / 4.0 / Developers / User Interface Customization / Actions / unassign_access_policy

unassign_access_policy ID: unassign_access_policy This pops up a modal to ask the user if they'd like to unassign the specified Access Policies. Upon confirmation, the Access Policies are unassigned from the target (specified by ref). Sample Code var UI = require("ui"); var actionContext = {}; actionContext.data = [policyId1]; actionContext.ref = node.ref(); // "node://platformId/repositoryId/branchId/nodeId"; UI.startAction(observableHolder, "unassign_access_policy", actionContext, function(er

Score: 3.3982425

Gitana / 3.2 / Guide / Guide / UI Developers Guide / Evaluators / context-document-is-node

context-document-is-node If a Document is currently being observed and is a node (not an association). { "evaluator": "context-document-is-node" }

Score: 3.3764834