Found 321 results for "access-policies conditions feature"

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

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

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

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

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

Gitana / 4.0 / Data Engine / Aspects / Auto Analyze Text

Auto Analyze Text This section describes features that are coming in 4.0 QName: f:auto-analyze-text With this feature in place, a content instance will automatically have its default binary attachment analyzed using a Text Analyzer service. The extracted analysis and text will then be applied back onto the node, allowing it to benefit from automatic full-text search indexing and other tooling. To use this service, you will first need to set up a Text Analysis Service. The service can either be c

Score: 11.797451

Gitana / 4.0 / Data Engine / Aspects / Auto OCR Extract

Auto OCR Extract This section describes features that are coming in 4.0 QName: f:auto-ocr-extract With this feature in place, a content instance will automatically have its default binary attachment analyzed using an Optical Character Recognition (OCR) service. The extracted analysis and text will then be applied back onto the node, allowing it to benefit from automatic full-text search indexing and other tooling. To use this service, you will first need to set up an OCR Extraction Service. The

Score: 11.797451

Gitana / 3.2 / Guide / Guide / Rules

Rules Content Rules provide a way for you to wire in business logic behind the content graph. Once they're set up, rules run automatically as content is created, updated and deleted within your branch. Rules are content nodes with a JSON payload the describes the Conditions and Actions to be triggered. As with all behaviors, Rule nodes must implement the f:behavior feature. They must be bound to a node upon which to act (either a definition node or a content instance) using a a:has_behavior asso

Score: 11.201192

Gitana / 4.0 / Data Engine / Behaviors / Rules

Rules Content Rules provide a way for you to wire in business logic behind the content graph. Once they're set up, rules run automatically as content is created, updated and deleted within your branch. Rules are content nodes with a JSON payload the describes the Conditions and Actions to be triggered. As with all behaviors, Rule nodes must implement the f:behavior feature. They must be bound to a node upon which to act (either a definition node or a content instance) using a a:has_behavior asso

Score: 11.201192

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

Conditions This section describes features that are coming in 4.0 Access Policy Conditions And Branch Changeset Data Store Feature ID Locale Not Or Path Project Property Reference Type Type QName

Score: 10.699244

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

Conditions This section describes features that are coming in 4.0 Access Policy Conditions And Branch Changeset Data Store Feature ID Locale Not Or Path Project Property Reference Type Type QName

Score: 10.699244

Gitana / 3.2 / Guide / Guide / Features

Features Features are aspect-oriented, cross-cutting concerns that can be applied to nodes. Once applied, they may introduce new behaviors and metadata to your content objects. You can use features to describe cross-cutting or aspect-oriented concerns that can be plugged onto your content nodes at any time. Features may participate in the inheritance tree of content types or they may be injected anywhere and at any point. There are a number of out-of-the-box features provided by Cloud CMS, inclu

Score: 9.147824

Gitana / 4.0 / Data Engine / Aspects / Overview

Features Features are aspect-oriented, cross-cutting concerns that can be applied to nodes. Once applied, they may introduce new behaviors and metadata to your content objects. You can use features to describe cross-cutting or aspect-oriented concerns that can be plugged onto your content nodes at any time. Features may participate in the inheritance tree of content types or they may be injected anywhere and at any point. There are a number of out-of-the-box features provided by Cloud CMS, inclu

Score: 9.147824

Gitana / 3.2 / Guide / Guide / Content Modeling

Content Modeling A content model consists of definitions which describe your project's content types, properties, graph associations, and the aspect-oriented features that Cloud CMS uses to ensure data consistency, integrity and validity when content is created, updated or deleted. In Cloud CMS, all content modeling is done using JSON and more specifically, JSON Schema. JSON Schema provides an elegant and well-adopted model for describing the types for content objects, properties and other neste

Score: 8.397309

Gitana / 4.0 / Data Engine / Content Models / Overview

