Found 316 results for "bulk-import nodes"

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

Gitana / 4.0 / Data Engine / Security / Access Policies / Conditions / Branch

Branch This section describes features that are coming in 4.0 The branch condition allows you to constrain a policy statement so that it applies to nodes and/or associations that are on a matching branch. The branch can be matched using its ID (_doc), title or alias. This condition supports regular expressions, allowing you to focus in on a single value or wildcard expressions for matches. Configuration To match a branch by ID: { "type": "branch", "config": { "id": "{value regex}

Score: 1.0619495

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

Move Node Type: moveNode This handler moves nodes that are part of a workflow's payload to a target container. The target container 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 exa

Score: 1.0619495

Gitana / 3.2 / Guide / Guide / Access Policies / Conditions / Feature

Feature This section describes features that are coming in 4.0 The feature condition allows you to constrain a policy statement so that it applies to content nodes that have a particular feature. Configuration { "type": "feature", "config": { "qname": "{qname regex}" } } Samples This policy grants the Consumer role to all content with feature f:thumbnailable: { "title": "My Sample Policy", "statements": [{ "action": "grant", "roles": ["consumer"],

Score: 1.0510397

Gitana / 4.0 / Data Engine / Security / Access Policies / Conditions / Feature

Feature This section describes features that are coming in 4.0 The feature condition allows you to constrain a policy statement so that it applies to content nodes that have a particular feature. Configuration { "type": "feature", "config": { "qname": "{qname regex}" } } Samples This policy grants the Consumer role to all content with feature f:thumbnailable: { "title": "My Sample Policy", "statements": [{ "action": "grant", "roles": ["consumer"],

Score: 1.0510397

How to limit the fields that come back in a query

Query API calls like http://api.cloudcms.com/docs#!/node/post_repositories_repositoryId_branches_branchId_nodes_query support a parameter named _fields which defines an object specifying the node properties you want to include in the result set for matching nodes. For example in the following query I want the title, subTitle and slug fields returned: { "_type":"my:article", "_fields":{ "title":1, "subTitle":1, "slug":1 } } The result set would look something like the

Score: 1.0510397

Gitana / 3.2 / Guide / Guide / Workflow / Sample Workflows / Events Example

Events Example This workflow model demonstrates how you can use events in various ways. This workflow model is provided as an kind of reference for how handlers can be set up. It isn't intended to be particularly useful or functional beyond its purpose as a demonstration. { "id": "events", "title": "Events Example Model", "nodes": { "start": { "type": "start", "transitions": { "start": "node1" } }, "node1": {

Score: 1.0403516

Gitana / 3.2 / Guide / Guide / Workflow / Sample Workflows / Simple Publish

Simple Publish The simple-publish workflow is provided out-of-the-box to support Publishing within Cloud CMS. { "id": "simple-publish", "title": "Simple Publish", "handlers": { "START": [{ "type": "script", "config": { "script": "workflowData.originalChangesetIds = {}; for (var i = 0; i < documents.length; i++) { workflowData.originalChangesetIds[documents[i].id] = documents[i].changesetId; }" } }] }, "nodes"

Score: 1.0403516

Gitana / 4.0 / Data Engine / Workflow / Sample Workflows / Events Example

Events Example This workflow model demonstrates how you can use events in various ways. This workflow model is provided as an kind of reference for how handlers can be set up. It isn't intended to be particularly useful or functional beyond its purpose as a demonstration. { "id": "events", "title": "Events Example Model", "nodes": { "start": { "type": "start", "transitions": { "start": "node1" } }, "node1": {

Score: 1.0403516

Gitana / 4.0 / Data Engine / Workflow / Sample Workflows / Simple Publish

Simple Publish The simple-publish workflow is provided out-of-the-box to support Publishing within Cloud CMS. { "id": "simple-publish", "title": "Simple Publish", "handlers": { "START": [{ "type": "script", "config": { "script": "workflowData.originalChangesetIds = {}; for (var i = 0; i < documents.length; i++) { workflowData.originalChangesetIds[documents[i].id] = documents[i].changesetId; }" } }] }, "nodes"

Score: 1.0403516

How to get a content definition JSON from the Cloud CMS API?

There are a couple of ways to do this. The first is simply use the node GET call and pass in the qname like this: GET /repositories/{repositoryId}/branches/{branchId}/nodes/{qname} http://api.cloudcms.com/docs#!/node/get_repositories_repositoryId_branches_branchId_nodes_nodeId This will give you back the JSON for the definition. Another way is to use this variation: GET /repositories/{repositoryId}/branches/{branchId}/definitions/{qname} http://api.cloudcms.com/docs#!/branch/get_repositories_rep

Score: 1.0403516

Gitana / 3.2 / Guide / Guide / Cookbooks / JavaScript (Legacy) Cookbook

JavaScript (Legacy) Cookbook Getting Started To get started with the JavaScript driver, please visit the Gitana JavaScript (Legacy) Driver Page. Connecting to Gitana To connect, supply your API Keys as the argument to the connect() method. Gitana.connect({ "clientKey": "{clientKey}", "clientSecret": "{clientSecret}", "username": "{username}", "password": "{password}", "baseURL": "https://api.cloudcms.com" }, function(err) { var platform = this; }); If a problem w

Score: 1.0165083

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

Gitana / 4.0 / Developers / Cookbooks / JavaScript (Legacy) Cookbook

JavaScript (Legacy) Cookbook Getting Started To get started with the JavaScript driver, please visit the Gitana JavaScript (Legacy) Driver Page. Connecting to Gitana To connect, supply your API Keys as the argument to the connect() method. Gitana.connect({ "clientKey": "{clientKey}", "clientSecret": "{clientSecret}", "username": "{username}", "password": "{password}", "baseURL": "https://api.cloudcms.com" }, function(err) { var platform = this; }); If a problem w

Score: 1.0165083

Gitana / 4.0 / Developers / 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: 1.0165083

Gitana / 3.2 / Guide / Guide / Publishing / Preview Servers

Preview Servers Before your changes go to Live website i.e. on the Production mode, to discover problems and fix them right away you can set up the Preview Servers and review the content changes instantly. You can look at the default Preview Servers under Manage Project : The default servers are Authoring and Production and are setup to a sample URL which can be modified with your website URL or some API or an Application. To add your Custom Server, you can click on Add Preview Server and set-up

Score: 1.0061228

Gitana / 4.0 / Data Engine / Publishing / Preview Servers

Preview Servers Before your changes go to Live website i.e. on the Production mode, to discover problems and fix them right away you can set up the Preview Servers and review the content changes instantly. You can look at the default Preview Servers under Manage Project : The default servers are Authoring and Production and are setup to a sample URL which can be modified with your website URL or some API or an Application. To add your Custom Server, you can click on Add Preview Server and set-up

Score: 1.0061228

Gitana / 4.0 / Developers / Cookbooks / C# Cookbook

C# Cookbook Getting Started To get started with the C# driver, visit Gitana C# Driver Page or the Github Page. It is written with .NET Core and can be used in any compatible project. You can install the driver via the command line: dotnet add package cloudcms or from within Visual Studio: Install-Package cloudcms Or by adding this to your .csproj file (you may have to adjust the version): Connecting to Gitana

Score: 1.0038486

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

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

Gitana / 4.0 / Home / Overview

Documentation Welcome to the Gitana Documentation Center. Gitana is a secure, enterprise-scale content platform that provides the fastest way to easily and continuously release approved, fresh content changes to your customer-facing APIs, web sites, applications and AI models. It provides everything that you need to power engaging digital experiences. It makes it easy for your business to create, manage and publish amazing content to your customers in real-time. Getting Started If you're new to

Score: 0.9996886

Gitana / 3.2 / Guide / Guide / Policies / Node Policies

Node Policies Node policies provide places where you can hook in behaviors that trigger when nodes are created, updated or deleted within the graph. Nodes may either be entities or associations. This provides an ideal way to plug in your custom behaviors for any definition or content instance within your content graph. The following policies are available: Policy QName Description p:beforeCreateNode Raised before a piece of content is created p:afterCreateNode Raised after a piece of content has

Score: 0.9995097

Gitana / 4.0 / Data Engine / Behaviors / Policies / Node Policies

Node Policies Node policies provide places where you can hook in behaviors that trigger when nodes are created, updated or deleted within the graph. Nodes may either be entities or associations. This provides an ideal way to plug in your custom behaviors for any definition or content instance within your content graph. The following policies are available: Policy QName Description p:beforeCreateNode Raised before a piece of content is created p:afterCreateNode Raised after a piece of content has

Score: 0.9995097

Gitana / 3.2 / Guide / Guide / Cookbooks / PHP Cookbook

PHP Cookbook Getting Started To get started with the PHP driver, visit Gitana PHP Driver Page or the Github Page. It can be used in any composer php project. To install with composer from the command line: composer require cloudcms/cloudcms Connecting to Gitana You can connect to Gitana with the php driver by providing a config array containing your keys, which can be obtained from a gitana.json file. It should look something like: { "clientKey": "{your client key}", "clientSecret": "{y

Score: 0.9866456

Gitana / 4.0 / Developers / Cookbooks / PHP Cookbook

PHP Cookbook Getting Started To get started with the PHP driver, visit Gitana PHP Driver Page or the Github Page. It can be used in any composer php project. To install with composer from the command line: composer require cloudcms/cloudcms Connecting to Gitana You can connect to Gitana with the php driver by providing a config array containing your keys, which can be obtained from a gitana.json file. It should look something like: { "clientKey": "{your client key}", "clientSecret": "{y

Score: 0.9866456

Directed and Undirected Associations

Cloud CMS has the notion of both directed and undirected associations. In the API and within the drivers, when you work with associations, you can query for associations that are "incoming" or "outgoing": These are both directed associations which are relative to a given node. Outgoing means start from this node and find associations pointing to another node. Incoming means find associations that point to me. It also supports the notion of "mutual" associations which are undirected. The source o

Score: 0.98052615