Found 393 results for "docs fields number"

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

Gitana / 4.0 / Developers / Cookbooks / JavaScript (Legacy) Cookbook

JavaScript (Legacy) Cookbook Getting Started To get started with the JavaScript driver, please visit the Gitana JavaScript (Legacy) Driver Page. Connecting to Gitana To connect, supply your API Keys as the argument to the connect() method. Gitana.connect({ "clientKey": "{clientKey}", "clientSecret": "{clientSecret}", "username": "{username}", "password": "{password}", "baseURL": "https://api.cloudcms.com" }, function(err) { var platform = this; }); If a problem w

Score: 0.7444129

Gitana / 3.2 / Guide / Guide / Features / Indexable

Indexable QName: f:indexable Informs a node of how it should be indexed. Cloud CMS maintains multiple indexes including a search index, a database index and special indexes for things like path-based retrieval. By default, all n:node instances have the f:indexable feature applied to them. The default behavior is for search to be enabled and for search-indexes to be updated synchronously upon a write. Nodes that are indexed for search will take a little extra time on write (create or update) sinc

Score: 0.7317277

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

Gitana / 3.2 / Guide / Guide / Content Modeling / Definitions / Feature Definition

Feature Definition A Feature Definition is a cross-cutting concern or Aspect that you can apply arbitrarily to content instances or content types (to apply to all instances of a type). A Feature Definition is used to optionally describe additional schema that should be applied to a content or association type. Feature Definitions also endow content instances with special behaviors. Feature Definitions are defined in much the same way as Types or Associations. Each Feature has a QName and the JSO

Score: 0.7317277

Gitana / 4.0 / Data Engine / Aspects / Indexable

Indexable QName: f:indexable Informs a node of how it should be indexed. Cloud CMS maintains multiple indexes including a search index, a database index and special indexes for things like path-based retrieval. By default, all n:node instances have the f:indexable feature applied to them. The default behavior is for search to be enabled and for search-indexes to be updated synchronously upon a write. Nodes that are indexed for search will take a little extra time on write (create or update) sinc

Score: 0.7317277

Gitana / 4.0 / Data Engine / Content Models / Definitions / Feature Definition

Feature Definition A Feature Definition is a cross-cutting concern or Aspect that you can apply arbitrarily to content instances or content types (to apply to all instances of a type). A Feature Definition is used to optionally describe additional schema that should be applied to a content or association type. Feature Definitions also endow content instances with special behaviors. Feature Definitions are defined in much the same way as Types or Associations. Each Feature has a QName and the JSO

Score: 0.7317277

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

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

Gitana / 3.2 / Guide / Guide / API / Data Types / Authentication Grant

Authentication Grant 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}} Why would you want to use an Authentication Grant? Here are a few reasons: Authentication Grants provide a way for you to distribute user au

Score: 0.7157726

Gitana / 4.0 / Data Engine / API / Data Types / Authentication Grant

Authentication Grant 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}} Why would you want to use an Authentication Grant? Here are a few reasons: Authentication Grants provide a way for you to distribute user au

Score: 0.7157726

Gitana / 3.2 / Guide / Guide / Docker / Configuration / UI Server

UI Server The Cloud CMS UI Server is a Node.js application that provides the editorial experience for Cloud CMS. It communicates with the Cloud CMS API via HTTP/HTTPS API calls and is built to be very extensible. Developers and system integrators can extend the Cloud CMS UI through the deployment of UI modules. Environment File (.env) The Cloud CMS UI is primarily configured via a series of environment variables. These environment variables are detected by the Node.js application at startup and

Score: 0.70589566

Gitana / 4.0 / Self Managed / Configuration / API Server

API Server The Cloud CMS API Server is a Java application that launches inside of a Java Servlet Container. The Java application surfaces a REST API as well as backend services and DAOs to support connectivity to Mongo DB, Elastic Search and a slew of Amazon services including S3, SNS, SQS, Route 53, Cloud Front and more. Properties File Cloud CMS is primarily configured via a properties file that is auto-detected and loaded when the underlying Spring Framework starts up. This properties file is

Score: 0.67279947

Gitana / 3.2 / Guide / Guide / Authentication / Drivers

Drivers To connect to Cloud CMS, you need to establish two important pieces of information: The client that you are connecting as The user that you are signing on as The only way that a remote application can connect to your platform is if it can produce the correct credentials to identify itself as a client that you know about. As the platform administrator, you issue a client key/secret ahead of time. The application then needs to present these credentials to you and prove that it is who it sa

Score: 0.6595808

