Found 533 results for "policies node"

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

Gitana / 3.2 / Guide / Guide / Tree

Tree Content that is organized into folders can be retrieved using the Tree API. The Tree API lets you pull back an entire path-based folder and file structure of content within a single API call. The API call lets you specify a root node, a maximum depth to traverse down the path structure, paths that should be automatically expanded and query terms for filtering of root nodes. The Tree API is deal to support a variety of cases including: retrieval of multiple deeply-nested paths within a singl

Score: 1.0340796

Gitana / 4.0 / Data Engine / Discovery / Tree

Tree Content that is organized into folders can be retrieved using the Tree API. The Tree API lets you pull back an entire path-based folder and file structure of content within a single API call. The API call lets you specify a root node, a maximum depth to traverse down the path structure, paths that should be automatically expanded and query terms for filtering of root nodes. The Tree API is deal to support a variety of cases including: retrieval of multiple deeply-nested paths within a singl

Score: 1.0340796

Gitana / 3.2 / Guide / Guide / Features / Knowledge Recipient

Knowledge Recipient QName: f:knowledge-recipient Used internally to identify that a node has received one or more knowledge properties from a source Knowledge Space. These properties exist on the JSON but may have their values overwritten at any time. The indicated properties are not "mastered" on this node but rather receive their values from elsewhere. Any node that is marked as a f:knowledge-recipient will have at least one a:shares-knowledge association binding it back to the source of the p

Score: 1.0311369

Gitana / 4.0 / Data Engine / Aspects / Knowledge Recipient

Knowledge Recipient QName: f:knowledge-recipient Used internally to identify that a node has received one or more knowledge properties from a source Knowledge Space. These properties exist on the JSON but may have their values overwritten at any time. The indicated properties are not "mastered" on this node but rather receive their values from elsewhere. Any node that is marked as a f:knowledge-recipient will have at least one a:shares-knowledge association binding it back to the source of the p

Score: 1.0311369

Gitana / 3.2 / Guide / Guide / Features / Audit

Audit QName: f:audit Marks a content node as auditable. Operations against this node will be logged and recorded by the Cloud CMS auditing service and stored as audit records on your platform. These audit records can then be viewed within the Cloud CMS user interface or downloaded for use in third-party reporting systems. Configuration Audit Example { "title": "My Content Instance", "_features": { "f:audit": { } } }

Score: 1.0304548

Gitana / 4.0 / Data Engine / Aspects / Audit

Audit QName: f:audit Marks a content node as auditable. Operations against this node will be logged and recorded by the Cloud CMS auditing service and stored as audit records on your platform. These audit records can then be viewed within the Cloud CMS user interface or downloaded for use in third-party reporting systems. Configuration Audit Example { "title": "My Content Instance", "_features": { "f:audit": { } } }

Score: 1.0304548

Gitana / 3.2 / Guide / Guide / Conditions / Property Equals

Property Equals The propertyEquals condition tests whether a node property is equal to a given value. JSON Schema { "title": "Property Equals", "properties": { "property": { "type": "string", "title": "Property Name" }, "value": { "type": "string", "title": "Value" } } } Example #1 Suppose you wanted to test whether a node has a property called published which was set to true. You could set up the condit

Score: 1.0269911

Gitana / 4.0 / Data Engine / Behaviors / Conditions / Property Equals

Property Equals The propertyEquals condition tests whether a node property is equal to a given value. JSON Schema { "title": "Property Equals", "properties": { "property": { "type": "string", "title": "Property Name" }, "value": { "type": "string", "title": "Value" } } } Example #1 Suppose you wanted to test whether a node has a property called published which was set to true. You could set up the condit

Score: 1.0269911

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

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

Stats Sum Counter QName: f:stats-sum-counter Applied to an association to indicate that a statistics counter from one of end of the association should be aggregated up into another counter on the other end of the association. This feature builds on the existing Node Statistics capabilities of Cloud CMS by letting you define custom sum counters from one end of an association to be applied to the other end. Statistics counters are accumulated once on create and decremented once on delete. Configur

Score: 1.0206549

Gitana / 4.0 / Data Engine / Aspects / Stats Sum Counter

Stats Sum Counter QName: f:stats-sum-counter Applied to an association to indicate that a statistics counter from one of end of the association should be aggregated up into another counter on the other end of the association. This feature builds on the existing Node Statistics capabilities of Cloud CMS by letting you define custom sum counters from one end of an association to be applied to the other end. Statistics counters are accumulated once on create and decremented once on delete. Configur

Score: 1.0206549

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

Gitana / 3.2 / Guide / Guide / Deployment / Deployment Mappings

Deployment Mappings The following Deployment Handlers supports the deployment of resources from Cloud CMS to files or file system equivalents: S3 Deployment Handler File System Deployment Handler FTP Deployment Handler These Deployment Handlers all have the common function. They must work with content from Cloud CMS, consisting of Nodes, Associations, binary attachments and a potentially complex content graph of relationships. They must take that content and then map it down into a file system c

Score: 1.0143564

Gitana / 4.0 / Developers / Drivers / Go

