Found 158 results for "forms references"
The search executed in 0.001721623 seconds. That's fast.
Gitana / 4.0 / Data Engine / Content Models / ReferencesReferences References provide a way for you to link two definitions together so as to reuse one of the definitions in the other. It gives you a way to centrally define something and then have that something's schema get reused in other definitions in your content model. For example, suppose you have an my:author definition that looks like this: { "type": "object", "properties": { "firstName": { "type": "string", "title": "First Name" }, "la
Score: 36.30676
|
|
Gitana / 4.0 / Forms / OverviewForms TODO Getting Started To get started with Cloud CMS Forms, please check out the following:
Score: 19.268194
|
|
Gitana / 3.2 / Guide / Guide / Content Modeling / ReferencesReferences References provide a way for you to link two definitions together so as to reuse one of the definitions in the other. It gives you a way to centrally define something and then have that something's schema get reused in other definitions in your content model. For example, suppose you have an my:author definition that looks like this: { "type": "object", "properties": { "firstName": { "type": "string", "title": "First Name" }, "la
Score: 18.878654
|
|
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: 17.44896
|
|
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: 11.270435
|
|
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: 11.270435
|
|
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: 10.862926
|
|
Gitana / 4.0 / Forms / API / ReferencesReferences This page shows examples of using JSON schema $ref markup to reference definitions and other structures within your JSON schema definition to generate more complex and nested schema documents. The $ref convention used by Alpaca builds on top of JSON schema and allows for the $ref value to identify a URI to a remote resource. It also allows you to point to JSON structures within the current document, enabling re-use. Alpaca extends $ref by allowing for additional loaders such as a dict
Score: 10.4613285
|
|
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: 9.046482
|
|
Gitana / 4.0 / Forms / API / FormsForms Alpaca lets you wrap a standard HTML form binding around your rendered fields to support both direct HTML submits and Ajax, behind-the-scenes submits. You can pass form configuration into the Alpaca engine to control the POST itself and also to bind buttons to the screen for the user to submit the form. If you're interested in multi-step forms, take a look at the section on wizards which describes how you can split fields across multiple pages in a form. You can then capture the data at th
Score: 8.612918
|
|
Gitana / 4.0 / Forms / API / Recursive ReferencesRecursive References Alpaca tracks references when looking up schema and options information so as to avoid circular loops. A circular loop happens when a child schema points back to a parent schema. If the reference is a hard reference (meaning that Alpaca must resolve a schema before it can proceed with rendering), then process of resolving the total document schema will never complete. One example of a circular reference might be a box object with a property called contains. The contains prop
Score: 7.8585844
|
|
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: 7.6466904
|
|
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: 4.8986764
|
|
Advanced Content Modeling options (example)Question. If I have the following collections: Categories Products Product_Description_Schemas Each Product is linked to a Category. Each Category is linked to a Product_Description_Schema. The outcome I want to accomplish is that the description schema for Product X I am entering, is defined by the Category it is linked to ( which in turn is defined by the Product_Description_Schema that the Category is linked to ). e.g. Product = Hilton Hotel London, Category = Hotel, Product_Description_Schem
Score: 3.0633426
|
|
Gitana / 4.0 / Forms / API / SerializationSerialization Serialization is the process of taking the data contained in a form and converting it into JSON or some other format so that you can transport it. Alpaca serializes data for you automatically, taking into account references, nested structures, types and more. By default, Alpaca serializes into JSON that is compatible with the underlying JSON schema model. Simple Example Here is a really simple form that is loaded from JSON and then serialized back out when you click "Serialize". {%
Score: 2.9681296
|
|
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.5607252
|
|
Gitana / 3.2 / Guide / Guide / Workflow / Sample WorkflowsSample Workflows Here we provide a collection of sample workflow models that you can use as references. Please look to these as you seek to build out your own custom models. Ad hoc Approval Ad hoc Approval with Email Template Custom Form Email Notification Events Example Pooled Task Simple Publish Simple Unpublish
Score: 2.475443
|
|
Gitana / 4.0 / Developers / API / Resources / accessPolicy / List the assigned targetsList the assigned targets Finds all of the resources that are assigned targets of this access policy. The targets are returned as references which identify resources that are bestowed the grants and revokes indicated by the policy. The targets are generally Users, Groups or Teams. This method supports pagination.
Score: 2.475443
|
|
Gitana / 4.0 / Data Engine / Workflow / Sample WorkflowsSample Workflows Here we provide a collection of sample workflow models that you can use as references. Please look to these as you seek to build out your own custom models. Ad hoc Approval Ad hoc Approval with Email Template Custom Form Email Notification Events Example Pooled Task Simple Publish Simple Unpublish
Score: 2.475443
|
|
Gitana / 3.2 / Guide / Guide / Features / Inline LinksInline Links QName: f:inline-links Adds support for automatic text parsing and discovery and tracking of linked references within text-based markup (referred to here as "inline links"). When this feature is present on a node, any persistence operations (such as create or update) will run some additional logic over your text fields. If text is discovered, it is potentially parsed and the discovered contents of the text are inspected for inline links. If your text fields contain HTML, the HTML is
Score: 2.4674306
|
|
Gitana / 4.0 / Data Engine / Aspects / Inline LinksInline Links QName: f:inline-links Adds support for automatic text parsing and discovery and tracking of linked references within text-based markup (referred to here as "inline links"). When this feature is present on a node, any persistence operations (such as create or update) will run some additional logic over your text fields. If text is discovered, it is potentially parsed and the discovered contents of the text are inspected for inline links. If your text fields contain HTML, the HTML is
Score: 2.4674306
|
|
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: 2.407123
|
|
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: 2.407123
|
|
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.3792431
|
|
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.3792431
|