Content Modeling A content model consists of definitions which describe your project's content types, properties, graph associations, and the aspect-oriented features that Cloud CMS uses to ensure data consistency, integrity and validity when content is created, updated or deleted. In Cloud CMS, all content modeling is done using JSON and more specifically, JSON Schema. JSON Schema provides an elegant and well-adopted model for describing the types for content objects, properties and other neste

Score: 8.397309

Gitana / 4.0 / Data Engine / Content Models / Default Paths

Default Paths Your content types define schemas that Cloud CMS uses to render intuitive forms for content entry. In addition, content types let you configure persistence paths so that JSON documents created using these forms are automatically saved in a directory structure that you intend. Paths support templated variables so that the path can be dynamic. It can depend on the values having been entered. For example, let's suppose I have the content type for an article, like this: { "title":

Score: 7.294821

Gitana / 3.2 / Guide / Guide / Actions / Add Feature

Add Feature ID: addFeature Adds a feature to a node. The configuration for this feature is described using JSON Schema like this: { "title": "Add Feature", "properties": { "qname": { "title": "Feature QName", "type": "string" }, "config": { "title": "Feature Configuration", "type": "object" } } } See the examples below for more detail. Example #1 Let's say we want to automatically configure the filename

Score: 6.166422

Gitana / 4.0 / Data Engine / Behaviors / Actions / Add Feature

Add Feature ID: addFeature Adds a feature to a node. The configuration for this feature is described using JSON Schema like this: { "title": "Add Feature", "properties": { "qname": { "title": "Feature QName", "type": "string" }, "config": { "title": "Feature Configuration", "type": "object" } } } See the examples below for more detail. Example #1 Let's say we want to automatically configure the filename

Score: 6.166422

Gitana / 3.2 / Guide / Guide / Actions / Remove Feature

Remove Feature ID: removeFeature Removes a feature from a node. { "title": "Remove Feature", "properties": { "qname": { "title": "Feature QName", "type": "string" } } }

Score: 6.1615887

Gitana / 4.0 / Data Engine / Behaviors / Actions / Remove Feature

Remove Feature ID: removeFeature Removes a feature from a node. { "title": "Remove Feature", "properties": { "qname": { "title": "Feature QName", "type": "string" } } }

Score: 6.1615887

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

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

Gitana / 3.2 / Guide / Guide / Features / Auto Analyze Text

Auto Analyze Text This section describes features that are coming in 4.0 QName: f:auto-analyze-text With this feature in place, a content instance will automatically have its default binary attachment analyzed using a Text Analyzer service. The extracted analysis and text will then be applied back onto the node, allowing it to benefit from automatic full-text search indexing and other tooling. To use this service, you will first need to set up a Text Analysis Service. The service can either be c

Score: 5.342344

Gitana / 3.2 / Guide / Guide / Features / Auto OCR Extract

Auto OCR Extract This section describes features that are coming in 4.0 QName: f:auto-ocr-extract With this feature in place, a content instance will automatically have its default binary attachment analyzed using an Optical Character Recognition (OCR) service. The extracted analysis and text will then be applied back onto the node, allowing it to benefit from automatic full-text search indexing and other tooling. To use this service, you will first need to set up an OCR Extraction Service. The

Score: 5.342344

Gitana / 3.2 / Guide / Guide / UI Developers Guide / Evaluators / context-document-has-feature

context-document-has-feature If a Document is currently being observed and has a specific feature. { "evaluator": "context-document-has-feature", "condition": "{featureId}" } Example: { "evaluator": "context-document-has-feature", "condition": "f:audit" }

Score: 4.8349743

Gitana / 4.0 / Developers / User Interface Customization / Evaluators / context-document-has-feature

context-document-has-feature If a Document is currently being observed and has a specific feature. { "evaluator": "context-document-has-feature", "condition": "{featureId}" } Example: { "evaluator": "context-document-has-feature", "condition": "f:audit" }

Score: 4.8349743