Found 176 results for "docs fields grid"
The search executed in 0.001060692 seconds. That's fast.
|
Gitana / 4.0 / Data Engine / Content Models / ConnectorsConnectors 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.423273
|
|
|
Gitana / 4.0 / Forms / Fields / Grid FieldGrid Field The grid field. Properties Title Grid Description Renders array items into a grid Field Type grid Base Field Type array Schema Property Type Default Description items object Schema for array items. maxItems number Maximum number of items. minItems number Minimum number of items. uniqueItems boolean Item values should be unique if true. Options Property Type Default Description animate boolean true Up and down transitions will be animated collapsed boolean Field set is initially collap
Score: 12.579278
|
|
|
Gitana / 4.0 / Data Engine / Content Models / Relator PropertiesRelator 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.340554
|
|
|
Gitana / 3.2 / Guide / Guide / FormsForms 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.602184
|
|
|
Gitana / 4.0 / Forms / CMS / OverviewForms 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.602184
|
|
|
Gitana / 3.2 / Guide / Guide / Forms / FieldsFields Attachment Picker CK Editor File Picker Node Picker Related Content Slug
Score: 8.364208
|
|
|
Gitana / 4.0 / Forms / CMS / FieldsFields Attachment Picker CK Editor File Picker Node Picker Related Content Slug
Score: 8.364208
|
|
|
Gitana / 3.2 / Guide / Guide / Content Modeling / ConnectorsConnectors 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.498906
|
|
|
Gitana / 4.0 / Forms / API / Custom FieldsCustom 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.146086
|
|
|
Gitana / 3.2 / Guide / Guide / UI Developers Guide / Contexts / documents-list-sort-fieldsdocuments-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.558008
|
|
|
Gitana / 4.0 / Developers / User Interface Customization / Contexts / documents-list-sort-fieldsdocuments-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.558008
|
|
|
Gitana / 3.2 / Guide / Guide / Content Modeling / Relator PropertiesRelator 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.540183
|
|
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: 5.083422
|
|
|
Gitana / 4.0 / Forms / Fields / OverviewFields Further Reading Address Field Any Field Array Field Checkbox Field Chooser Field CKEditor Field Color Field Color Picker Field Country Field Currency Field Date Field Date Time Field Editor Field Email Field File Field Grid Field Hidden Field Image Field Integer Field IPv4 Field JSON Field Lower Case Field Map Field Markdown Editor Field Number Field Object Field Option Tree Field Password Field Personal Name Field Phone Field Pick A Color Field Radio Field Search Field Select Field State
Score: 5.0510373
|
|
|
How to limit the fields that come back in a queryQuery 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.547242
|
|
|
Migrating Binary files to S3By default, on-premise installations of Cloud CMS are configured with a GridFS (`gridfs`) Binary Storage Provider. This allows Cloud CMS to read and write binary files (such as attachments) to GridFS. At some point, as your installation grows, you may want change this. Suppose you wanted to move your binary files into S3 and use S3 as a Binary Storage Provider for Cloud CMS. To do so, we recommend the following steps: 1. Make a backup of your Cloud CMS database. 2. Create an S3 bucket and IAM us
Score: 3.841316
|
|
|
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.4690406
|
|
|
Gitana / 4.0 / Forms / Fields / Date Time FieldDate Time Field The datetime field. The DateTime Field builds on the standard Date Field and leverages the Bootstrap DateTime plugin under the hood. You can learn more about this plugin on its GitHub page: https://github.com/Eonasdan/bootstrap-datetimepicker. For more information on date and time formatting strings, see the Moment.js documentation: http://momentjs.com/docs/. The default date time format is assumed to be MM/DD/YYYY HH:mm:ss. This is an American approach to the date with a 24-hour
Score: 3.2060769
|
|
|
How to Retrieve content by their document library pathYou 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: 3.0742397
|
|
|
Gitana / 4.0 / Forms / Fields / Date FieldDate Field The date field. The Date Field uses the Bootstrap Datetime picker under the hood. You can learn more about the picker at it's GitHub project page: https://github.com/Eonasdan/bootstrap-datetimepicker. For more information on date and time formatting strings, see the Moment.js documentation: http://momentjs.com/docs/. With this control, you can pass any of the bootstrap-datetimepicker options information through to the underlying control via the options.picker setting. Properties Title
Score: 3.0378735
|
|
|
Gitana / 3.2 / Guide / Guide / User Interface / Add-onsAdd-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.766007
|
|
|
Gitana / 4.0 / User Interface / Add-ons / OverviewAdd-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.766007
|
|
|
Gitana / 3.2 / Guide / Guide / Forms / Fields / CK EditorCK Editor ID: ckeditor The ckeditor field renders the popular CKEditor HTML control. This offers a fully-featured HTML editor on top of a string schema type. It is ideal for situations where you wish to provide your editorial team with the ability to edit HTML visually and offers a large range of plugins and behaviors that you can customize. For basic information of what is possible in terms of configuring this field type, please view the Alpaca Forms documentation for the CKEditor field. Config
Score: 2.580773
|
|
|
Gitana / 4.0 / Forms / CMS / Fields / CK EditorCK Editor ID: ckeditor The ckeditor field renders the popular CKEditor HTML control. This offers a fully-featured HTML editor on top of a string schema type. It is ideal for situations where you wish to provide your editorial team with the ability to edit HTML visually and offers a large range of plugins and behaviors that you can customize. For basic information of what is possible in terms of configuring this field type, please view the Alpaca Forms documentation for the CKEditor field. Config
Score: 2.580773
|
|
|
REST based access callsThe authentication mechanism in Cloud CMS is OAuth 2.0. While you can use any of the flows, the easiest one to begin with is "password". We've outlined a basic example here using Advanced REST Client to show our API-first platform in action. First, from your Cloud CMS platform home page, navigate to "Manage Platform" and select the "API Keys" section to list all available projects for remote access: If you have no keys for your project then create a new "Application" from "Manage Platform" and t
Score: 2.5276794
|