Found 75 results for "conditions node-has-attachment"

The search executed in 7.85212E-4 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 / 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.662451

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Gitana / 4.0 / Developers / User Interface Customization / 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.7269328

Gitana / 4.0 / Data Engine / Security / Access Policies

Access Policies Access Control Policy documents are JSON documents that live at the Platform level. They provide a recipe that describes the access control that should be granted to any policy holder that is assigned the policy. Users may be assigned the policy directly, via a group or via a Team. Policy Document The Access Control Policy document provides a series of Statements that declare truths about what authority rights the policy holder should have over resources in the system. Each State

Score: 2.6974306

Gitana / 3.2 / Guide / Guide / Access Policies

Access Policies This section describes features that are coming in 4.0 Access Control Policy documents are JSON documents that live at the Platform level. They provide a recipe that describes the access control that should be granted to any policy holder that is assigned the policy. Users may be assigned the policy directly, via a group or via a Team. Policy Document The Access Control Policy document provides a series of Statements that declare truths about what authority rights the policy hold

Score: 2.6698523

Enterprise Access Policies in Gitana 4.0 (Part 1)

In this article, we'll take a look at Access Policies -- a powerful, new feature in Gitana 4.0 that allows organizations to set up and guarantee compliance with complex, enterprise-wide security requirements. Access Policies build upon the existing access control facilities provided which include per-object ACLs and broader, team-based ACLs. They extend those capabilities by allowing administrators to express access rights in a broad sweeping and prescriptive manner -- one that allows for custom

Score: 2.629842

Gitana / 3.2 / Guide / Guide / Access Policies / Samples / Editor of all Content in Spanish

Editor of all Content in Spanish This section describes features that are coming in 4.0 JSON { "title": "Editor of all Content in Spanish", "statements": [{ "action": "grant", "roles": ["editor"], "conditions": [{ "conditions": [{ "type": "locale", "config": { "locale": "es" } }] }] }] }

Score: 2.6062012

Gitana / 4.0 / Data Engine / Security / Access Policies / Samples / Editor of all Content in Spanish

Editor of all Content in Spanish This section describes features that are coming in 4.0 JSON { "title": "Editor of all Content in Spanish", "statements": [{ "action": "grant", "roles": ["editor"], "conditions": [{ "conditions": [{ "type": "locale", "config": { "locale": "es" } }] }] }] }

Score: 2.6062012