Found 179 results for "docs fields lowercase"

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

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

Score: 16.455013

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

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

Score: 8.625388

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

Score: 8.625388

Gitana / 3.2 / Guide / Guide / Forms / Fields

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

Score: 8.390276

Gitana / 4.0 / Forms / CMS / Fields

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

Score: 8.390276

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

Score: 7.5293703

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

Score: 7.17248

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" },

Score: 5.5827837

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" },

Score: 5.5827837

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

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

Score: 4.9910946

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

Score: 4.4846106

Gitana / 4.0 / Forms / Fields / Option Tree Field

Option Tree Field The optiontree field. Properties Title Option Tree Description Text field for lowercase text Field Type optiontree Base Field Type text Schema Property Type Default Description allowOptionalEmpty Allows this non-required field to validate when the value is empty autocomplete string Allows you to specify the autocomplete attribute for the underlying input control whether or not field should have autocomplete enabled. data object Allows you to specify a key/value map of data attr

Score: 3.844943

Gitana / 4.0 / Forms / Fields / Lower Case Field

Lower Case Field The lowercase field. Properties Title Lower Case Description Text field for lowercase text Field Type lowercase Base Field Type text Schema Property Type Default Description allowOptionalEmpty Allows this non-required field to validate when the value is empty autocomplete string Allows you to specify the autocomplete attribute for the underlying input control whether or not field should have autocomplete enabled. data object Allows you to specify a key/value map of data attribut

Score: 3.585723

Is there a programmatic way to add more content to workflows?

There is a programmatic way to add more content to workflows once they're in-flight. However, once the workflow is in-flight, the workflow process instance isn't the correct place to add things. Instead, you'd want to add new content to a workflow task. Essentially, a workflow is made up of a series of tasks. When the workflow transitions from one node to another in the workflow model, it instantiates a new task and the task holds the state (and references to documents) for that phase of the wor

Score: 3.3650582

Gitana / 4.0 / Forms / Fields / Text Field

Text Field The text field is used to represent text within a form. Properties Title Text Description Renders object items into a table row Field Type text Base Field Type control Schema Property Type Default Description allowOptionalEmpty Allows this non-required field to validate when the value is empty autocomplete string Allows you to specify the autocomplete attribute for the underlying input control whether or not field should have autocomplete enabled. data object Allows you to specify a k

Score: 3.0546777

How to Retrieve content by their document library path

You can retrieve content by their document library path using the CMS API using the Node API. For example, you can paginate through the children of a node using this call: http://api.cloudcms.com/docs#!/node/get_repositories_repositoryId_branches_branchId_nodes_nodeId_children GET /repositories/{repositoryId}/branches/{branchId}/nodes/{nodeId}/children?path={path} In this case, you would set "nodeId" to the value "root" to indicate the root node. And then use "path" to describe the offset. If yo

Score: 2.9811773

Gitana / 3.2 / Guide / Guide / Search

Search Any content you put into Cloud CMS is automatically indexed for full-text and structured search. This lets your editorial teams instantly search for content and find the things they're looking for. Under the hood, Cloud CMS uses Elastic Search and makes available to your editorial users and developers the full syntax of the Elastic Search Query DSL. This allows you to execute simple searches as well as more complex queries that take into account term and phrase matching, nested operations

Score: 2.8534064

Gitana / 4.0 / Data Engine / Discovery / Search

Search Any content you put into Cloud CMS is automatically indexed for full-text and structured search. This lets your editorial teams instantly search for content and find the things they're looking for. Under the hood, Cloud CMS uses Elastic Search and makes available to your editorial users and developers the full syntax of the Elastic Search Query DSL. This allows you to execute simple searches as well as more complex queries that take into account term and phrase matching, nested operations

Score: 2.8534064

Gitana / 3.2 / Guide / Guide / API / Pagination

Pagination Pagination allows you to control the result set that comes back from Cloud CMS for any operations that produce a list of items. It is called pagination because it gives you a way to organize your record set into pages and then get those pages back, one at a time. Pagination gives you a way to adjust the result set before it is sent over the wire (and back to you) so that you can have smaller "paged" payloads. Pagination is useful because, most of the time, unless the result set is ver

Score: 2.7214642

Gitana / 4.0 / Data Engine / API / Pagination

Pagination Pagination allows you to control the result set that comes back from Cloud CMS for any operations that produce a list of items. It is called pagination because it gives you a way to organize your record set into pages and then get those pages back, one at a time. Pagination gives you a way to adjust the result set before it is sent over the wire (and back to you) so that you can have smaller "paged" payloads. Pagination is useful because, most of the time, unless the result set is ver

Score: 2.7214642

Gitana / 3.2 / Guide / Guide / User Interface / Add-ons

Add-ons Cloud CMS Add-Ons let you enhance your editorial user interface with new features and capabilities that integrate to popular third-party services like YouTube, Vimeo and Google Docs. Add-ons provision your editorial environment with things like: new form field types that integrate to third-party services new user interface pages for browsing and working with media from third-party services new actions or rules to enhance your repository's business logic new content types, associations an

Score: 2.6824522

Gitana / 4.0 / User Interface / Add-ons / Overview

Add-ons Cloud CMS Add-Ons let you enhance your editorial user interface with new features and capabilities that integrate to popular third-party services like YouTube, Vimeo and Google Docs. Add-ons provision your editorial environment with things like: new form field types that integrate to third-party services new user interface pages for browsing and working with media from third-party services new actions or rules to enhance your repository's business logic new content types, associations an

Score: 2.6824522

Gitana / 3.2 / Guide / Guide / Search / Query String Reference

Query String Reference Cloud CMS lets you search for your content using either a text-based query string or a JSON block. These two methods are fairly equivalent for most typical operations. They provide two ways to express a search operation that will execute within Elastic Search. They are expressions of the Elastic Search DSL. This portion of the documentation goes into some of things you can do with the former, textual representation of an Elastic Search query string. In Cloud CMS, you can t

Score: 2.6159666