Found 176 results for "access-policies conditions reference"

The search executed in 0.001155705 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.153793

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

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

Reference This section describes features that are coming in 4.0 The reference condition allows you to constrain a policy statement so that it applies to entities that match a given Reference. This condition supports regular expressions, allowing you to focus in on a single Reference or wildcard expressions within an Reference. In Cloud CMS, a Reference is a string that uniquely locates an item within the system. It takes on a structure that looks like one of the following: {type}://{platformId}

Score: 16.421913

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

Reference This section describes features that are coming in 4.0 The reference condition allows you to constrain a policy statement so that it applies to entities that match a given Reference. This condition supports regular expressions, allowing you to focus in on a single Reference or wildcard expressions within an Reference. In Cloud CMS, a Reference is a string that uniquely locates an item within the system. It takes on a structure that looks like one of the following: {type}://{platformId}

Score: 16.421913

Gitana / 4.0 / Data Engine / Content Models / References

References References provide a way for you to link two definitions together so as to reuse one of the definitions in the other. It gives you a way to centrally define something and then have that something's schema get reused in other definitions in your content model. For example, suppose you have an my:author definition that looks like this: { "type": "object", "properties": { "firstName": { "type": "string", "title": "First Name" }, "la

Score: 14.497503

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

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

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

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

Gitana / 3.2 / Guide / Guide / Search / Query String Reference

Query String Reference Cloud CMS lets you search for your content using either a text-based query string or a JSON block. These two methods are fairly equivalent for most typical operations. They provide two ways to express a search operation that will execute within Elastic Search. They are expressions of the Elastic Search DSL. This portion of the documentation goes into some of things you can do with the former, textual representation of an Elastic Search query string. In Cloud CMS, you can t

Score: 5.572946

Gitana / 4.0 / Data Engine / Discovery / Search / Query String Reference

Query String Reference Cloud CMS lets you search for your content using either a text-based query string or a JSON block. These two methods are fairly equivalent for most typical operations. They provide two ways to express a search operation that will execute within Elastic Search. They are expressions of the Elastic Search DSL. This portion of the documentation goes into some of things you can do with the former, textual representation of an Elastic Search query string. In Cloud CMS, you can t

Score: 5.572946

Gitana / 3.2 / Guide / Guide / Content Modeling / References

References References provide a way for you to link two definitions together so as to reuse one of the definitions in the other. It gives you a way to centrally define something and then have that something's schema get reused in other definitions in your content model. For example, suppose you have an my:author definition that looks like this: { "type": "object", "properties": { "firstName": { "type": "string", "title": "First Name" }, "la

Score: 5.3607316

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

And This section describes features that are coming in 4.0 The and condition lets you perform a logical AND operation across multiple sub-conditions. Configuration { "type": "and", "config": { "conditions": [ ... subconditions ] } } Sample #1 This policy document allows a principal to read content from the /products so long as it is of type my:article. { "title": "My Sample Policy", "statements": [{ "action": "grant", "roles": ["co

Score: 2.8675368

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

And This section describes features that are coming in 4.0 The and condition lets you perform a logical AND operation across multiple sub-conditions. Configuration { "type": "and", "config": { "conditions": [ ... subconditions ] } } Sample #1 This policy document allows a principal to read content from the /products so long as it is of type my:article. { "title": "My Sample Policy", "statements": [{ "action": "grant", "roles": ["co

Score: 2.8675368

Gitana / 3.2 / Guide / Guide / Conditions / Or

Or The or condition tests whether at least one of multiple sub-conditions are true. This joins the sub-conditions together in a logical OR. JSON Schema { "title": "Or", "properties": { "conditions": { "type": "array", "items": { "type": "object", "properties": { "type": { "type": "string" }, "config": { "type": "object

Score: 2.8584485

Gitana / 4.0 / Data Engine / Behaviors / Conditions / Or

Or The or condition tests whether at least one of multiple sub-conditions are true. This joins the sub-conditions together in a logical OR. JSON Schema { "title": "Or", "properties": { "conditions": { "type": "array", "items": { "type": "object", "properties": { "type": { "type": "string" }, "config": { "type": "object

Score: 2.8584485

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

Path This section describes features that are coming in 4.0 The path condition allows you to constrain a policy statement so that it applies to content nodes that exist at a matching path. This condition supports regular expressions, allowing you to focus in on a single path, sub paths or arbitrary matching path structures. Configuration { "type": "path", "config": { "path": "{value regex}" } } Samples This policy document grants the Consumer role to all content in the path

Score: 2.7952228

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

Path This section describes features that are coming in 4.0 The path condition allows you to constrain a policy statement so that it applies to content nodes that exist at a matching path. This condition supports regular expressions, allowing you to focus in on a single path, sub paths or arbitrary matching path structures. Configuration { "type": "path", "config": { "path": "{value regex}" } } Samples This policy document grants the Consumer role to all content in the path

Score: 2.7952228

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

Or This section describes features that are coming in 4.0 The or condition lets you perform a logical OR operation across multiple sub-conditions. Configuration { "type": "or", "config": { "conditions": [ ... subconditions ] } } Sample #1 This policy document allows a principal to read content from the /products and /images folders. { "title": "My Sample Policy", "statements": [{ "action": "grant", "roles": ["consumer"], "c

Score: 2.7921557

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

Or This section describes features that are coming in 4.0 The or condition lets you perform a logical OR operation across multiple sub-conditions. Configuration { "type": "or", "config": { "conditions": [ ... subconditions ] } } Sample #1 This policy document allows a principal to read content from the /products and /images folders. { "title": "My Sample Policy", "statements": [{ "action": "grant", "roles": ["consumer"], "c

Score: 2.7921557

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

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

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

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

Gitana / 3.2 / Guide / Guide / UI Developers Guide / Contexts / rule-subcontext

rule-subcontext [ { "config": { "rule-subcontext": { "items": [ { "key": "rule", "header": true, "title": "Rule", "items": [ { "key": "properties", "title": "Properties", "uri": "{projectUri}/rules/{documentId}", "order": 1000 }, { "key": "binding", "title": "Policies",

Score: 2.7274833