Found 134 results for "access-policies conditions datastore"
The search executed in 0.001292943 seconds. That's fast.
![]() |
Gitana / 3.2 / Guide / Guide / ConditionsConditions 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 / ConditionsConditions 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 / RulesRules 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 / RulesRules 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 / Scripting / DataStoreDataStore Properties Name Type Description description string The Description of this document. id string The ID of this document. properties object The properties for this document. title string The Title of this document. Methods stringify Usage string stringify() Arguments None Return Type Description string Examples In this code sample, we take the JSON for the given document and produce a string representation of it. var text = document.stringify(true);
Score: 9.890575
|
![]() |
DataStoreDataStore Properties Name Type Description description string The Description of this document. id string The ID of this document. properties object The properties for this document. title string The Title of this document. Methods stringify Usage string stringify() Arguments None Return Type Description string Examples In this code sample, we take the JSON for the given document and produce a string representation of it. var text = document.stringify(true);
Score: 9.890575
|
![]() |
Gitana / 3.2 / Guide / Guide / Access Policies / ConditionsConditions 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.3366585
|
![]() |
Gitana / 4.0 / Data Engine / Security / Access Policies / ConditionsConditions 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.3366585
|
![]() |
Gitana / 3.2 / Guide / Guide / Access Policies / Conditions / Data StoreData 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: 4.9692383
|
![]() |
Gitana / 4.0 / Data Engine / Security / Access Policies / Conditions / Data StoreData 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: 4.9692383
|
![]() |
Gitana / 3.2 / Guide / Guide / SecuritySecurity 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: 2.8699844
|
![]() |
Gitana / 4.0 / Data Engine / Security / OverviewSecurity 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: 2.8699844
|
![]() |
Gitana / 3.2 / Guide / Guide / Access Policies / Conditions / AndAnd 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 / AndAnd 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 / OrOr 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 / OrOr 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 / PathPath 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 / PathPath 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 / OrOr 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 / OrOr 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 / FeatureFeature 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 / FeatureFeature 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 / AndAnd 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 / AndAnd 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-subcontextrule-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
|