Found 139 results for "conditions merge"
The search executed in 0.001615892 seconds. That's fast.
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.752789
|
|
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.752789
|
|
Gitana / 3.2 / Guide / Guide / WorkspacesWorkspaces Cloud CMS offers Workspaces to provide editors with a way to create their own private and shared spaces where they can work on content without stepping on each other's toes. Workspaces are implemented using branches to provide all of those capabilities to the editorial team, including fork, merge, differencing, compare and push/pull between workspaces. Editorial users can create workspaces for any purpose they wish. Here are a few good uses of workspaces: A place to work on content th
Score: 2.7166524
|
|
Gitana / 4.0 / Data Engine / Branches / WorkspacesWorkspaces Cloud CMS offers Workspaces to provide editors with a way to create their own private and shared spaces where they can work on content without stepping on each other's toes. Workspaces are implemented using branches to provide all of those capabilities to the editorial team, including fork, merge, differencing, compare and push/pull between workspaces. Editorial users can create workspaces for any purpose they wish. Here are a few good uses of workspaces: A place to work on content th
Score: 2.7166524
|
|
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.708853
|
|
Gitana / 4.0 / Developers / User Interface Customization / 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.708853
|
|
Gitana / 4.0 / Data Engine / Security / Access PoliciesAccess 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.6788597
|
|
Gitana / 3.2 / Guide / Guide / Access PoliciesAccess Policies This section describes features that are coming in 4.0 Hello 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 polic
Score: 2.651387
|
|
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.6114774
|
|
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: 2.5889146
|
|
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: 2.5889146
|
|
Gitana / 3.2 / Guide / Guide / Access Policies / Samples / Manager of all Content in a FolderManager of all Content in a Folder This section describes features that are coming in 4.0 JSON { "title": "Manager of all Content in a Folder", "statements": [{ "action": "grant", "roles": ["manager"], "conditions": [{ "conditions": [{ "type": "path", "config": { "path": "^/my/folder/.*" } }] }] }] }
Score: 2.5800338
|
|
Gitana / 4.0 / Data Engine / Security / Access Policies / Samples / Manager of all Content in a FolderManager of all Content in a Folder This section describes features that are coming in 4.0 JSON { "title": "Manager of all Content in a Folder", "statements": [{ "action": "grant", "roles": ["manager"], "conditions": [{ "conditions": [{ "type": "path", "config": { "path": "^/my/folder/.*" } }] }] }] }
Score: 2.5800338
|
|
Enterprise Access Policies in Gitana 4.0 (Part 2)In this article, we'll continue our series on Access Policies within Gitana. We'll take a few interesting and more complex examples of how Access Policies may be used to guarantee compliance witih enterprise security requirements. In the previous article, we left off looking at how you can grant access to content using Access Policies that are defined at either a Platform or Project-level. Platform-scoped policies can be written once and applied across all of your Projects. In this way, you can
Score: 2.4966567
|
|
Gitana / 3.2 / Guide / Guide / Access Policies / Conditions / ReferenceReference This section describes features that are coming in 4.0 The reference 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}://{platformId}
Score: 2.4500113
|
|
Gitana / 4.0 / Data Engine / Security / Access Policies / Conditions / ReferenceReference This section describes features that are coming in 4.0 The reference 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}://{platformId}
Score: 2.4500113
|
|
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: 2.437865
|
|
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: 2.437865
|
|
Gitana / 3.2 / Guide / Guide / PoliciesPolicies Policies can be used to run custom code or fire off actions when an event, such as creating a content item or associating a content item into the content graph, occurs. Cloud CMS provides a wide array of policies that you can hook your custom logic into. By default, Cloud CMS provides sensible and useful content policy handlers to manage the lifecycle of you content. You can wire in new policy handlers. Policy handlers include scripts and rules. These policies will trigger behaviors whe
Score: 2.3813481
|
|
Gitana / 4.0 / Data Engine / Behaviors / PoliciesPolicies Policies can be used to run custom code or fire off actions when an event, such as creating a content item or associating a content item into the content graph, occurs. Cloud CMS provides a wide array of policies that you can hook your custom logic into. By default, Cloud CMS provides sensible and useful content policy handlers to manage the lifecycle of you content. You can wire in new policy handlers. Policy handlers include scripts and rules. These policies will trigger behaviors whe
Score: 2.3813481
|
|
Gitana / 3.2 / Guide / Guide / Features / Copied FromCopied From QName: f:copied-from Indicates that a specific revision of a node received its content from a copy operation. This feature can be used to identify points in the node history where a copy operation occurred from a different node (even a node from a different branch or repository entirely) into the current node. The Copied From feature tracks a single property called sourceRef which is a node reference to the node on the source branch that was the source for the copy operation. The Cop
Score: 2.3809972
|
|
Gitana / 4.0 / Data Engine / Aspects / Copied FromCopied From QName: f:copied-from Indicates that a specific revision of a node received its content from a copy operation. This feature can be used to identify points in the node history where a copy operation occurred from a different node (even a node from a different branch or repository entirely) into the current node. The Copied From feature tracks a single property called sourceRef which is a node reference to the node on the source branch that was the source for the copy operation. The Cop
Score: 2.3809972
|
|
Gitana / 4.0 / Data Engine / Behaviors / Overview_page Actions Conditions Policies Rules
Score: 2.3496084
|
|
Gitana / 3.2 / Guide / Guide / UI Developers Guide / Evaluators / context-conflictcontext-conflict If a Merge Conflict is currently being observed. { "evaluator": "context-conflict" }
Score: 2.336682
|
|
Gitana / 4.0 / Developers / User Interface Customization / Evaluators / context-conflictcontext-conflict If a Merge Conflict is currently being observed. { "evaluator": "context-conflict" }
Score: 2.336682
|