Gitana / 3.2 / Guide / Guide / Application Server / Services / Cache

Cache The Cache Service is responsible for providing an application server cache that all processes, whether local or distributed, have access to for non-transactional caching. Objects stored in the cache are eventually available to other members of the cluster (if there are any), no matter whether running on the same server or on other servers in the cluster. Modes The Cloud CMS Application Server can run in one of three modes: single node cluster multiple nodes (on a single process) sticky-clu

Score: 0.6595808

Gitana / 4.0 / Developers / Application Server / Services / Cache

Cache The Cache Service is responsible for providing an application server cache that all processes, whether local or distributed, have access to for non-transactional caching. Objects stored in the cache are eventually available to other members of the cluster (if there are any), no matter whether running on the same server or on other servers in the cluster. Modes The Cloud CMS Application Server can run in one of three modes: single node cluster multiple nodes (on a single process) sticky-clu

Score: 0.6595808

Gitana / 4.0 / Data Engine / Authentication / Drivers

Drivers To connect to Cloud CMS, you need to establish two important pieces of information: The client that you are connecting as The user that you are signing on as The only way that a remote application can connect to your platform is if it can produce the correct credentials to identify itself as a client that you know about. As the platform administrator, you issue a client key/secret ahead of time. The application then needs to present these credentials to you and prove that it is who it sa

Score: 0.6595808

Gitana / 4.0 / Data Engine / Security / Access Policies

Access 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: 0.6595808

Gitana / 3.2 / Guide / Guide / UI Developers Guide / Contexts

Contexts Cloud CMS uses a browser-side configuration service that evaluates "blocks" of configuration rules to determine the overall runtime configuration that drives every page render. Each block contains an evaluator and a snippet of configuration. If the evaluator evaluates to true, the snippet of configuration is included. It is merged into the overall runtime set and then used to make rendering decisions. Most of the Cloud CMS components that render on the screen, such as the left-hand navi

Score: 0.6398537

Gitana / 3.2 / Guide / Guide / API / Data Types / Client

Client 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}} Configuration Clients maintain a configuration that you can adjust or consult as you create, update and query for them. The following table presents you t

Score: 0.6398537

Gitana / 4.0 / Developers / User Interface Customization / Contexts

Contexts Cloud CMS uses a browser-side configuration service that evaluates "blocks" of configuration rules to determine the overall runtime configuration that drives every page render. Each block contains an evaluator and a snippet of configuration. If the evaluator evaluates to true, the snippet of configuration is included. It is merged into the overall runtime set and then used to make rendering decisions. Most of the Cloud CMS components that render on the screen, such as the left-hand navi

Score: 0.6398537

Gitana / 4.0 / Data Engine / API / Data Types / Client

Client 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}} Configuration Clients maintain a configuration that you can adjust or consult as you create, update and query for them. The following table presents you t

Score: 0.6398537

Gitana / 3.2 / Guide / Guide / Access Policies

Access Policies This section describes features that are coming in 4.0 Hello 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 polic

Score: 0.6285918

Gitana / 3.2 / Guide / Guide / Features / Knowledge Space

Knowledge Space QName: f:knowledge-space Used to indicate that a node should behave as a Knowledge Space. A Knowledge Space has zero or more knowledge properties. A knowledge property is a regular old property on your JSON object that is special in that its value may propagate to other nodes automatically. A Knowledge Space is holds the "master value" for those knowledge properties. When those properties change, their new values are pushed to any other nodes that are sharing the knowledge from t

Score: 0.6285918

Gitana / 3.2 / Guide / Guide / Search / Examples

Examples This page provides sample searches that you can review to get an idea of what is possible with search within Cloud CMS. Cloud CMS offers full integration to Elastic Search and, in doing so, it gives developers the ability to powerful queries using the Elastic Search DSL (as either JSON or a text-based query string format). Example: Full-text Search (using JS Driver) Suppose we want to search for all of the content nodes where the text eddie van halen appears. We can do so by using a ful

Score: 0.6285918

Gitana / 3.2 / Guide / Guide / Integrations / Amazon Web Services / Amazon SQS

Amazon SQS The Amazon Simple Queue Service (SQS) is a fast, reliable, scalable, fully managed message queuing service. Amazon SQS makes it simple and cost-effective to decouple the components of a cloud application. You can use Amazon SQS to transmit any volume of data, at any level of throughput, without losing messages or requiring other services to be always available. Cloud CMS Application Server The Cloud CMS Application Server is a middle-tier cluster that sits between your mobile/web appl

Score: 0.6285918