Found 717 results for "api datatypes node"

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

Score: 1.140961

Score: 1.140961

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

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

Gitana / 3.2 / Guide / Guide / User Interface / Locking

Locking Cloud CMS locking is a "data lock" approach which is a transactional lock is taken out when the write of multiple documents begins. This is a transactional lock in the sense that it blocks other write operations against those documents and fails entirely with rollback if any of the documents fail individually. We have transactional writes for multiple documents. We have a changeset-driven versioning model where each transaction writes onto it's own changeset. N number of documents may wr

Score: 1.1468997

Gitana / 4.0 / User Interface / User Interface / Locking

Locking Cloud CMS locking is a "data lock" approach which is a transactional lock is taken out when the write of multiple documents begins. This is a transactional lock in the sense that it blocks other write operations against those documents and fails entirely with rollback if any of the documents fail individually. We have transactional writes for multiple documents. We have a changeset-driven versioning model where each transaction writes onto it's own changeset. N number of documents may wr

Score: 1.1468997

CMS editor Locking

There are two levels of locking which usually come into play in a scenario like this. One is a "UI lock" which is taken out when a user begins editing something within the user interface. This lock is released when they finished editing (either by hitting save or canceling). The other lock is a "data lock" which is a transactional lock taken out when the write of multiple documents begins. This is a transactional lock in the sense that it blocks other write operations against those documents and

Score: 1.1468997

Gitana / 3.2 / Guide / Guide / API / Data Types / Association

