Found 191 results for "docs fields country"
The search executed in 0.001804486 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.455013
|
|
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.35951
|
|
Gitana / 4.0 / Forms / Fields / Country FieldCountry Field The country field. Properties Title Country Description Provides a dropdown selector of countries keyed by their ISO3 code. The names of the countries are read from the I18N bundle for the current locale. Field Type country Base Field Type select Schema Property Type Default Description enum array List of field value options Options Property Type Default Description allowDefaultNoneSelected boolean This is used for required fields, where by default no "None" option is available. En
Score: 10.65097
|
|
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.625388
|
|
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.625388
|
|
Gitana / 3.2 / Guide / Guide / Forms / FieldsFields Attachment Picker CK Editor File Picker Node Picker Related Content Slug
Score: 8.390276
|
|
Gitana / 4.0 / Forms / CMS / FieldsFields Attachment Picker CK Editor File Picker Node Picker Related Content Slug
Score: 8.390276
|
|
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.5293703
|
|
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.17248
|
|
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.5827837
|
|
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.5827837
|
|
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.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
|
|
Gitana / 4.0 / Getting Started / Working with Content / FormsForms Cloud CMS provides a forms engine that instantly renders user interface forms on top of your content models. As your content models change, forms are automatically updated to provide an intuitive and easy-to-use editorial experience. Forms automatically calibrate for the most common web controls including text, numbers, text areas, drop downs, radio buttons, checkbox elements and nested fields (arrays, sub-objects). Cloud CMS integrates the powerful, open-source Alpaca.js Forms Engine so t
Score: 4.6230154
|
|
Gitana / 3.2 / Guide / Guide / Getting Started / Web FormsWeb Forms Cloud CMS provides an forms engine that instantly renders user interface forms on top of your content models. As your content models change, forms are automatically updated to provide an intuitive and easy-to-use editorial experience. Forms automatically calibrate for the most common web controls including text, numbers, text areas, drop downs, radio buttons, checkbox elements and nested fields (arrays, sub-objects). Cloud CMS integrates the powerful, open-source Alpaca.js Forms Engine
Score: 4.586872
|
|
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.4846106
|
|
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: 4.3159127
|
|
Gitana / 3.2 / Guide / Guide / Bulk Import / XML
XML The Cloud CMS Bulk Import tool makes it easy to import content from an XML file into a Cloud CMS content repository. XML is a common format for content that has been exported from an existing database or legacy CMS system. Suppose you have a XML data set containing information about soccer leagues around the world. It might look something like this:
|
|
Gitana / 4.0 / Data Engine / Bulk Import / XML
XML The Cloud CMS Bulk Import tool makes it easy to import content from an XML file into a Cloud CMS content repository. XML is a common format for content that has been exported from an existing database or legacy CMS system. Suppose you have a XML data set containing information about soccer leagues around the world. It might look something like this:
|
|
Gitana / 3.2 / Guide / Guide / API / Data Types / ApplicationApplication Configuration and custom properties. You can write your own properties onto this configuration document if you wish. You might use those properties to query and retrieve the directory at a later time. Some system properties are read-only and others are writable. You can adjust the writable properties to modify the behavior and characteristics of the directory. The following table presents you the system properties. Data Store Properties Data Store Type {{#dataTypeArticle datastoreTyp
Score: 3.4522078
|
|
Gitana / 3.2 / Guide / Guide / API / Data Types / DirectoryDirectory Configuration and custom properties. You can write your own properties onto this configuration document if you wish. You might use those properties to query and retrieve the directory at a later time. Some system properties are read-only and others are writable. You can adjust the writable properties to modify the behavior and characteristics of the directory. The following table presents you the system properties. Data Store Properties Data Store Type {{#dataTypeArticle datastoreTypeI
Score: 3.4522078
|
|
Gitana / 3.2 / Guide / Guide / API / Data Types / DomainDomain Configuration and custom properties. You can write your own properties onto this configuration document if you wish. You might use those properties to query and retrieve the directory at a later time. Some system properties are read-only and others are writable. You can adjust the writable properties to modify the behavior and characteristics of the directory. The following table presents you the system properties. Data Store Properties Data Store Type {{#dataTypeArticle datastoreTypeId}}
Score: 3.4522078
|
|
Gitana / 3.2 / Guide / Guide / API / Data Types / RegistrarRegistrar Configuration and custom properties. You can write your own properties onto this configuration document if you wish. You might use those properties to query and retrieve the directory at a later time. Some system properties are read-only and others are writable. You can adjust the writable properties to modify the behavior and characteristics of the directory. The following table presents you the system properties. Data Store Properties Data Store Type {{#dataTypeArticle datastoreTypeI
Score: 3.4522078
|
|
Gitana / 3.2 / Guide / Guide / API / Data Types / RepositoryRepository Configuration and custom properties. You can write your own properties onto this configuration document if you wish. You might use those properties to query and retrieve the directory at a later time. Some system properties are read-only and others are writable. You can adjust the writable properties to modify the behavior and characteristics of the directory. The following table presents you the system properties. Data Store Properties Data Store Type {{#dataTypeArticle datastoreType
Score: 3.4522078
|
|
Gitana / 3.2 / Guide / Guide / API / Data Types / VaultVault Configuration and custom properties. You can write your own properties onto this configuration document if you wish. You might use those properties to query and retrieve the directory at a later time. Some system properties are read-only and others are writable. You can adjust the writable properties to modify the behavior and characteristics of the directory. The following table presents you the system properties. Data Store Properties Data Store Type {{#dataTypeArticle datastoreTypeId}}{
Score: 3.4522078
|