Gitana / 4.0 / Data Engine / Content Models / Connectors

Connectors You can create fields in your form which connect to your Cloud CMS content. This is done by configuring the Alpaca field's datasource to use CloudCMS via a connector. Example Suppose you have a type my:category and want to create a dropdown field to select category when creating another document. To do that, you would create a field in your form like this: { ... "category": { "type": "select", "dataSource": { "connector": true, "conf

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

Gitana / 3.2 / Guide / Guide / Security

Security Cloud CMS lets you define enterprise-grade access control policies across all of your content to ensure and assert that the right content is being accessed by the right people at all times. To achieve this, Cloud CMS offers a security engine that incorporates multiple levels of access provisioning. These include: A Role-based, multi-level Authorization engine that asserts Permissions on every API, service and DAO method invocation. Fine-grained, object-level access control lists for spe

Gitana / 4.0 / Data Engine / Bulk Import / CSV

CSV The Cloud CMS Bulk Import tool makes it easy to import content from a CSV (comma-separated value) text file into a Cloud CMS content repository. Suppose you have a CSV data set consisting of the 2014 World Cup Finals matches. It might look something like this: match_num,round/group,date,time,stadium,where,home,score,away,home_scorers,away_scorers 49,Round of 16,Jun 28,13:00,Estádio Mineirão,Belo Horizonte,Brazil,"3-2 pen. 1-1 (1-1, 1-1)",Chile,David Luiz 18', Alexis Sánchez 32' 50,Round of 1

Gitana / 4.0 / Data Engine / Security / Overview

Security Cloud CMS lets you define enterprise-grade access control policies across all of your content to ensure and assert that the right content is being accessed by the right people at all times. To achieve this, Cloud CMS offers a security engine that incorporates multiple levels of access provisioning. These include: A Role-based, multi-level Authorization engine that asserts Permissions on every API, service and DAO method invocation. Fine-grained, object-level access control lists for spe

Gitana / 3.2 / Guide / Guide / UI Developers Guide / Contexts / documents-list-sort-fields

