Found 284 results for "features behavior"

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

Gitana / 3.2 / Guide / Guide / Features

Features 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: 26.341175

Gitana / 4.0 / Data Engine / Aspects / Overview

Features 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: 20.335514

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

Gitana / 4.0 / Data Engine / Content Models / Behaviors

Behaviors 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: 13.334879

Gitana / 3.2 / Guide / Guide / Features / Behavior

Behavior QName: f:behavior This features indicates that a node provides the implementation of a behavior. This feature simply tags the node as a behavior implementation. The node must be a script or a rule. Configuration This feature does not require configuration. Behavior Example { "title": "My JavaScript file", "_features": { "f:behavior": { } } }

Score: 10.758148

Gitana / 4.0 / Data Engine / Aspects / Behavior

Behavior QName: f:behavior This features indicates that a node provides the implementation of a behavior. This feature simply tags the node as a behavior implementation. The node must be a script or a rule. Configuration This feature does not require configuration. Behavior Example { "title": "My JavaScript file", "_features": { "f:behavior": { } } }

Score: 10.758148

Gitana / 3.2 / Guide / Guide / Content Modeling

Content Modeling A content model consists of definitions which describe your project's content types, properties, graph associations, and the aspect-oriented features that Cloud CMS uses to ensure data consistency, integrity and validity when content is created, updated or deleted. In Cloud CMS, all content modeling is done using JSON and more specifically, JSON Schema. JSON Schema provides an elegant and well-adopted model for describing the types for content objects, properties and other neste

Score: 10.348318

Gitana / 4.0 / Data Engine / Content Models / Overview

Content Modeling A content model consists of definitions which describe your project's content types, properties, graph associations, and the aspect-oriented features that Cloud CMS uses to ensure data consistency, integrity and validity when content is created, updated or deleted. In Cloud CMS, all content modeling is done using JSON and more specifically, JSON Schema. JSON Schema provides an elegant and well-adopted model for describing the types for content objects, properties and other neste

Score: 10.348318

Gitana / 4.0 / Data Engine / Content Models / Default Paths

Default Paths Your content types define schemas that Cloud CMS uses to render intuitive forms for content entry. In addition, content types let you configure persistence paths so that JSON documents created using these forms are automatically saved in a directory structure that you intend. Paths support templated variables so that the path can be dynamic. It can depend on the values having been entered. For example, let's suppose I have the content type for an article, like this: { "title":

Score: 7.9690475

Gitana / 3.2 / Guide / Guide / Features / Behavior Binding

Behavior Binding QName: f:behavior-binding Marks an association as pointing to the implementation of a behavior for a policy on the source node. Valid target nodes include script nodes and rules. By applying this feature, you indicate that the target node script or rule should execute when the policy triggers. The target node (script or rule) must implement the f:behavior feature. For example, you might upload a JavaScript file that provides an implementation of a method to handle the afterNodeU

Score: 7.8889694

Gitana / 4.0 / Data Engine / Aspects / Behavior Binding

Behavior Binding QName: f:behavior-binding Marks an association as pointing to the implementation of a behavior for a policy on the source node. Valid target nodes include script nodes and rules. By applying this feature, you indicate that the target node script or rule should execute when the policy triggers. The target node (script or rule) must implement the f:behavior feature. For example, you might upload a JavaScript file that provides an implementation of a method to handle the afterNodeU

Score: 7.8889694

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

Gitana / 3.2 / Guide / Guide / Workflow / Workflow Handlers / Remove Features

Remove Features Type: removeFeatures This handler removes features from a node that is part of the workflow's payload. This can be used to remove one or more features from your content instances as they flow through your workflow. The config for this handler is as follows: { "features": [{ "qname": "" }] } Each of the features identified by qname will be removed from the documents attached to the workflow payload. Here is an example configuration which assumes tha

Score: 6.630544

Gitana / 4.0 / Data Engine / Workflow / Workflow Handlers / Remove Features

Remove Features Type: removeFeatures This handler removes features from a node that is part of the workflow's payload. This can be used to remove one or more features from your content instances as they flow through your workflow. The config for this handler is as follows: { "features": [{ "qname": "" }] } Each of the features identified by qname will be removed from the documents attached to the workflow payload. Here is an example configuration which assumes tha

Score: 6.630544

Gitana / 3.2 / Guide / Guide / Workflow / Workflow Handlers / Add Features

Add Features Type: addFeatures This handler adds features to a node that is part of the workflow's payload. This can be used to apply one or more features to your content instances as they flow through your workflow. The config for this handler is as follows: { "features": [{ "qname": "", "config": { ... optional configuration for the feature } }] } The config is an optional parameter. You can use this handler to add one or more features

