Found 456 results for "content-behaviors policies property"
The search executed in 0.001621543 seconds. That's fast.
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: 19.188889
|
|
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: 19.188889
|
|
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: 16.020313
|
|
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: 15.975578
|
|
Gitana / 3.2 / Guide / Guide / Policies / Property PoliciesProperty 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: 11.75459
|
|
Gitana / 4.0 / Data Engine / Behaviors / Policies / Property PoliciesProperty 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: 11.75459
|
|
Gitana / 3.2 / Guide / Guide / Access Policies / Conditions / PropertyProperty 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.175659
|
|
Gitana / 4.0 / Data Engine / Security / Access Policies / Conditions / PropertyProperty 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.175659
|
|
Gitana / 3.2 / Guide / Guide / Policies / Node PoliciesNode 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.195309
|
|
Gitana / 4.0 / Data Engine / Behaviors / Policies / Node PoliciesNode 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.195309
|
|
Gitana / 3.2 / Guide / Guide / Policies / Association PoliciesAssociation 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.936328
|
|
Gitana / 4.0 / Data Engine / Behaviors / Policies / Association PoliciesAssociation 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.936328
|
|
Gitana / 3.2 / Guide / Guide / Policies / Attachment PoliciesAttachment 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.7476044
|
|
Gitana / 4.0 / Data Engine / Behaviors / Policies / Attachment PoliciesAttachment 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.7476044
|
|
Gitana / 3.2 / Guide / Guide / Policies / Data List PoliciesData 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.170826
|
|
Gitana / 4.0 / Data Engine / Behaviors / Policies / Data List PoliciesData 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.170826
|
|
Gitana / 3.2 / Guide / Guide / Conditions / Property ChangedProperty 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.0293694
|
|
Gitana / 4.0 / Data Engine / Behaviors / Conditions / Property ChangedProperty 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.0293694
|
|
Gitana / 3.2 / Guide / Guide / Actions / Set PropertySet 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.027074
|
|
Gitana / 4.0 / Data Engine / Behaviors / Actions / Set PropertySet 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.027074
|
|
Gitana / 3.2 / Guide / Guide / Conditions / Property EqualsProperty 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.0221806
|
|
Gitana / 4.0 / Data Engine / Behaviors / Conditions / Property EqualsProperty 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.0221806
|
|
Gitana / 3.2 / Guide / Guide / Actions / Remove PropertyRemove Property ID: removeProperty Removes a property from a node. { "title": "Remove Property", "properties": { "property": { "type": "string", "title": "Property Name" } } }
Score: 5.0188236
|
|
Gitana / 4.0 / Data Engine / Behaviors / Actions / Remove PropertyRemove Property ID: removeProperty Removes a property from a node. { "title": "Remove Property", "properties": { "property": { "type": "string", "title": "Property Name" } } }
Score: 5.0188236
|
|
Gitana / 3.2 / Guide / Guide / Conditions / Property ComparisonProperty Comparison The propertyComparison condition tests whether a given property matches a comparison to a given value. You can use this to test whether a value is greater than or less than another value (among other operations). JSON Schema { "title": "Property Comparison", "properties": { "property": { "type": "string", "title": "Property Name" }, "comparison": { "type": "string", "title": "Comparison",
Score: 5.0131373
|