Found 454 results for "policies property"

The search executed in 0.00151438 seconds. That's fast.

Gitana / 3.2 / Guide / Guide / Policies

Policies 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: 24.785965

Gitana / 4.0 / Data Engine / Behaviors / Policies

Policies 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: 24.785965

Gitana / 3.2 / Guide / Guide / Policies / Property Policies

Property Policies Property policies provide places where you can hook in behaviors that trigger when a property is created, updated or deleted. They allow you to get very granular about when you custom code is invoked - such as only when a specific property in your content is affected. The following property policies are available: Policy QName Description p:beforeCreateProperty Raised before a property on a node is created p:afterCreateProperty Raised after a property on a node is created p:bef

Score: 17.890541

Gitana / 4.0 / Data Engine / Behaviors / Policies / Property Policies

Property Policies Property policies provide places where you can hook in behaviors that trigger when a property is created, updated or deleted. They allow you to get very granular about when you custom code is invoked - such as only when a specific property in your content is affected. The following property policies are available: Policy QName Description p:beforeCreateProperty Raised before a property on a node is created p:afterCreateProperty Raised after a property on a node is created p:bef

Score: 17.890541

Gitana / 4.0 / Data Engine / Security / Access Policies

Access 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: 16.013803

Gitana / 3.2 / Guide / Guide / Access Policies

Access 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: 15.969088

Gitana / 3.2 / Guide / Guide / Access Policies / Conditions / Property

Property This section describes features that are coming in 4.0 The property 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", "config": { "property": "{property name}", "value": "{property value or regex}" } } Samples This policy docu

Score: 11.164478

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

Property This section describes features that are coming in 4.0 The property 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", "config": { "property": "{property name}", "value": "{property value or regex}" } } Samples This policy docu

Score: 11.164478

Gitana / 3.2 / Guide / Guide / Policies / Node Policies

Node Policies Node policies provide places where you can hook in behaviors that trigger when nodes are created, updated or deleted within the graph. Nodes may either be entities or associations. This provides an ideal way to plug in your custom behaviors for any definition or content instance within your content graph. The following policies are available: Policy QName Description p:beforeCreateNode Raised before a piece of content is created p:afterCreateNode Raised after a piece of content has

Score: 7.1888957

Gitana / 4.0 / Data Engine / Behaviors / Policies / Node Policies

Node Policies Node policies provide places where you can hook in behaviors that trigger when nodes are created, updated or deleted within the graph. Nodes may either be entities or associations. This provides an ideal way to plug in your custom behaviors for any definition or content instance within your content graph. The following policies are available: Policy QName Description p:beforeCreateNode Raised before a piece of content is created p:afterCreateNode Raised after a piece of content has

Score: 7.1888957

Gitana / 3.2 / Guide / Guide / Policies / Association Policies

Association Policies Association policies provide places where you can hook in behaviors that trigger when associations are created or removed between two nodes in the Cloud CMS content graph. When two nodes are connected together via an association or an association is broken, these policies trigger and may fire into your custom handlers. The following policies are available: Policy QName Description p:beforeAssociate Raised before an association is created between two nodes p:afterAssociate Ra

Score: 6.9296904

Gitana / 4.0 / Data Engine / Behaviors / Policies / Association Policies

Association Policies Association policies provide places where you can hook in behaviors that trigger when associations are created or removed between two nodes in the Cloud CMS content graph. When two nodes are connected together via an association or an association is broken, these policies trigger and may fire into your custom handlers. The following policies are available: Policy QName Description p:beforeAssociate Raised before an association is created between two nodes p:afterAssociate Ra

Score: 6.9296904

Gitana / 3.2 / Guide / Guide / Policies / Attachment Policies

Attachment Policies Attachment policies provide places where you can hook in behaviors that trigger when attachments are read, created, updated or deleted against a node. Unlike other policy handlers, these will only fire at the instance when an attachment is created, updated, or deleted, and will not fire upon a branch merge or release. When configuring your attachments, you can specify an attachment ID you wish to fire your policy. For example, suppose you are configuring a webhook rule that y

