Found 138 results for "content-behaviors behaviors conditions"
The search executed in 0.001362147 seconds. That's fast.
Gitana / 4.0 / Data Engine / Content Models / BehaviorsBehaviors Cloud CMS lets you wire in behaviors behind your content models so that rules automatically execute when your content is touched. Content editors work with simple forms to create content that conforms to your defined content models. When that content is created, updated or deleted, it automatically triggers policies (or events) which you use to bind in custom behaviors. In this way, the developers can wire up behaviors and the editorial team never needs to know about it. Furthermore, b
Score: 22.50994
|
|
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.161142
|
|
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.161142
|
|
Gitana / 3.2 / Guide / Guide / Content Modeling / BehaviorsBehaviors Cloud CMS lets you wire in behaviors behind your content models so that rules automatically execute when your content is touched. Content editors work with simple forms to create content that conforms to your defined content models. When that content is created, updated or deleted, it automatically triggers policies (or events) which you use to bind in custom behaviors. In this way, the developers can wire up behaviors and the editorial team never needs to know about it. Furthermore, b
Score: 15.654238
|
|
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: 12.097052
|
|
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: 12.097052
|
|
Gitana / 3.2 / Guide / Guide / FeaturesFeatures Features are aspect-oriented, cross-cutting concerns that can be applied to nodes. Once applied, they may introduce new behaviors and metadata to your content objects. You can use features to describe cross-cutting or aspect-oriented concerns that can be plugged onto your content nodes at any time. Features may participate in the inheritance tree of content types or they may be injected anywhere and at any point. There are a number of out-of-the-box features provided by Cloud CMS, inclu
Score: 10.741803
|
|
Gitana / 4.0 / Data Engine / Aspects / OverviewFeatures Features are aspect-oriented, cross-cutting concerns that can be applied to nodes. Once applied, they may introduce new behaviors and metadata to your content objects. You can use features to describe cross-cutting or aspect-oriented concerns that can be plugged onto your content nodes at any time. Features may participate in the inheritance tree of content types or they may be injected anywhere and at any point. There are a number of out-of-the-box features provided by Cloud CMS, inclu
Score: 10.741803
|
|
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.343948
|
|
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.343948
|
|
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: 3.9307418
|
|
The Gitana Blog - Page 1 - GitanaThe Gitana Blog - Page 1 - Gitana Status Releases Registry Blog Cloud CMS Platform Content Management Create, Approve and Publish quality content to production on-time. Easy editorial and workflow tools let your best work reach your customers. Enterprise Data Engine Manage, collaborate, search and distribute your highly-structured data across branches, versions and workflow-driven lifecycle. Automate Automate your content creation and approval flows while taking advantage of AI services to enhan
Score: 3.110986
|
|
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.87038
|
|
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.87038
|
|
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.8613155
|
|
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.8613155
|
|
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.7980602
|
|
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.7980602
|
|
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.7949142
|
|
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.7949142
|
|
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.777344
|
|
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.777344
|
|
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.7745483
|
|
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.7745483
|
|
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.7301788
|