documents-list-sort-fields [ { "evaluator": "document-is-folder", "condition": true, "config": { "documents-list-sort-fields": [ { "key": "title", "title": "Title", "field": "title" }, { "key": "description", "title": "Description", "field": "description" }, { "key": "createdOn", "title": "Created On", "field": "_system.created_on.ms" },

Gitana / 4.0 / Developers / User Interface Customization / Contexts / documents-list-sort-fields

documents-list-sort-fields [ { "evaluator": "document-is-folder", "condition": true, "config": { "documents-list-sort-fields": [ { "key": "title", "title": "Title", "field": "title" }, { "key": "description", "title": "Description", "field": "description" }, { "key": "createdOn", "title": "Created On", "field": "_system.created_on.ms" },

Gitana / 3.2 / Guide / Guide / Forms

Forms Cloud CMS automatically generates and displays mobile-friendly forms using the Alpaca Javascript / HTML5 forms engine. The Alpaca Forms Engine was created by Cloud CMS and is available as an open source project. In addition to the standard library of 40+ controls provided by Alpacajs, Cloud CMS provides support for several additional controls that run within the Cloud CMS user interface. Schemas and Forms Cloud CMS separates the concept of a schema from a form. A schema (or definition) des

Gitana / 4.0 / Forms / CMS / Overview

Forms Cloud CMS automatically generates and displays mobile-friendly forms using the Alpaca Javascript / HTML5 forms engine. The Alpaca Forms Engine was created by Cloud CMS and is available as an open source project. In addition to the standard library of 40+ controls provided by Alpacajs, Cloud CMS provides support for several additional controls that run within the Cloud CMS user interface. Schemas and Forms Cloud CMS separates the concept of a schema from a form. A schema (or definition) des

Gitana / 3.2 / Guide / Guide / Forms / Fields

Fields Attachment Picker CK Editor File Picker Node Picker Related Content Slug

Gitana / 4.0 / Forms / CMS / Fields

Fields Attachment Picker CK Editor File Picker Node Picker Related Content Slug

Gitana / 3.2 / Guide / Guide / Content Modeling / Connectors

Connectors You can create fields in your form which connect to your Cloud CMS content. This is done by configuring the Alpaca field's datasource to use CloudCMS via a connector. Example Suppose you have a type my:category and want to create a dropdown field to select category when creating another document. To do that, you would create a field in your form like this: { ... "category": { "type": "select", "dataSource": { "connector": true, "conf

Gitana / 4.0 / Forms / API / Custom Fields

Custom Fields Alpaca has a pretty inclusive field library that you can use straight away. Fields are simply referenced by their type within your Alpaca forms configuration. If you don't provide specific field types to use, Alpaca guesses at sensible defaults for you. You can also create your own fields. Alpaca fields are object-oriented (essentially) so that you can extend existing fields, override methods and modify behaviors. The result is less work and a complete extensibility layer so that y

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

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

list [ { "evaluator": "context-datalist-locale", "condition": true, "config": { "list": { "selected": { "actions": [ { "action": "delete_datalist_translations", "order": 7000 } ] } } } }, { "evaluator": "context-datalist-locale", "condition": false, "config": { "list": { "selected": { "actions": [ { "action": "remo

Gitana / 4.0 / Developers / User Interface Customization / Contexts / list

list [ { "evaluator": "context-datalist-locale", "condition": true, "config": { "list": { "selected": { "actions": [ { "action": "delete_datalist_translations", "order": 7000 } ] } } } }, { "evaluator": "context-datalist-locale", "condition": false, "config": { "list": { "selected": { "actions": [ { "action": "remo

Gitana / 3.2 / Guide / Guide / UI Developers Guide / Templates / List Items

List Items List Items exist in multiple places in CloudCMS UI. They consist of an icon on the left and some detailed descriptions on the right. Below is an example of some list items configured with the default template. You can customize the description on the right using Templates. The Default Template

{{title data}}

Gitana / 4.0 / Developers / User Interface Customization / Templates / List Items

List Items List Items exist in multiple places in CloudCMS UI. They consist of an icon on the left and some detailed descriptions on the right. Below is an example of some list items configured with the default template. You can customize the description on the right using Templates. The Default Template

{{title data}}

How to get a content definition JSON from the Cloud CMS API?

There are a couple of ways to do this. The first is simply use the node GET call and pass in the qname like this: GET /repositories/{repositoryId}/branches/{branchId}/nodes/{qname} http://api.cloudcms.com/docs#!/node/get_repositories_repositoryId_branches_branchId_nodes_nodeId This will give you back the JSON for the definition. Another way is to use this variation: GET /repositories/{repositoryId}/branches/{branchId}/definitions/{qname} http://api.cloudcms.com/docs#!/branch/get_repositories_rep

How to limit the fields that come back in a query

Query API calls like http://api.cloudcms.com/docs#!/node/post_repositories_repositoryId_branches_branchId_nodes_query support a parameter named _fields which defines an object specifying the node properties you want to include in the result set for matching nodes. For example in the following query I want the title, subTitle and slug fields returned: { "_type":"my:article", "_fields":{ "title":1, "subTitle":1, "slug":1 } } The result set would look something like the

Gitana / 3.2 / Guide / Guide / Policies / Data List Policies

Data List Policies Data List policies provide places where you can hook in behaviors that trigger when items within a data list are operated upon. When items are added to a data list, removed from a data list or updated, these policies trigger and may fire into your custom handlers. The following policies are available: Policy QName Description p:beforeAddListItem Raised before an item is added to a list p:afterAddListItem Raised after an item is added to a list p:beforeUpdateListItem Raised bef

Gitana / 4.0 / Data Engine / Behaviors / Policies / Data List Policies

Data List Policies Data List policies provide places where you can hook in behaviors that trigger when items within a data list are operated upon. When items are added to a data list, removed from a data list or updated, these policies trigger and may fire into your custom handlers. The following policies are available: Policy QName Description p:beforeAddListItem Raised before an item is added to a list p:afterAddListItem Raised after an item is added to a list p:beforeUpdateListItem Raised bef

Gitana / 3.2 / Guide / Guide / UI Developers Guide / Contexts / documents-list-buttons

documents-list-buttons [ { "evaluator": "document-is-file", "condition": true, "config": { "documents-list-buttons": [] } }, { "evaluator": "document-is-folder", "condition": true, "config": { "documents-list-buttons": [ { "key": "new", "title": "Create...", "iconClass": "fa fa-magic", "align": "left", "allowPermission": [ "read" ], "buttons": [ {

Gitana / 4.0 / Developers / User Interface Customization / Contexts / documents-list-buttons

documents-list-buttons [ { "evaluator": "document-is-file", "condition": true, "config": { "documents-list-buttons": [] } }, { "evaluator": "document-is-folder", "condition": true, "config": { "documents-list-buttons": [ { "key": "new", "title": "Create...", "iconClass": "fa fa-magic", "align": "left", "allowPermission": [ "read" ], "buttons": [ {

Gitana / 3.2 / Guide / Guide / Bulk Import / CSV

CSV The Cloud CMS Bulk Import tool makes it easy to import content from a CSV (comma-separated value) text file into a Cloud CMS content repository. Suppose you have a CSV data set consisting of the 2014 World Cup Finals matches. It might look something like this: match_num,round/group,date,time,stadium,where,home,score,away,home_scorers,away_scorers 49,Round of 16,Jun 28,13:00,Estádio Mineirão,Belo Horizonte,Brazil,"3-2 pen. 1-1 (1-1, 1-1)",Chile,David Luiz 18', Alexis Sánchez 32' 50,Round of 1