Found 123 results for "access-policies conditions locale"
The search executed in 0.001758371 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.216343
|
![]() |
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.216343
|
![]() |
Gitana / 4.0 / Data Engine / API / PaginationPagination Pagination allows you to control the result set that comes back from Cloud CMS for any operations that produce a list of items. It is called pagination because it gives you a way to organize your record set into pages and then get those pages back, one at a time. Pagination gives you a way to adjust the result set before it is sent over the wire (and back to you) so that you can have smaller "paged" payloads. Pagination is useful because, most of the time, unless the result set is ver
Score: 14.516556
|
![]() |
Gitana / 3.2 / Guide / Guide / Access Policies / Conditions / LocaleLocale This section describes features that are coming in 4.0 The locale 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", "config": { "locale": "{value regex}" } } Samples This policy document grants the Consumer role to all content with l
Score: 12.8457155
|
![]() |
Gitana / 4.0 / Data Engine / Security / Access Policies / Conditions / LocaleLocale This section describes features that are coming in 4.0 The locale 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", "config": { "locale": "{value regex}" } } Samples This policy document grants the Consumer role to all content with l
Score: 12.8457155
|
![]() |
Gitana / 4.0 / Data Engine / Aspects / Auto TranslateAuto Translate QName: f:auto-translate This feature makes it so that any content that is saved is automatically translated into any desired target locales and stored as translations within the Cloud CMS I18N (Internationalization) framework. With this feature, your editorial users could, for example, make a change to a node and save it. The change could then be translated into Chinese, Spanish and German so that content can be retrieved from Cloud CMS in those locales. This all happens automatic
Score: 12.798612
|
![]() |
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: 11.77837
|
![]() |
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: 11.77837
|
![]() |
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.712661
|
![]() |
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.712661
|
![]() |
Gitana / 3.2 / Guide / Guide / API / PaginationPagination Pagination allows you to control the result set that comes back from Cloud CMS for any operations that produce a list of items. It is called pagination because it gives you a way to organize your record set into pages and then get those pages back, one at a time. Pagination gives you a way to adjust the result set before it is sent over the wire (and back to you) so that you can have smaller "paged" payloads. Pagination is useful because, most of the time, unless the result set is ver
Score: 6.7051964
|
![]() |
Gitana / 3.2 / Guide / Guide / Features / Auto TranslateAuto Translate QName: f:auto-translate This feature makes it so that any content that is saved is automatically translated into any desired target locales and stored as translations within the Cloud CMS I18N (Internationalization) framework. With this feature, your editorial users could, for example, make a change to a node and save it. The change could then be translated into Chinese, Spanish and German so that content can be retrieved from Cloud CMS in those locales. This all happens automatic
Score: 5.7680635
|
![]() |
Gitana / 3.2 / Guide / Guide / Access Policies / Samples / Editor of all Content in SpanishEditor 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: 5.3958282
|
![]() |
Gitana / 4.0 / Data Engine / Security / Access Policies / Samples / Editor of all Content in SpanishEditor 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: 5.3958282
|
![]() |
Gitana / 3.2 / Guide / Guide / Access Policies / Conditions / NotNot This section describes features that are coming in 4.0 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.896057
|
![]() |
Gitana / 4.0 / Data Engine / Security / Access Policies / Conditions / NotNot This section describes features that are coming in 4.0 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.896057
|
![]() |
Gitana / 3.2 / Guide / Guide / Access PoliciesAccess 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: 4.7501173
|
![]() |
Gitana / 4.0 / Data Engine / Security / Access PoliciesAccess 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: 4.7501173
|
![]() |
Gitana / 3.2 / Guide / Guide / User Interface / MultilingualMultilingual When applied to a node, this indicates that you wish to have the contents of this node support multilingual behavior and translated content. This node then serves as the "master node" for translation support. Master nodes have a:has_translation associations to translation nodes that hold copies of the content (JSON and any attachments) in the target locale Marking a node as f:multilingual does not automatically produce translations for you. However, once marked, the Cloud CMS user i
Score: 3.022251
|
![]() |
Gitana / 4.0 / User Interface / User Interface / MultilingualMultilingual When applied to a node, this indicates that you wish to have the contents of this node support multilingual behavior and translated content. This node then serves as the "master node" for translation support. Master nodes have a:has_translation associations to translation nodes that hold copies of the content (JSON and any attachments) in the target locale Marking a node as f:multilingual does not automatically produce translations for you. However, once marked, the Cloud CMS user i
Score: 3.022251
|
![]() |
Gitana / 4.0 / Forms / API / InternationalizationInternationalization Alpaca provides localized bundles for several locales including: Chinese (zh_CN) Czech (cs_CZ) Croatian (hr_HR) Dutch (nl_BE) Finnish (fi_FI) French (fr_FR) German (variant 1) (de_AT) German (variant 2) (de_DE) Greek (el_GR) Italian (it_IT) Japanese (ja_JP) Norwegian (nb_NO) Polish (pl_PL) Portugeuse (pt_BR) Spanish (es_ES) Swedish (sv_SE) These bundles allow Alpaca to render default messages (such as validation messages) in translated languages. In addition, Alpaca supports
Score: 2.9193184
|
![]() |
Gitana / 3.2 / Guide / Guide / Features / TranslationTranslation QName: f:translation Indicates this node contains the translated content of a "master node". The master node is the original node. This feature is applied to the node which contains the translation. Note: This node will be pointed to from the master node via an a:has_translation association. The a:has_translation association contains the locale and edition as properties. Configuration Property Type Default Read-Only Description master-node-id text The node ID of the node that holds t
Score: 2.9114096
|
![]() |
Gitana / 4.0 / Data Engine / Aspects / TranslationTranslation QName: f:translation Indicates this node contains the translated content of a "master node". The master node is the original node. This feature is applied to the node which contains the translation. Note: This node will be pointed to from the master node via an a:has_translation association. The a:has_translation association contains the locale and edition as properties. Configuration Property Type Default Read-Only Description master-node-id text The node ID of the node that holds t
Score: 2.9114096
|
![]() |
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.8992374
|
![]() |
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.8992374
|