Score: 6.7410154

Gitana / 4.0 / Data Engine / Behaviors / Policies / Attachment Policies

Attachment Policies Attachment policies provide places where you can hook in behaviors that trigger when attachments are read, created, updated or deleted against a node. Unlike other policy handlers, these will only fire at the instance when an attachment is created, updated, or deleted, and will not fire upon a branch merge or release. When configuring your attachments, you can specify an attachment ID you wish to fire your policy. For example, suppose you are configuring a webhook rule that y

Score: 6.7410154

Gitana / 3.2 / Guide / Guide / Policies / Data List Policies

Data List Policies Data List policies provide places where you can hook in behaviors that trigger when items within a data list are operated upon. When items are added to a data list, removed from a data list or updated, these policies trigger and may fire into your custom handlers. The following policies are available: Policy QName Description p:beforeAddListItem Raised before an item is added to a list p:afterAddListItem Raised after an item is added to a list p:beforeUpdateListItem Raised bef

Score: 6.164671

Gitana / 4.0 / Data Engine / Behaviors / Policies / Data List Policies

Data List Policies Data List policies provide places where you can hook in behaviors that trigger when items within a data list are operated upon. When items are added to a data list, removed from a data list or updated, these policies trigger and may fire into your custom handlers. The following policies are available: Policy QName Description p:beforeAddListItem Raised before an item is added to a list p:afterAddListItem Raised after an item is added to a list p:beforeUpdateListItem Raised bef

Score: 6.164671

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

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

Gitana / 3.2 / Guide / Guide / Content Modeling / Scripts

Scripts Scripts are content nodes with a default attachment of type application/javascript. As with all behaviors, script 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 association. Script Interfaces If you elect to write scripts to implement custom behaviors, the following signatures can be used inside of your JavaScript: {{#article "policies/association"}}Association Policies{{/

Score: 6.10769

Gitana / 4.0 / Data Engine / Content Models / Scripts

Scripts Scripts are content nodes with a default attachment of type application/javascript. As with all behaviors, script 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 association. Script Interfaces If you elect to write scripts to implement custom behaviors, the following signatures can be used inside of your JavaScript: {{#article "policies/association"}}Association Policies{{/

Score: 6.10769

Gitana / 3.2 / Guide / Guide / Conditions / Property Changed

Property Changed The propertyChanged condition tests whether a property on a node changed its value in a prescribed way. You can use this condition to test if a node property changed at all, from a specific value or to a specific value (or both). JSON Schema { "title": "Property Changed", "properties": { "property": { "type": "string", "title": "Property Name", "required": true }, "oldValue": { "type": "string",

Score: 5.027466

Gitana / 4.0 / Data Engine / Behaviors / Conditions / Property Changed

Property Changed The propertyChanged condition tests whether a property on a node changed its value in a prescribed way. You can use this condition to test if a node property changed at all, from a specific value or to a specific value (or both). JSON Schema { "title": "Property Changed", "properties": { "property": { "type": "string", "title": "Property Name", "required": true }, "oldValue": { "type": "string",

Score: 5.027466

Gitana / 3.2 / Guide / Guide / Actions / Set Property

Set Property ID: setProperty Sets a property on a node. { "title": "Set Property", "properties": { "property": { "type": "string", "title": "Property Name" }, "value": { "type": "any", "title": "Property Value" } } }

Score: 5.025202

Gitana / 4.0 / Data Engine / Behaviors / Actions / Set Property

Set Property ID: setProperty Sets a property on a node. { "title": "Set Property", "properties": { "property": { "type": "string", "title": "Property Name" }, "value": { "type": "any", "title": "Property Value" } } }

Score: 5.025202

Gitana / 3.2 / Guide / Guide / Conditions / Property Equals

Property Equals The propertyEquals condition tests whether a node property is equal to a given value. JSON Schema { "title": "Property Equals", "properties": { "property": { "type": "string", "title": "Property Name" }, "value": { "type": "string", "title": "Value" } } } Example #1 Suppose you wanted to test whether a node has a property called published which was set to true. You could set up the condit

Score: 5.020291