Found 181 results for "docs fields hidden"
The search executed in 0.001977196 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 / Hidden FieldHidden Field The hidden field. Properties Title Hidden Description Field for a hidden HTML input Field Type hidden Base Field Type control Schema Property Type Default Description enum array List of specific values for this property Options Property Type Default Description name string Field Name. sort function Defines an f(a,b) sort function for the array of enumerated values [{text, value}]. This is used to sort enum and optionLabels as well as results that come back from any data sources (for
Score: 10.643991
|
|
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
|
|
Gitana / 4.0 / Forms / API / ValidationValidation Alpaca computes the validity of fields in a rendered form and updates the DOM automatically to reflect things nicely for the end user. When validity checks run, the entire tree is traversed and computed. Each field being traversed will have it's outer DOM element updated with new classes. The alpaca-valid class is applied to fields that are in a valid state. The alpaca-invalid class is applied to fields that in an invalid state. In addition, a field may be in an invalid state and also
Score: 5.427122
|
|
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 / 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.7616324
|
|
Gitana / 4.0 / Forms / API / WizardsWizards Alpaca lets you arrange your form into simple multi-step wizards along with buttons for previous, next and submit using a simple configuration-driven approach. Wizards are essentially fields within a single form that are split across multiple DIVS, letting you orchestrate a single and non-conditional flow path as DIVs are hidden and shown in sequence. In addition, wizards optionally allow for configuration-driven options to assert the validation state of the set of shown fields before al
Score: 4.5266275
|
|
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
|
|
Precompile your Text fields with Markdown or HandlebarsOne of the new features in Cloud CMS 3.2.41 is the f:precompile feature. This feature tells Cloud CMS to automatically precompile one or more fields on your content items whenever the content is saved. With precompiling in place, you can now let your editors work in Markdown or use Handlebars tags in their content and then have that content automatically convert into HTML (or another output format) for use in your front-end applications. An Example Suppose, for example, that you defined an artcl
Score: 4.4545617
|
|
Gitana / 4.0 / Forms / API / DependenciesDependencies JSON Schema provides support for dependencies as a means for describing dependencies between fields. Using dependencies, you can establish that property2 should be supplied when property1 is supplied. Alpaca supports both JSON Schema v3 and v4 syntax for declaring dependencies. We recommend using JSON Schema v4 syntax. In JSON Schema v4, a single dependencies block within the container object stores key/values which consist of the ID of the property (key) and an array of property ID
Score: 3.9894145
|
|
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
|
|
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: 2.9811773
|
|
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.6824522
|
|
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.6824522
|
|
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.5565414
|
|
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.5565414
|