Found 297 results for "docs fields state"
The search executed in 0.006191283 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 / State FieldState Field The state field. Properties Title State Description Provides a dropdown selector of states and/or territories in the United States, keyed by their two-character code Field Type state 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. Enabling this will allow the none option, and
Score: 9.214362
|
|
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
|
|
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: 5.080467
|
|
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 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 / 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: 3.8972569
|
|
Content Entry Forms ExampleCloud CMS lets you easily design and deploy forms for your web applications and content contributors. In this blog entry, we’ll walk through how you can do this within the Cloud CMS user interface. In this example, we’ll create a form that allows editors to create City Guide information. Note: in the Cloud CMS Trial there is a City Guide Content definition which can be used as a starting point or as a reference for this example. Add a Definition The Content Definitions can be found in the Cloud
Score: 3.5805893
|
|
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: 3.4981503
|
|
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: 3.4735708
|
|
Gitana / 4.0 / Forms / API / CallbacksCallbacks Alpaca provides several places where you can hook in callbacks. Events - events are raised when the user interacts with fields. You can register callbacks to handle these events, adjust field state or other operations. Observables - each field maintains an observable that you can subscribe to. Subscribing to an observable means that you're listening for changes to its value. You can also use observables to interrogate and find values of fields within namespaces. This lets you find valu
Score: 3.2188828
|
|
Gitana / 3.2 / Guide / Guide / Workflow / Sample Workflows / Custom FormCustom Form You may wish to introduce custom properties that flow along with your workflow. These properties are tracked as your workflow transitions from state to state. They may comprise things like due dates, notes, parameters for the workflow or anything else you'd like. You can use the form capability to define a form that lets users editing and modify these properties. Global Form The global form can be defined once and it will be used for all places within the workflow where a form can be
Score: 3.1882315
|
|
Gitana / 4.0 / Data Engine / Workflow / Sample Workflows / Custom FormCustom Form You may wish to introduce custom properties that flow along with your workflow. These properties are tracked as your workflow transitions from state to state. They may comprise things like due dates, notes, parameters for the workflow or anything else you'd like. You can use the form capability to define a form that lets users editing and modify these properties. Global Form The global form can be defined once and it will be used for all places within the workflow where a form can be
Score: 3.1882315
|
|
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: 3.142286
|
|
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 / 4.0 / Forms / API / ObservablesObservables Alpaca maintains observables that can be subscribed to by listeners that want to listen for changes to values in the form. An observable exists for every field and registration can be either programmatic or driven from configuration. In general, if you're sticking to straight JSON-schema, you won't find much use for observables. JSON schema is fairly fixed in terms of its interdependency of fields (see dependencies). Rather, observables are most useful when you really want to take fu
Score: 2.7980342
|