Found 533 results for "policies node"

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

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

@queryOne Supports all of the same mechanics as the @query tag but keeps only the first result. 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 relativ

Score: 0.8717022

Gitana / 3.2 / Guide / Guide / Deployment / Deployment Handlers / Azure Blob Storage Deployment Handler

Azure Blob Storage Deployment Handler Handles the deployment of one or more Deployment Packages to an Azure Blob Storage Container. The Azure Blob Storage Container is described by: connectionString containerName And optionally: prefix The contents of the Deployment Packages will be deployed sequentially to the target location. If any of the content within the Deployment Packages fails to copy, it will simply be skipped. Other content objects will be allowed to proceed unabated. Configurat

Score: 0.8717022

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

@queryOne Supports all of the same mechanics as the @query tag but keeps only the first result. 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 relativ

Score: 0.8717022

Gitana / 4.0 / Data Engine / Aspects / Auto Transcribe

Auto Transcribe This section describes features that are coming in 4.0 QName: f:auto-transcribe With this feature in place, a content instance will automatically have an audio attachment converted to text using speech-to-text conversion. The generated text will be stored back to an attachment named transcription (as a text/plain file). To use this service, you will first need to set up a Transcription Service. The service can either be configured as the default Transcription Service for your Pro

Score: 0.8717022

Gitana / 4.0 / Data Engine / Deployment / Deployment Handlers / Azure Blob Storage Deployment Handler

Azure Blob Storage Deployment Handler Handles the deployment of one or more Deployment Packages to an Azure Blob Storage Container. The Azure Blob Storage Container is described by: connectionString containerName And optionally: prefix The contents of the Deployment Packages will be deployed sequentially to the target location. If any of the content within the Deployment Packages fails to copy, it will simply be skipped. Other content objects will be allowed to proceed unabated. Configurat

Score: 0.8717022

Proxy API calls

Whenever a resulting URL looks something like: https://api.cloudcms.com/repositories/f0fb4efd3de07c54420a/branches/9bcdbfea8f2d900f0387/nodes//attachments/thumb.jpg It works great as an API URL but not necessarily as one that can be resolved by the end user's browser. In a typical Node.js-based architecture, you have the User’s browser Node.js application server Cloud CMS backend API The URL generated above is the URL directly to the resource in the backend API. What you really would pre

Score: 0.8717022

Gitana / 3.2 / Guide / Guide / Features / Knowledge Space

Knowledge Space QName: f:knowledge-space Used to indicate that a node should behave as a Knowledge Space. A Knowledge Space has zero or more knowledge properties. A knowledge property is a regular old property on your JSON object that is special in that its value may propagate to other nodes automatically. A Knowledge Space is holds the "master value" for those knowledge properties. When those properties change, their new values are pushed to any other nodes that are sharing the knowledge from t

Score: 0.86502457

Gitana / 4.0 / Data Engine / Aspects / Knowledge Space

Knowledge Space QName: f:knowledge-space Used to indicate that a node should behave as a Knowledge Space. A Knowledge Space has zero or more knowledge properties. A knowledge property is a regular old property on your JSON object that is special in that its value may propagate to other nodes automatically. A Knowledge Space is holds the "master value" for those knowledge properties. When those properties change, their new values are pushed to any other nodes that are sharing the knowledge from t

Score: 0.86502457

Gitana / 3.2 / Guide / Guide / Content Modeling / Attachment Properties

Attachment Properties Cloud CMS provides support for properties that auto-manage the creation, update and deletion of binary attachments for a node. These are known as "attachment properties". They provide an easy way for editorial users to manage binary attachments from within a form. Attachment properties provide the following benefits: They provide an easy form-driven way for editorial users to upload and manage named attachments of a node. They automatically reflect important attachment info

Score: 0.8543066

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

@dependency Indicates that the cache state for a WCM-generated page has a dependency. Dependencies play two important roles within Cloud CMS. First, they indicate to the runtime whether the previously cached output for a page may be used to service a future request ("requirements"). And second, they identify which data objects were used to build the page output ("produces"). This latter information is then be used to invalidate page objects when content items change within the Cloud CMS editoria

Score: 0.8543066

Gitana / 3.2 / Guide / Guide / Content Modeling / Definitions / Feature Definition

Feature Definition A Feature Definition is a cross-cutting concern or Aspect that you can apply arbitrarily to content instances or content types (to apply to all instances of a type). A Feature Definition is used to optionally describe additional schema that should be applied to a content or association type. Feature Definitions also endow content instances with special behaviors. Feature Definitions are defined in much the same way as Types or Associations. Each Feature has a QName and the JSO

Score: 0.8543066

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

@dependency Indicates that the cache state for a WCM-generated page has a dependency. Dependencies play two important roles within Cloud CMS. First, they indicate to the runtime whether the previously cached output for a page may be used to service a future request ("requirements"). And second, they identify which data objects were used to build the page output ("produces"). This latter information is then be used to invalidate page objects when content items change within the Cloud CMS editoria

Score: 0.8543066

Gitana / 4.0 / Data Engine / Content Models / Attachment Properties

Attachment Properties Cloud CMS provides support for properties that auto-manage the creation, update and deletion of binary attachments for a node. These are known as "attachment properties". They provide an easy way for editorial users to manage binary attachments from within a form. Attachment properties provide the following benefits: They provide an easy form-driven way for editorial users to upload and manage named attachments of a node. They automatically reflect important attachment info