Score: 6.6195745

Gitana / 4.0 / Data Engine / Workflow / Workflow Handlers / Add Features

Add Features Type: addFeatures This handler adds features to a node that is part of the workflow's payload. This can be used to apply one or more features to your content instances as they flow through your workflow. The config for this handler is as follows: { "features": [{ "qname": "", "config": { ... optional configuration for the feature } }] } The config is an optional parameter. You can use this handler to add one or more features

Score: 6.6195745

Gitana / 3.2 / Guide / Guide / Content Modeling / Behaviors

Behaviors 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: 5.893228

Gitana / 3.2 / Guide / Guide / Actions / Execute Script

Execute Script ID: executeScript Executes a script attachment of a node. The configuration for this action is described using JSON Schema like this: { "script": "if (typeof(node.data.count) === 'undefined') { node.data.count = 0; }; node.data.count++;" } Property Required Default Description script yes String containing the script scriptMimetype no application/javascript String methodName no The method name of the script args no The arguments for the method in the script

Score: 4.4806623

Gitana / 3.2 / Guide / Guide / Actions / Execute Script from a Node

Execute Script from a Node ID: executeScriptNode Executes a script attachment of a node. The configuration for this action is described using JSON Schema like this: { "scriptNodeId": "d904227f8628b15d4763" } Property Required Description scriptNodeId yes The node id of the script document scriptAttachmentId no The id of the attachment where the script locates methodName no The method name of the script args no The arguments for the method in the script

Score: 4.4806623

Gitana / 4.0 / Data Engine / Behaviors / Actions / Execute Script

Execute Script ID: executeScript Executes a script attachment of a node. The configuration for this action is described using JSON Schema like this: { "script": "if (typeof(node.data.count) === 'undefined') { node.data.count = 0; }; node.data.count++;" } Property Required Default Description script yes String containing the script scriptMimetype no application/javascript String methodName no The method name of the script args no The arguments for the method in the script

Score: 4.4806623

Gitana / 4.0 / Data Engine / Behaviors / Actions / Execute Script from a Node

Execute Script from a Node ID: executeScriptNode Executes a script attachment of a node. The configuration for this action is described using JSON Schema like this: { "scriptNodeId": "d904227f8628b15d4763" } Property Required Description scriptNodeId yes The node id of the script document scriptAttachmentId no The id of the attachment where the script locates methodName no The method name of the script args no The arguments for the method in the script

Score: 4.4806623

Gitana / 3.2 / Guide / Guide / UI Developers Guide / Contexts / content-model-features-list-item-actions

content-model-features-list-item-actions [ { "config": { "content-model-features-list-item-actions": [ { "key": "edit-document", "link": "/#/projects/{{project._doc}}/model/features/{{_qname}}/properties", "iconClass": "fa fa-pencil" }, { "key": "view-json", "link": "/#/projects/{{project._doc}}/model/features/{{_qname}}/json", "iconClass": "fa fa-code" }, { "key": "content-i

Score: 4.4082937

Gitana / 4.0 / Developers / User Interface Customization / Contexts / content-model-features-list-item-actions

content-model-features-list-item-actions [ { "config": { "content-model-features-list-item-actions": [ { "key": "edit-document", "link": "/#/projects/{{project._doc}}/model/features/{{_qname}}/properties", "iconClass": "fa fa-pencil" }, { "key": "view-json", "link": "/#/projects/{{project._doc}}/model/features/{{_qname}}/json", "iconClass": "fa fa-code" }, { "key": "content-i

Score: 4.4082937

Gitana / 3.2 / Guide / Guide / Content Modeling / Default Paths

Default Paths Your content types define schemas that Cloud CMS uses to render intuitive forms for content entry. In addition, content types let you configure persistence paths so that JSON documents created using these forms are automatically saved in a directory structure that you intend. Paths support templated variables so that the path can be dynamic. It can depend on the values having been entered. For example, let's suppose I have the content type for an article, like this: { "title":

Score: 3.509128

Gitana / 3.2 / Guide / Guide / API / Statistics

Statistics Cloud CMS automatically collects and aggregates node statistics for you as you connect nodes together in the content graph. Nodes are entities and associations are used to connect them together through a series of relationships. As nodes are connected together, both the source and target node may optionally adjust the statistics tracked on either end of the relationship. These statistics generally track aggregations, sums and totals of counters for properties on either end of the rela

Score: 2.9276662