Found 528 results for "policies node"

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

Gitana 4.0 / Content Engine / Behaviors / Conditions / Property Changed

Monitor node property changes with customizable conditions, including property, old, and new values. Trigger actions on state changes efficiently.

Score: 1.02327

Gitana 3.2 / Guide / Guide / Cookbooks / REST API Cookbook

Discover Cloud CMS REST API: detailed guides on OAuth2 authentication, API requests via HTTP clients, node creation, associations, querying, and searching.

Score: 1.0226005

Gitana 4.0 / Developers / Cookbooks / REST API Cookbook

Explore our comprehensive REST API Cookbook, featuring guides on Gitana OAuth2 connection, node creation, associations, and MongoDB queries.

Score: 1.0226005

Gitana 3.2 / Guide / Guide / Conditions / Or

Learn how to use logical or conditions in JSON schemas, with examples for articles and press releases.

Score: 1.0175611

Gitana 4.0 / Content Engine / Behaviors / Conditions / Or

Learn how to use logical or conditions in JSON schemas, with examples for articles and press releases.

Score: 1.0175611

Gitana 3.2 / Guide / Guide / Cookbooks / PHP Cookbook

Learn to use Gitana's PHP driver for database connections, code samples, and advanced querying with this comprehensive guide.

Score: 1.0134474

Gitana 4.0 / Developers / Cookbooks / PHP Cookbook

Learn PHP with Gitana's PHP Driver. Connect to Cloud CMS using examples and code snippets for integration.

Score: 1.0134474

Gitana 3.2 / Guide / Guide / Features / Knowledge Recipient

Cloud CMS manages Knowledge Recipient, identifying nodes receiving knowledge properties from a source, ensuring data integrity and association.

Score: 1.0119153

Gitana 4.0 / Content Engine / Aspects / Knowledge Recipient

Cloud CMS manages Knowledge Recipient, identifying nodes receiving knowledge properties from a source, ensuring data integrity and association.

Score: 1.0119153

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.0119153

Gitana 3.2 / Guide / Guide / Features / Inline Links

Enhance text parsing with automatic link discovery and prevent deletion of linked docs in Cloud CMS, ensuring robust content management.

Score: 1.01028

Gitana 4.0 / Content Engine / Aspects / Inline Links

Enhance your text-based markup with automatic inline link detection and management, ensuring seamless content tracking and reference updates.

Score: 1.01028

Gitana 3.2 / Guide / Guide / Tree

Retrieve and manage entire path-based folder structures with the Tree API, supporting dynamic loading, filtering, and composite queries.

Score: 1.0096273

Gitana 4.0 / Content Engine / Tree

Retrieve and manage entire path-based folder structures with the Tree API, supporting dynamic loading, filtering, and composite queries.

Score: 1.0096273

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.0077529

Gitana 3.2 / Guide / Guide / Features / Rendition

Learn about the f:rendition feature, which auto-generates nodes from renditionable content, requiring no configuration.

Score: 1.0069803

Gitana 4.0 / Content Engine / Aspects / Rendition

Learn about the f:rendition feature, which auto-generates nodes from renditionable content, requiring no configuration.

Score: 1.0069803

Gitana 3.2 / Guide / Guide / Features / Deployment Config

Optimize deployment processes with the f:deployment-config feature, guiding handlers like S3, FTP, and File System for seamless, structured deployment.

Score: 1.006455

Gitana 4.0 / Content Engine / Aspects / Deployment Config

Optimize your deployment with Gitana by using f:deployment-config to map content to paths for S3, FTP, and file systems effectively.

Score: 1.006455

Gitana 3.2 / Guide / Guide / Scripting / Workflow Transition

Discover the components of Workflow Transition, including key properties like fromNodeId, id, and toNodeId, within our detailed guide.

Score: 1.0038856

Workflow Transition

Discover the components of Workflow Transition, including key properties like fromNodeId, id, and toNodeId, within our detailed guide.

Score: 1.0038856

Gitana 3.2 / Guide / Guide / Features / Stats Sum Counter

Leverage Cloud CMS Stats Sum Counter to aggregate custom statistics between associations, enhancing data insights and content popularity.

Score: 1.0034156

Gitana 4.0 / Content Engine / Aspects / Stats Sum Counter

Leverage Cloud CMS Stats Sum Counter to aggregate custom statistics between associations, enhancing data insights and content popularity.

Score: 1.0034156

What is the reason for "Failed to index node"?

If you scan your log entries and see "Failed to index node", this indicates that Elastic Search failed to update its index for a node. Cloud CMS tells Elastic Search to updates its index whenever a node is created or updated. When a node is deleted, Cloud CMS tells Elastic Search to remove the node from its index. This error message means that Elastic Search failed to update the index and therefore the index wasn't updated. If you open up the error, you may see further information that indicates

Score: 0.99825287

How do I retrieve the folder path for my content?

In Cloud CMS, you may choose to associate nodes with folders. This allows the content to be worked with by editorial teams such that they can navigate to content within folders, move content between folders and generally organize their content as they wish. It also allows for content to be retrieved by path via the API, if you wish. Technically speaking, Cloud CMS does not require folders or paths. In fact, plenty of customers use Cloud CMS in such a way that they don't require folders at all. C

Score: 0.9936482