Found 247 results for "features relator"

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

Gitana / 4.0 / Data Engine / Content Models / Relator Properties

Relator Properties Cloud CMS provides support for properties that auto-manage their relationships between multiple nodes in the content graph. Whenever you intend to connect two nodes together, it is often convenient to model a property on one or both of the nodes involved in the relationship such that the properties maintain information locally on the endpoints about the relationship. Such properties are known as "relator properties". Consider a Store that sells Books. Books are written by Auth

Score: 30.073755

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

Gitana / 3.2 / Guide / Guide / Content Modeling / Relator Properties

Relator Properties Cloud CMS provides support for properties that auto-manage their relationships between multiple nodes in the content graph. Whenever you intend to connect two nodes together, it is often convenient to model a property on one or both of the nodes involved in the relationship such that the properties maintain information locally on the endpoints about the relationship. Such properties are known as "relator properties". Consider a Store that sells Books. Books are written by Auth

Score: 15.654343

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

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.515227

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.515227

Gitana / 3.2 / Guide / Guide / Features / Relator

Relator QName: f:relator This feature is applied internally to relator associations within the content graph that connect two nodes via a relator property. There is no need to apply this feature manually. For information on relator properties, please see relator properties. Configuration There are no configuration properties for this feature.

Score: 9.710794

Gitana / 4.0 / Data Engine / Aspects / Relator

Relator QName: f:relator This feature is applied internally to relator associations within the content graph that connect two nodes via a relator property. There is no need to apply this feature manually. For information on relator properties, please see relator properties. Configuration There are no configuration properties for this feature.

Score: 9.710794

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.993327

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.634085

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.634085

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.622959

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.622959

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.4117513

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.4117513

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.5112896

Gitana / 3.2 / Guide / Guide / Features / Related

Related QName: f:related This feature is applied internally to nodes that are on the other end of a relator association to indicate that the target node is related to the source node. This feature acts as a marker to tell Cloud CMS to consider the related nodes and the relator association at persistence time so the properties can be managed more efficiently in terms of mapping values from one end of the relationship to the other. There is no need to apply or work with this feature manually. For

Score: 2.971855

Gitana / 4.0 / Data Engine / Aspects / Related

Related QName: f:related This feature is applied internally to nodes that are on the other end of a relator association to indicate that the target node is related to the source node. This feature acts as a marker to tell Cloud CMS to consider the related nodes and the relator association at persistence time so the properties can be managed more efficiently in terms of mapping values from one end of the relationship to the other. There is no need to apply or work with this feature manually. For

Score: 2.971855

Pricing: Self Managed Options - Gitana

Pricing: Self Managed Options - 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, distribute and utilize your data operations, all integrated seamlessly and managed via single point of access. Automate Automate your content creation and approval flows while taking advantage of AI services

Score: 2.9628296

Pricing: Free Options - Gitana

Pricing: Free Options - 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, distribute and utilize your data operations, all integrated seamlessly and managed via single point of access. Automate Automate your content creation and approval flows while taking advantage of AI services to enha

Score: 2.9318097

Pricing: Hosted Options - Gitana

Pricing: Hosted Options - 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, distribute and utilize your data operations, all integrated seamlessly and managed via single point of access. Automate Automate your content creation and approval flows while taking advantage of AI services to en

Score: 2.6853862

Gitana / 3.2 / Guide / Guide / Actions / Sync Multiple Nodes

Sync Multiple Nodes ID: syncMultipleNodes Syncs a node to a target location. If the node does not exist in the target location, it is created. If it is already created, it is updated. If the node was deleted or we are explicitly told to sync a delete operation, the node will be deleted at the target location. Configuration Property Type Required Default Description repositoryId text true The ID of the repository of the source node. branchId text true The ID of the branch of the source node. node

Score: 2.6166635

Gitana / 3.2 / Guide / Guide / Actions / Sync Node

Sync Node ID: syncNode Syncs a node to a target location. If the node does not exist in the target location, it is created. If it is already created, it is updated. If the node was deleted or we are explicitly told to sync a delete operation, the node will be deleted at the target location. Configuration Property Type Required Default Description repositoryId text true The ID of the repository of the source node. branchId text true The ID of the branch of the source node. nodeId text true The ID

Score: 2.6166635

Gitana / 4.0 / Data Engine / Behaviors / Actions / Sync Multiple Nodes

Sync Multiple Nodes ID: syncMultipleNodes Syncs a node to a target location. If the node does not exist in the target location, it is created. If it is already created, it is updated. If the node was deleted or we are explicitly told to sync a delete operation, the node will be deleted at the target location. Configuration Property Type Required Default Description repositoryId text true The ID of the repository of the source node. branchId text true The ID of the branch of the source node. node

Score: 2.6166635

Gitana / 4.0 / Data Engine / Behaviors / Actions / Sync Node

Sync Node ID: syncNode Syncs a node to a target location. If the node does not exist in the target location, it is created. If it is already created, it is updated. If the node was deleted or we are explicitly told to sync a delete operation, the node will be deleted at the target location. Configuration Property Type Required Default Description repositoryId text true The ID of the repository of the source node. branchId text true The ID of the branch of the source node. nodeId text true The ID

Score: 2.6166635