Found 32 results for "access-policies conditions node-type-matches"

The search executed in 2.23459E-4 seconds. That's fast.

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 Node Has Attachment Or Property Changed Property Comparison

Score: 43.003628

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

Access Policies / Conditions

Conditions This section describes features that are coming in 3.3 Access Policy Conditions And Feature Matches ID Matches Locale Matches Not Or Path Matches Project Matches Property Matches Reference Matches Type Matches Type QName Matches

Score: 20.684927

Access Policies / Conditions / And

And This section describes features that are coming in 3.3 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: 6.5007935

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

Access Policies / Conditions / Or

Or This section describes features that are coming in 3.3 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: 6.3274875

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

Access Policies / Conditions / Feature Matches

Feature Matches This section describes features that are coming in 3.3 The feature-matches condition allows you to constrain a policy statement so that it applies to content nodes that have a particular feature. Configuration { "type": "feature-matches", "config": { "qname": "{qname}" } } Samples This policy grants the Consumer role to all content with feature f:thumbnailable: { "title": "My Sample Policy", "statements": [{ "action": "grant", "roles":

Score: 6.252774

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

Access Policies

Access Policies This section describes features that are coming in 3.3 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: 6.0526366

Access Policies / Samples / Editor of all Content in Spanish

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

Score: 5.900486

Access Policies / Samples / Manager of all Content in a Folder

Manager of all Content in a Folder This section describes features that are coming in 3.3 JSON { "title": "Manager of all Content in a Folder", "statements": [{ "action": "grant", "roles": ["manager"], "conditions": [{ "conditions": [{ "type": "path-matches", "config": { "path": "^/my/folder/.*" } }] }] }] }

Score: 5.893505

Access Policies / Conditions / Path Matches

Path Matches This section describes features that are coming in 3.3 The path-matches 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-matches", "config": { "path": "{value regex}" } } Samples This policy document grants the Consumer role to

Score: 5.8495264

Access Policies / Conditions / Reference Matches

Reference Matches This section describes features that are coming in 3.3 The reference-matches 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

Score: 5.5373907

Access Policies / Conditions / Locale Matches

Locale Matches This section describes features that are coming in 3.3 The node-locale-matches condition allows you to constrain a policy statement so that it applies to content nodes that have a matching locale. This condition supports regular expressions, allowing you to focus in on a single path, sub paths or arbitrary matching path structures. Configuration { "type": "locale-matches", "config": { "locale": "{value regex}" } } Samples This policy document grants the Consum

Score: 5.4846764

Access Policies / Conditions / Not

Not This section describes features that are coming in 3.3 The not condition lets you perform a logical NOT operation against a sub-condition. Configuration { "type": "not", "config": { "condition": { ... } } } Sample #1 This policy document allows a principal to edit any content that is not in Spanish { "title": "My Sample Policy", "statements": [{ "action": "grant", "roles": ["consumer"], "conditions": [{ "typ

Score: 4.9311867

Access Policies / Conditions / Type Matches

Type Matches This section describes features that are coming in 3.3 The type-matches condition allows you to constrain a policy statement so that it applies to entities of a specific type. This condition supports regular expressions, allowing you to focus in on a single ID or wildcard expressions within an ID. Configuration { "type": "type-matches", "config": { "type": "{type name}" } } Samples This policy document grants the Consumer role to all Projects. { "title": "My

Score: 4.76149

Access Policies / Conditions / ID Matches

ID Matches This section describes features that are coming in 3.3 The id-matches condition allows you to constrain a policy statement so that it applies to entities that match a given ID. This condition supports regular expressions, allowing you to focus in on a single ID or wildcard expressions within an ID. Configuration { "type": "id-matches", "config": { "id": "{value regex}" } } Samples This policy document grants the Consumer role to a specific piece of content with th

Score: 4.7253537

Access Policies / Conditions / Type QName Matches

Type QName Matches This section describes features that are coming in 3.3 The type-qname-matches condition allows you to constrain a policy statement so that it applies to content nodes that have a matching QName. This condition supports regular expressions, allowing you to focus in on a single path, sub paths or arbitrary matching path structures. Configuration { "type": "type-qname-matches", "config": { "qname": "{value regex}" } } Sample #1 This policy document allows a p

Score: 4.654702

Access Policies / Conditions / Property Matches

Property Matches This section describes features that are coming in 3.3 The property-matches condition allows you to constrain a policy statement so that it applies to entities where a specific property matches a value. This condition supports regular expressions, allowing you to focus in on a single ID or wildcard expressions within an ID. Configuration { "type": "property-matches", "config": { "property": "{property name}", "value": "{property value or regex}" } }

Score: 4.620163

Access Policies / Conditions / Project Matches

Project Matches This section describes features that are coming in 3.3 The project-matches condition allows you to constrain a policy statement so that it applies to entities that are contained with a project. The project can be matched using either its ID (_doc) or its title. This condition supports regular expressions, allowing you to focus in on a single value or wildcard expressions for matches. Configuration To match a project by ID: { "type": "project-matches", "config": {

Score: 4.552599

Projects

Projects In Cloud CMS, a Project is an isolated workspace in which your team can collaborate on the production and publication of content. You can create as many Projects as you wish. Within each Project, you can: Design your content model (types, features and associations) Build out editorial forms for easy-content entry Wire up "automagic" business logic consisting of Rules, Actions and Conditions to automatically do things like call out to web hooks, send emails or sanitize your data as edito

Score: 4.075777

Deployment / Deployment Strategy

Deployment Strategy A Deployment Strategy defines the conditions by which a Deployment Package should automatically be assembled and delivered to one or more Deployment Targets. A Deployment Strategy is a recipe that tells a listener within Cloud CMS how to identify nodes whose content has changed and should be deployed. It then describes what steps to take in terms of deploying the content. If you're using Cloud CMS Publishing, you will not need to set up a Deployment Strategy by hand. The Publ

Score: 3.872958

UI Developers Guide / Evaluators

Evaluators Evaluators are used to define conditions that determine whether a block of configuration should be included in the evaluated and merged configuration document. Evaluators work on different aspects of the runtime experience, including: what is being observed who is observed it what URL is being looked at what objects are known about at the time (i.e. observables) what permissions and authorities the current user has over things that are being observed There are many types of evaluators

Score: 3.7789342

Security

Security Cloud CMS lets you define enterprise-grade access control policies across all of your content to ensure and assert that the right content is being accessed by the right people at all times. To achieve this, Cloud CMS offers a security engine that incorporates multiple levels of access provisioning. These include: A Role-based, multi-level Authorization engine that asserts Permissions on every API, service and DAO method invocation. Fine-grained, object-level access control lists for spe

Score: 3.5829902