Go Connect your Go applications to Gitana Latest Version Version undefined Date Current version: v0.1.3. Released Jun 13, 2022 The Gitana Go driver allows you to easily connect your Go applications to the Gitana server. Currently supports the following functionality: Connect to and refresh access tokens with the API Read platform, branches, repositories, projects, releases Read, query, search, create, update, and delete nodes Manage node translations, versions, associations, attachments Make gra

Score: 1.0143564

Gitana / 4.0 / Data Engine / Deployment / Deployment Mappings

Deployment Mappings The following Deployment Handlers supports the deployment of resources from Cloud CMS to files or file system equivalents: S3 Deployment Handler File System Deployment Handler FTP Deployment Handler These Deployment Handlers all have the common function. They must work with content from Cloud CMS, consisting of Nodes, Associations, binary attachments and a potentially complex content graph of relationships. They must take that content and then map it down into a file system c

Score: 1.0143564

Gitana / 3.2 / Guide / Guide / Actions / Send Email

Send Email ID: sendEmail Sends an email to a recipient. To send an email using this action, it is required that you identify: The email provider to be used to send the email (applicationId and emailProviderId The recipient of the email (using to or toPrincipalId) Who the email is from (either using from or the default from value of your email provider) The body of the email (by either specifying body directly, via a node reference or via an Email Template reference) The subject of the email All

Score: 1.0142576

Gitana / 4.0 / Data Engine / Behaviors / Actions / Send Email

Send Email ID: sendEmail Sends an email to a recipient. To send an email using this action, it is required that you identify: The email provider to be used to send the email (applicationId and emailProviderId The recipient of the email (using to or toPrincipalId) Who the email is from (either using from or the default from value of your email provider) The body of the email (by either specifying body directly, via a node reference or via an Email Template reference) The subject of the email All

Score: 1.0142576

Gitana / 4.0 / Forms / API / Connectors

Connectors Alpaca supports Connectors as a means for loading schema, options, view and data information from remote data sources. By default, Alpaca comes with a default connector that handles loading of data from public / unprotected HTTP/HTTPS URLs. Connectors are used to load information based on what they receive in the following properties: schemaSource optionsSource dataSource viewSource Information loaded from any of these sources is merged with information that is fed directly into Alpac

Score: 1.0123794

Gitana / 4.0 / Developers / Drivers / C#

C# Driver Connect your .NET applications to Gitana Latest Version Version undefined Date The Gitana C# driver allows you to easily connect your C# and .NET applications to the Gitana server. Currently supports the following functionality: Connect to and refresh access tokens with the API Read platform, branch, and repositories Read, query, search, create, update, and delete nodes Installation Install this driver as you would any other NuGet package. Command Line: dotnet add package cloudcms Vis

Score: 1.00986

Gitana / 3.2 / Guide / Guide / Features / Related

Related QName: f:related This feature is applied internally to nodes that are on the other end of a relator association to indicate that the target node is related to the source node. This feature acts as a marker to tell Cloud CMS to consider the related nodes and the relator association at persistence time so the properties can be managed more efficiently in terms of mapping values from one end of the relationship to the other. There is no need to apply or work with this feature manually. For

Score: 1.003383

Gitana / 4.0 / Data Engine / Aspects / Related

Related QName: f:related This feature is applied internally to nodes that are on the other end of a relator association to indicate that the target node is related to the source node. This feature acts as a marker to tell Cloud CMS to consider the related nodes and the relator association at persistence time so the properties can be managed more efficiently in terms of mapping values from one end of the relationship to the other. There is no need to apply or work with this feature manually. For

Score: 1.003383

How does Cloud CMS work with a CDN

There are a few places where this either occurs automatically if you're using our hosted service or can occur optionally if you're either running within Docker containers on your own or integrating to custom CDN endpoints. First, the API itself can be fronted by a CDN that supports fallback lookup to an origin server. In this case, we recommend Amazon CloudFront with short-lived TTLs on cache headers. More specifically, you can use Amazon's API Gateway to get caching coverage across multiple geo

Score: 1.0010629

Gitana / 3.2 / Guide / Guide / Application Server / Tags / @query

@query Queries for nodes and makes those nodes available to the template. Parameters parameter required description type the type of node to query for (definition QName) sort the field to sort on sortDirection the direction to sort in (either 1 for ascending or -1 for descending) limit the number of records to return fields comma separated list of property names to include in query results skip a position to skip ahead to in the record set scope if "page", then only relatives related to the curr

Score: 0.99929106

Gitana / 4.0 / Developers / Application Server / Tags / @query

@query Queries for nodes and makes those nodes available to the template. Parameters parameter required description type the type of node to query for (definition QName) sort the field to sort on sortDirection the direction to sort in (either 1 for ascending or -1 for descending) limit the number of records to return fields comma separated list of property names to include in query results skip a position to skip ahead to in the record set scope if "page", then only relatives related to the curr

Score: 0.99929106

Gitana / 3.2 / Guide / Guide / Actions / Web Hook

Web Hook ID: webhook Makes a remote call to an HTTP endpoint. Core Configuration Property Type Required Default Description url text true The fully-qualified HTTP endpoint (i.e. http://www.myserver.com/endpoint) method text false The HTTP method to invoke (default: POST) username text false The Basic authentication username. password text false The Basic authentication password. payload object false The JSON payload for PUT and POST calls. headers object false The headers to apply to the HTTP ca

Score: 0.9972738