Association Type {{#dataTypeArticle objectTypeId}}{{objectTypeId}}{{/dataTypeArticle}} Datastore Type {{#dataTypeArticle datastoreTypeId}}{{datastoreTypeId}}{{/dataTypeArticle}} Supports {{#article "security/authorities"}}authorities{{/article}}, {{#article "security/permissions"}}permissions{{/article}}, {{#article "transfer"}}transfer{{/article}} Associations, on the other hand, do not bear permissions. They are considered structural elements that provide several meanings for the content in a

Score: 1.1456125

Gitana / 4.0 / Data Engine / API / Data Types / Association

Association Type {{#dataTypeArticle objectTypeId}}{{objectTypeId}}{{/dataTypeArticle}} Datastore Type {{#dataTypeArticle datastoreTypeId}}{{datastoreTypeId}}{{/dataTypeArticle}} Supports {{#article "security/authorities"}}authorities{{/article}}, {{#article "security/permissions"}}permissions{{/article}}, {{#article "transfer"}}transfer{{/article}} Associations, on the other hand, do not bear permissions. They are considered structural elements that provide several meanings for the content in a

Score: 1.1456125

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

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

Gitana / 3.2 / Guide / Guide / Features / Renditionable

Renditionable QName: f:renditionable Marks that an instance or type is to have one or more renditions. Renditions are other nodes in the branch whose content is automatically generated and kept in sync as the source node is created, updated and deleted (or has its relevant attachment modified). Configuration

Property Type Default Read-Only Description

Gitana / 4.0 / Data Engine / Aspects / Renditionable

Renditionable QName: f:renditionable Marks that an instance or type is to have one or more renditions. Renditions are other nodes in the branch whose content is automatically generated and kept in sync as the source node is created, updated and deleted (or has its relevant attachment modified). Configuration

Property Type Default Read-Only Description

Gitana / 3.2 / Guide / Guide / Application Server / Installation / Standalone Installation

Standalone Installation The Cloud CMS Application Server is a Node.js / Express-based Application that can be downloaded and run with very little setup. All you need to do is provide your Cloud CMS account credentials and the Cloud CMS Application Server will connect and come online ready to serve your content. Node.js To get started, you will need Node.js. Please visit http://www.node.js.org to download Node.js for your platform. Git You will also need to be familiar with Git. The source for th

Score: 1.1404706

Gitana / 3.2 / Guide / Guide / Docker / Security Notices / CVE-2021-44228

CVE-2021-44228 Cloud CMS API Container Cloud CMS API docker containers prior to version 3.2.71 ship with a version of Log4j2 that contains the vulnerability identified on December 9, 2021 as CVE-2021-44228. The Cloud CMS API shipped with recent versions packages with Log4j2 version 2.10.1 and runs on JDK 11.0.2. While the Cloud CMS product does not use Log4j lookups and does not use JNDI, we still recommend taking mitigation steps for this vulnerability. For purposes of mitigating CVE-2021-44228

Score: 1.1404706

Gitana / 4.0 / Developers / Application Server / Installation / Standalone Installation

Standalone Installation The Cloud CMS Application Server is a Node.js / Express-based Application that can be downloaded and run with very little setup. All you need to do is provide your Cloud CMS account credentials and the Cloud CMS Application Server will connect and come online ready to serve your content. Node.js To get started, you will need Node.js. Please visit http://www.node.js.org to download Node.js for your platform. Git You will also need to be familiar with Git. The source for th

Score: 1.1404706

Gitana / 3.2 / Guide / Guide / Templates / Workflow Transition

Workflow Transition Name: workflowTransition Property Description id The ID of the route that was fired fromNodeId The ID of the node from which the transition starts toNodeId The ID of the node to which the transition ends Example: The workflow is transitioning from node {{ transition.fromNodeId }} to node {{transition.toNodeId}} via route {{transition.id}}.

Score: 1.1370599

Gitana / 3.2 / Guide / Guide / Scripting / Actions

Actions Properties There are no properties for this class. Methods execute Usage object execute() Arguments None Return Type Description object Examples Change the type of a Node In this example, we fire off the changeType action to change the type of a node to custom:thing. actions.execute("changeType", { "node": node, "type": "custom:thing" });

Score: 1.1370599

Actions

Actions Properties There are no properties for this class. Methods execute Usage object execute() Arguments None Return Type Description object Examples Change the type of a Node In this example, we fire off the changeType action to change the type of a node to custom:thing. actions.execute("changeType", { "node": node, "type": "custom:thing" });

Score: 1.1370599

Gitana / 4.0 / Data Engine / Templates / Workflow Transition

Workflow Transition Name: workflowTransition Property Description id The ID of the route that was fired fromNodeId The ID of the node from which the transition starts toNodeId The ID of the node to which the transition ends Example: The workflow is transitioning from node {{ transition.fromNodeId }} to node {{transition.toNodeId}} via route {{transition.id}}.

Score: 1.1370599

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

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

Gitana / 4.0 / Self Managed / Configuration / Overview

Configuration Antivirus Server API Server Encrypting Properties UI Server

Score: 1.1340182

Gitana / 3.2 / Guide / Guide / Docker / Configuration

Configuration Antivirus Server API Server Encrypting Properties Support UI Server

Score: 1.132262

Gitana / 3.2 / Guide / Guide / Application Server / Tags / @content

@content Fetches a single content instance by node id or path and makes it available to the template. Parameters parameter required description id the ID of the node path the path of the node as specifies the name of the variable (by default - content) Response The response is a JSON object representing the node. The exact properties contained here will be dependent on the properties of your content. Examples Example #1: Retrieve by Node ID {@content id="922e6b9c9f4b7564bab"}

Score: 1.1277306

Gitana / 4.0 / Developers / Application Server / Tags / @content

@content Fetches a single content instance by node id or path and makes it available to the template. Parameters parameter required description id the ID of the node path the path of the node as specifies the name of the variable (by default - content) Response The response is a JSON object representing the node. The exact properties contained here will be dependent on the properties of your content. Examples Example #1: Retrieve by Node ID {@content id="922e6b9c9f4b7564bab"}

Score: 1.1277306

Gitana / 3.2 / Guide / Guide / Actions / Send a Slack Message

Send a Slack Message ID: slackMessage Sends a Slack Message to a configured channel. For information on how to connect Slack and Cloud CMS, see Slack Integration. Configuration Property Type Required Default Description url text true The webhook URL provided by slack that will send messages to the configured channel. message text false Markdown message template of message that will be sent when action is fired. Required if template node is not provided. message text false Markdown message templa

Score: 1.1256317