Score: 0.8543066

Gitana / 4.0 / Data Engine / Content Models / Definitions / Feature Definition

Feature Definition A Feature Definition is a cross-cutting concern or Aspect that you can apply arbitrarily to content instances or content types (to apply to all instances of a type). A Feature Definition is used to optionally describe additional schema that should be applied to a content or association type. Feature Definitions also endow content instances with special behaviors. Feature Definitions are defined in much the same way as Types or Associations. Each Feature has a QName and the JSO

Score: 0.8543066

Gitana / 3.2 / Guide / Guide / Conditions

Conditions Conditions provide a way for Rules to evaluate their content and their environment prior to determining whether to proceed with the execution of their Actions. A Condition might be a simple check such as checking to see whether the current content item has a certain property value. But it also might consist of more complex logic chains utilizing and and or blocks. Cloud CMS provides a number of out-of-the-box Conditions: And Merge Node Has Attachment Or Property Changed Property Compa

Score: 0.8461415

Gitana / 3.2 / Guide / Guide / Conditions / And

And The and condition tests whether one or more sub-conditions are all true. This joins the sub-conditions together in a logical AND. JSON Schema { "title": "And", "properties": { "conditions": { "type": "array", "items": { "type": "object", "properties": { "type": { "type": "string" }, "config": { "type": "object"

Score: 0.8461415

Gitana / 3.2 / Guide / Guide / Workflow / Workflow Handlers / Remove Features

Remove Features Type: removeFeatures This handler removes features from a node that is part of the workflow's payload. This can be used to remove one or more features from your content instances as they flow through your workflow. The config for this handler is as follows: { "features": [{ "qname": "" }] } Each of the features identified by qname will be removed from the documents attached to the workflow payload. Here is an example configuration which assumes tha

Score: 0.8461415

Gitana / 4.0 / Data Engine / Behaviors / Conditions

Conditions Conditions provide a way for Rules to evaluate their content and their environment prior to determining whether to proceed with the execution of their Actions. A Condition might be a simple check such as checking to see whether the current content item has a certain property value. But it also might consist of more complex logic chains utilizing and and or blocks. Cloud CMS provides a number of out-of-the-box Conditions: And Merge Node Has Attachment Or Property Changed Property Compa

Score: 0.8461415

Gitana / 4.0 / Data Engine / Behaviors / Conditions / And

And The and condition tests whether one or more sub-conditions are all true. This joins the sub-conditions together in a logical AND. JSON Schema { "title": "And", "properties": { "conditions": { "type": "array", "items": { "type": "object", "properties": { "type": { "type": "string" }, "config": { "type": "object"

Score: 0.8461415

Gitana / 4.0 / Data Engine / Workflow / Workflow Handlers / Remove Features

Remove Features Type: removeFeatures This handler removes features from a node that is part of the workflow's payload. This can be used to remove one or more features from your content instances as they flow through your workflow. The config for this handler is as follows: { "features": [{ "qname": "" }] } Each of the features identified by qname will be removed from the documents attached to the workflow payload. Here is an example configuration which assumes tha

Score: 0.8461415

Gitana / 3.2 / Guide / Guide / Conditions / Property Comparison

Property Comparison The propertyComparison condition tests whether a given property matches a comparison to a given value. You can use this to test whether a value is greater than or less than another value (among other operations). JSON Schema { "title": "Property Comparison", "properties": { "property": { "type": "string", "title": "Property Name" }, "comparison": { "type": "string", "title": "Comparison",

Score: 0.83687127

Gitana / 3.2 / Guide / Guide / Features / Word Count

Word Count QName: f:word-count Indicates that a node should track the number of words in each text property. Configuration Word Count Example Suppose we have a content type (my:article) that looks like this: { "_qname": "my:article", "_type": "d:type", "type": "object", "properties":{ "title": { "type": "string" }, "body": { "type": "string" } }, "mandatoryFeatures": { "f:word-count": {} } } Now we create

Score: 0.83687127

Gitana / 4.0 / Data Engine / Aspects / Word Count

Word Count QName: f:word-count Indicates that a node should track the number of words in each text property. Configuration Word Count Example Suppose we have a content type (my:article) that looks like this: { "_qname": "my:article", "_type": "d:type", "type": "object", "properties":{ "title": { "type": "string" }, "body": { "type": "string" } }, "mandatoryFeatures": { "f:word-count": {} } } Now we create

Score: 0.83687127

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

Property Comparison The propertyComparison condition tests whether a given property matches a comparison to a given value. You can use this to test whether a value is greater than or less than another value (among other operations). JSON Schema { "title": "Property Comparison", "properties": { "property": { "type": "string", "title": "Property Name" }, "comparison": { "type": "string", "title": "Comparison",

Score: 0.83687127

Programmatically create content in a folder?

The Cloud CMS content API lets you work with JSON to create any kind of content you'd like. It supports any JSON structure you desire and also supports a number of special properties that you can use to make life easier for you. These special properties are: _rootNodeId - The mount node ID of the root against which relatives path are computed. By default, this is the root of the repository. In general, it isn't necessary to use this property unless you have multiple mount nodes configured. And m

Score: 0.8336481