Found 131 results for "access-policies conditions changeset"

The search executed in 0.001377495 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 / Changeset

Changeset This section describes features that are coming in 4.0 The changeset condition allows you to constrain a policy statement so that it applies to nodes and/or associations that are written onto a matching changeset. The changeset can be matched using its ID (_doc). This condition supports regular expressions, allowing you to focus in on a single value or wildcard expressions for matches. Configuration To match a changeset by ID: { "type": "changeset", "config": { "id": "{

Score: 15.788656

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

Changeset This section describes features that are coming in 4.0 The changeset condition allows you to constrain a policy statement so that it applies to nodes and/or associations that are written onto a matching changeset. The changeset can be matched using its ID (_doc). This condition supports regular expressions, allowing you to focus in on a single value or wildcard expressions for matches. Configuration To match a changeset by ID: { "type": "changeset", "config": { "id": "{

Score: 15.788656

Gitana / 3.2 / Guide / Guide / Branches

Branches Cloud CMS stands apart from just about every other content management product on the market in that it offers a versioning model that is based around changesets. It is inspired by Git and Mercurial which are popular source-control products within the software development world. As such, Cloud CMS provides a changeset versioning system that captures every touch - every create, update or delete - that you make. Nothing is ever lost. Every data operation is fully transactional with every t

Score: 13.330507

Gitana / 4.0 / Data Engine / Branches / Overview

Branches Cloud CMS stands apart from just about every other content management product on the market in that it offers a versioning model that is based around changesets. It is inspired by Git and Mercurial which are popular source-control products within the software development world. As such, Cloud CMS provides a changeset versioning system that captures every touch - every create, update or delete - that you make. Nothing is ever lost. Every data operation is fully transactional with every t

Score: 13.330507

Gitana / 4.0 / User Interface / User Interface / Version Control

Version Control Cloud CMS provides a changeset versioning system that captures every touch - every create, update or delete - that you make. It is inspired by Git and Mercurial which are popular source-control products within the software development world. Nothing is ever lost. Every data operation is fully transactional with every transaction payload is fully captured into its own changesets. Transactions span multiple documents and full "units of work" are written into the changeset history w

Score: 13.251051

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

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

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 / 4.0 / Data Engine / API / System Metadata

System Metadata Cloud CMS automatically tracks system metadata for all of the objects that you create within it. System metadata consists of non-data values that describe things like who created an object and when it was modified. System Metadata This system metadata is tracked under the special _system key at the root of your objects. This system metadata is read-only in so far as it is tracked by Cloud CMS automatically. It is available for any object returned by any of the Cloud CMS APIs by s

Score: 9.9143715

Gitana / 3.2 / Guide / Guide / API / Data Types / Changeset

Changeset Type {{#dataTypeArticle objectTypeId}}{{objectTypeId}}{{/dataTypeArticle}} Datastore Type {{#dataTypeArticle datastoreTypeId}}{{datastoreTypeId}}{{/dataTypeArticle}} Supports {{#article "security/authorities"}}authorities{{/article}}, {{#article "security/permissions"}}permissions{{/article}}, {{#article "transfer"}}transfer{{/article}} In this sense, a branch can be thought of as a stack of changesets. There is a root changeset (where the branch starts) and a tip changeset (where the

Score: 9.711071

Gitana / 4.0 / Data Engine / API / Data Types / Changeset

Changeset Type {{#dataTypeArticle objectTypeId}}{{objectTypeId}}{{/dataTypeArticle}} Datastore Type {{#dataTypeArticle datastoreTypeId}}{{datastoreTypeId}}{{/dataTypeArticle}} Supports {{#article "security/authorities"}}authorities{{/article}}, {{#article "security/permissions"}}permissions{{/article}}, {{#article "transfer"}}transfer{{/article}} In this sense, a branch can be thought of as a stack of changesets. There is a root changeset (where the branch starts) and a tip changeset (where the

Score: 9.711071

Gitana / 3.2 / Guide / Guide / Access Policies / Conditions / Data Store

Data Store This section describes features that are coming in 4.0 The datastore condition allows you to constrain a policy statement so that it applies to datastores and/or objects within a datastore. The datastore can be matched using its Type, ID and/or a title. This condition supports regular expressions, allowing you to focus in on a single value or wildcard expressions for matches. Configuration To match a changeset by Type: { "type": "datastore", "config": { "typeId": "{val

Score: 8.77435

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

Data Store This section describes features that are coming in 4.0 The datastore condition allows you to constrain a policy statement so that it applies to datastores and/or objects within a datastore. The datastore can be matched using its Type, ID and/or a title. This condition supports regular expressions, allowing you to focus in on a single value or wildcard expressions for matches. Configuration To match a changeset by Type: { "type": "datastore", "config": { "typeId": "{val

Score: 8.77435

Gitana / 3.2 / Guide / Guide / User Interface / Version Control

Version Control Cloud CMS provides a changeset versioning system that captures every touch - every create, update or delete - that you make. It is inspired by Git and Mercurial which are popular source-control products within the software development world. Nothing is ever lost. Every data operation is fully transactional with every transaction payload is fully captured into its own changesets. Transactions span multiple documents and full "units of work" are written into the changeset history w

Score: 6.1971006

Gitana / 3.2 / Guide / Guide / Releases

Releases Releases allow you to set up collaborative workspaces where future sets of content can be worked on in real-time. Content can be created, edited and deleted in the workspace and then scheduled for publishing at a future date. Scheduled publishing allows your content to "go live" automatically - merging your content changes back into the mainline while triggering release actions for things like: Email Notifications CDN Synchronization Web Hook Calls Releases give your content team the ab

Score: 5.5897646

Gitana / 4.0 / Data Engine / Releases / Overview

Releases Releases allow you to set up collaborative workspaces where future sets of content can be worked on in real-time. Content can be created, edited and deleted in the workspace and then scheduled for publishing at a future date. Scheduled publishing allows your content to "go live" automatically - merging your content changes back into the mainline while triggering release actions for things like: Email Notifications CDN Synchronization Web Hook Calls Releases give your content team the ab

Score: 5.5897646

Gitana / 3.2 / Guide / Guide / API / System Metadata

System Metadata Cloud CMS automatically tracks system metadata for all of the objects that you create within it. System metadata consists of non-data values that describe things like who created an object and when it was modified. System Metadata This system metadata is tracked under the special _system key at the root of your objects. This system metadata is read-only in so far as it is tracked by Cloud CMS automatically. It is available for any object returned by any of the Cloud CMS APIs by s

Score: 4.703342

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

Introduction to Changeset Versioning

Cloud CMS provides you with content repositories that are powered by a “changeset” versioning model. This a powerful versioning model that you won’t find in most conventional CMS products. It’s one of the reasons why Cloud CMS is such a great platform for collaboration! Document-level Versioning A lot of legacy CMS products feature document-level versioning. With document-level versioning, when you make a change to a document, the system simply increments a version counter. You end up with multi

Score: 2.803257