Found 243 results for "forms fields slug"
The search executed in 0.011977319 seconds. That's fast.
![]() |
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.7198684
|
![]() |
Gitana / 4.0 / Forms / API / OverviewAPI Further Reading Callbacks Conditional Dependencies Connectors Cookbook Custom Fields Data Sources Dependencies Events Forms Functions Internationalization Layouts Lookups Observables Ordering Recursive References References Serialization Templates Usage Validation Views Wizards
Score: 3.6848867
|
![]() |
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: 3.502751
|
![]() |
Gitana / 3.2 / Guide / Guide / Content Modeling / Content Model Builder / Edit An Existing Content TypeEdit An Existing Content Type Select Content Model Builder in the left Nav, and you will be able to see a list of existing Content Types. Click into one to edit it in the Content Model Builder. Select A Form If the content type has more than one forms, select the one you hope to edit: Then the builder will render with the settings in the selected form. Change Field Order Dragging a field and dropping it on top of another field allows you to move it in front of the other field. In the above image
Score: 3.4811301
|
![]() |
Gitana / 4.0 / Data Engine / Content Models / Content Model Builder / Edit An Existing Content TypeEdit An Existing Content Type Select Content Model Builder in the left Nav, and you will be able to see a list of existing Content Types. Click into one to edit it in the Content Model Builder. Select A Form If the content type has more than one forms, select the one you hope to edit: Then the builder will render with the settings in the selected form. Change Field Order Dragging a field and dropping it on top of another field allows you to move it in front of the other field. In the above image
Score: 3.4811301
|
![]() |
Gitana / 4.0 / Forms / API / LayoutsLayouts Alpaca features both automatic and layout-driven mechanisms for placing your fields onto a page. The automatic mechanism simply walks through your fields in the order they are expressed in schema and places them one by one in a stacked order. The layout-driven mechanism allows you to provide a layout template that finely describes where your fields should be placed using DOM-driven injection. To use a layout, you simply need to provide a view that has a layout block. The layout block def
Score: 3.2979324
|
![]() |
Gitana / 4.0 / Forms / API / LookupsLookups Alpaca provides abstractions for forms, fields, connectors and other types so as to provide a consistent and easy-to-use interface. This interface lets you find other objects in the JSON structure and plug in function handlers that make decisions by drawing from values of other fields. Every field that renders fundamentally receives an ID. The ID is a dynamically assigned value of no particular significance other than that it is unique. Typically, it is something like alpaca123. Each fie
Score: 2.959863
|
![]() |
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: 2.9015985
|
![]() |
Definitions for Date formatOur definitions are based on JSON schema and, as such, the default is to use strings for dates. The date controls in our forms engine let you customize the format string so that you can store ISO 8601 or other formats (perhaps simplified formats) as per your preference. The advantage here is simplicity with these controls and compatibility with JSON schema. The disadvantage is that MongoDB provides a lot of very powerful capabilities for range query and sorting that do not play as nicely with th
Score: 2.882856
|
![]() |
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: 2.6348233
|
![]() |
Gitana / 4.0 / Forms / API / TemplatesTemplates Alpaca includes an advanced templating system that is driven by views. You can create your own views and templates at compile time (when you actually build Alpaca) or you can override them on the fly at runtime. Templates can be supplied either as inline functions (which are discovered if you've built them at compile time), as URLs (which are loaded at runtime), as DOM references (which are then sourced) or as HTML strings. In the latter two cases, the templates are acquired and then c
Score: 2.625194
|
![]() |
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.5401025
|
![]() |
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.5401025
|
![]() |
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.5017085
|
![]() |
Gitana / 4.0 / Forms / Fields / Select FieldSelect Field The select field. Properties Title Select Description A search box field Field Type select Base Field Type list 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 allow it to be initially selected (although this value will be invalid and must be changed b
Score: 2.3924804
|
![]() |
Gitana / 3.2 / Guide / Guide / UI Developers Guide / Contexts / form-subcontextform-subcontext [ { "evaluator": "context-form", "condition": true, "config": { "form-subcontext": { "items": [ { "key": "form", "title": "Form", "header": true, "order": 1000, "items": [ { "key": "form/overview", "title": "Overview", "uri": "{definitionUri}/forms/{formId}", "order": 1000 }, {
Score: 2.3792133
|
![]() |
Gitana / 4.0 / Developers / User Interface Customization / Contexts / form-subcontextform-subcontext [ { "evaluator": "context-form", "condition": true, "config": { "form-subcontext": { "items": [ { "key": "form", "title": "Form", "header": true, "order": 1000, "items": [ { "key": "form/overview", "title": "Overview", "uri": "{definitionUri}/forms/{formId}", "order": 1000 }, {
Score: 2.3792133
|
![]() |
Chat GPT and Cloud CMSLately, the the new development taking the tech world and media by storm is Chat GPT - an incredible new chatbot from Open AI which is capable of producing clear and well worded text of all kinds, from instructions to build a treehouse to poems written from the perspective of a pirate. While not perfect, the potential of this technology is immense, and got us to thinking, how might an AI of this calibur be applied to the future of content management? As it turns out, the training process for Ope
Score: 2.351644
|
![]() |
Cloud CMS Web and Mobile FormsOne of the things that Cloud CMS does really well is forms - specifically, web and mobile forms. If you’ve ever worked with the development of forms before, you know they’re pretty tricky to put together. You typically have back-end code that is responsible for taking a data structure, validating it and writing it to a database. And you also have front-end code which does user-facing data validation that is cosmetically appealing (pretty red boxes) and helpful. You need to think about customizin
Score: 2.3110714
|
![]() |
Gitana / 3.2 / Guide / Guide / UI Developers Guide / Contexts / definition-subcontextdefinition-subcontext [ { "evaluator": "context-definition", "condition": true, "config": { "definition-subcontext": { "items": [ { "key": "definition", "title": "Definition", "header": true, "order": 1000, "items": [ { "key": "definition/overview", "title": "Overview", "uri": "{definitionUri}", "order": 1000
Score: 2.221661
|
![]() |
Gitana / 4.0 / Developers / User Interface Customization / Contexts / definition-subcontextdefinition-subcontext [ { "evaluator": "context-definition", "condition": true, "config": { "definition-subcontext": { "items": [ { "key": "definition", "title": "Definition", "header": true, "order": 1000, "items": [ { "key": "definition/overview", "title": "Overview", "uri": "{definitionUri}", "order": 1000
Score: 2.221661
|
![]() |
Gitana / 4.0 / Forms / API / UsageUsage Alpaca is packaged up as a function that you call to render a form on top of a DOM element. The function takes in the target DOM element and a configuration block. It then figures out the schema, options and layout information that is needed and sets about compiling any dynamic templates and assembling any views needed to make things work. And then it renders, executing templates and committing DOM elements to the target. It wires everything up and then fires the postRender callback. At va
Score: 2.2009606
|
![]() |
Gitana / 3.2 / Guide / Guide / Forms / ReferencesReferences Forms may use a $ref variable to pull in or include the configuration of another Cloud CMS form (or sub-section of a form). This capability is designed to be compatible with the use of $ref within JSON schema for pulling in alternate schemas or definitions. $ref within schemas Cloud CMS allows you to use the $ref variable within your schemas or definitions to pull in JSON schema blocks from other definitions on the same branch. This is typically done using a QName loader and generally
Score: 2.1430755
|
![]() |
Gitana / 4.0 / Forms / CMS / ReferencesReferences Forms may use a $ref variable to pull in or include the configuration of another Cloud CMS form (or sub-section of a form). This capability is designed to be compatible with the use of $ref within JSON schema for pulling in alternate schemas or definitions. $ref within schemas Cloud CMS allows you to use the $ref variable within your schemas or definitions to pull in JSON schema blocks from other definitions on the same branch. This is typically done using a QName loader and generally
Score: 2.1430755
|
![]() |
Gitana / 3.2 / Guide / Guide / WorkflowWorkflow In explaining workflow, let's first take a look at the following things: Workflow Models Workflow Instances Workflow Tasks Workflow Payload Resources Workflow Comments Workflow History Item Workflow Events Workflow Event Handlers A workflow model is a definition of a workflow consisting of a full set of instructions on how content should be routed between participants or activities on its way toward completion. A workflow model is kind of like a blueprint describing the sequence of step
Score: 2.0195627
|