Found 393 results for "docs fields number"

The search executed in 0.001961943 seconds. That's fast.

Gitana / 4.0 / Forms / Fields / TinyMCE Field

TinyMCE Field The tinymce field. The TinyMCE Field renders the Tiny MCE editor control to allow users to visually work with HTML and save the results back into a text property. Properties Title Tiny MCE Description Provides an instance of a TinyMCE control for use in editing HTML Field Type tinymce Base Field Type textarea Schema Property Type Default Description allowOptionalEmpty Allows this non-required field to validate when the value is empty autocomplete string Allows you to specify the au

Score: 1.522341

Product Releases - Gitana

Product Releases - Gitana Status Releases Registry Blog Cloud CMS Platform Content Management Create, Approve and Publish quality content to production on-time. Easy editorial and workflow tools let your best work reach your customers. Enterprise Data Engine Manage, collaborate, search and distribute your highly-structured data across branches, versions and workflow-driven lifecycle. Automate Automate your content creation and approval flows while taking advantage of AI services to enhance and c

Score: 1.5199153

Gitana / 3.2 / Guide / Guide / Features / Filename

Filename QName: f:filename Allows for nodes to retain a display-friendly and file-system compatible name for use in containment-based navigation systems such as WebDAV, FTP or the Cloud CMS document library. Nodes that are tagged with this feature can either deterministically specify their preferred filename or have one calculated for them from the node's title or _doc fields. Filenames may not contain the following special characters: .:_<>?&@!$%^()-+=\. If these characters are included, they w

Score: 1.5196328

Gitana / 4.0 / Data Engine / Aspects / Filename

Filename QName: f:filename Allows for nodes to retain a display-friendly and file-system compatible name for use in containment-based navigation systems such as WebDAV, FTP or the Cloud CMS document library. Nodes that are tagged with this feature can either deterministically specify their preferred filename or have one calculated for them from the node's title or _doc fields. Filenames may not contain the following special characters: .:_<>?&@!$%^()-+=\. If these characters are included, they w

Score: 1.5196328

Gitana / 4.0 / Developers / Drivers / JavaScript (Legacy)

JavaScript (Legacy) Connect your HTML browser applications to Gitana Latest Version Version undefined Date The Gitana JavaScript driver can be dropped into any web or mobile application running in the browser, within Node.js or any of a host of web frameworks including jQuery, Vue.js, Next.js, Nuxt and many others. Loading the Driver In the Browser ### Using AMD define(["gitana"], function(Gitana) { Gitana.connect({...}, function() { // ...your code

Score: 1.5166814

Gitana / 3.2 / Guide / Guide / User Interface / Projects / Configure Search

Configure Search You can configure the project search page to show different filter controls on the left hand side by adding some properties to your project JSON descriptor. These controls ultimately feed into a Cloud CMS node API find call that has the following structure: { "query": ... query block into MongoDB, "search": ... search block into Elastic Search } The following customization block can be added to your project's JSON descriptor: { ..., "search": { "showContentTypes"

Score: 1.4830086

Gitana / 4.0 / Forms / API / Forms

Forms 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: 1.4830086

Gitana / 4.0 / User Interface / Projects / Configure Search

Configure Search You can configure the project search page to show different filter controls on the left hand side by adding some properties to your project JSON descriptor. These controls ultimately feed into a Cloud CMS node API find call that has the following structure: { "query": ... query block into MongoDB, "search": ... search block into Elastic Search } The following customization block can be added to your project's JSON descriptor: { ..., "search": { "showContentTypes"

Score: 1.4830086

Gitana / 3.2 / Guide / Guide / Templates

Templates Cloud CMS supports the usage of templates at various points to generate presentation and output for things like emails, PDFs, web page components and more. Cloud CMS supports two template engines - Handlebars and Freemarker. In general, we recommend using Handlebars since the syntax is a bit easier. This document covers Handlebars and describes helper functions available in Handlebars that make processing simpler. Model Variables The following describes the internal structure of model

Score: 1.4317853

Gitana / 4.0 / Data Engine / Templates / Overview

Templates Cloud CMS supports the usage of templates at various points to generate presentation and output for things like emails, PDFs, web page components and more. Cloud CMS supports two template engines - Handlebars and Freemarker. In general, we recommend using Handlebars since the syntax is a bit easier. This document covers Handlebars and describes helper functions available in Handlebars that make processing simpler. Model Variables The following describes the internal structure of model

Score: 1.4317853

Gitana / 3.2 / Guide / Guide / API / Data Types / Registration

Registration Type {{#dataTypeArticle objectTypeId}}{{objectTypeId}}{{/dataTypeArticle}} Datastore Type {{#dataTypeArticle datastoreTypeId}}{{datastoreTypeId}}{{/dataTypeArticle}} Supports {{#article "security/authorities"}}authorities{{/article}}, {{#article "security/permissions"}}permissions{{/article}}, {{#article "transfer"}}transfer{{/article}} The minimum registration flow looks like this: The application collects the user's email The application creates an Registration object. It stores t

Score: 1.4229496

Gitana / 4.0 / Data Engine / API / Data Types / Registration

Registration Type {{#dataTypeArticle objectTypeId}}{{objectTypeId}}{{/dataTypeArticle}} Datastore Type {{#dataTypeArticle datastoreTypeId}}{{datastoreTypeId}}{{/dataTypeArticle}} Supports {{#article "security/authorities"}}authorities{{/article}}, {{#article "security/permissions"}}permissions{{/article}}, {{#article "transfer"}}transfer{{/article}} The minimum registration flow looks like this: The application collects the user's email The application creates an Registration object. It stores t

Score: 1.4229496

Gitana / 3.2 / Guide / Guide / Features / Rates

Rates QName: f:rates Applied to an association to indicate that the target node contains a property with a rating value that should be used to aggregate (increment or decrement) rating statistics on the source. This feature automatically computes rating statistics on the source node for the property indicated on the target node. The following statistics are aggregated on the source node: { "_statistics": { "ratingTotalCount": , "ratingTotalValue": , "r

Score: 1.4213464

Gitana / 4.0 / Data Engine / Aspects / Rates

Rates QName: f:rates Applied to an association to indicate that the target node contains a property with a rating value that should be used to aggregate (increment or decrement) rating statistics on the source. This feature automatically computes rating statistics on the source node for the property indicated on the target node. The following statistics are aggregated on the source node: { "_statistics": { "ratingTotalCount": , "ratingTotalValue": , "r

Score: 1.4213464

Gitana / 3.2 / Guide / Guide / UI Developers Guide / UI Views

UI Views Customized changes to the user interface configuration can be introduced through the use of UI View configuration documents. UI Views are JSON documents that contain one or more configuration blocks. The UI View configuration blocks are loaded after the standard configuration document and therefore have the opportunity to either extend or override the base configuration. UI View are scoped either to the platform or to the project. As such, you can use UI Config objects to customize the

Score: 1.4063928

Gitana / 4.0 / Developers / User Interface Customization / UI Views

UI Views Customized changes to the user interface configuration can be introduced through the use of UI View configuration documents. UI Views are JSON documents that contain one or more configuration blocks. The UI View configuration blocks are loaded after the standard configuration document and therefore have the opportunity to either extend or override the base configuration. UI View are scoped either to the platform or to the project. As such, you can use UI Config objects to customize the

Score: 1.4063928

Gitana / 4.0 / Forms / API / Observables

Observables 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: 1.397143

Gitana / 3.2 / Guide / Guide / Features / Geolocation

Geolocation QName: f:geolocation Indicates that this node supports geolocation properties. This feature provisions the node with a loc property that contains two sub-properties - lat and long. { "properties": { "loc": { "type": "object", "title": "Geolocation Details", "properties": { "lat": { "type":"number", "title": "Latitude", "minimum": -180, "maxim

Score: 1.3967962

Gitana / 4.0 / Data Engine / Aspects / Geolocation

Geolocation QName: f:geolocation Indicates that this node supports geolocation properties. This feature provisions the node with a loc property that contains two sub-properties - lat and long. { "properties": { "loc": { "type": "object", "title": "Geolocation Details", "properties": { "lat": { "type":"number", "title": "Latitude", "minimum": -180, "maxim

Score: 1.3967962

Gitana / 3.2 / Guide / Guide / Bulk Import / JSON

JSON The Cloud CMS Bulk Import tool makes it easy to import JSON content into a Cloud CMS content repository. JSON is a common format for content that has been exported from an existing database or legacy CMS system. Suppose that we have a JSON file containing an array of player information from the 2014 World Cup. This file is located at data/2014-world-cup-squads.json and looks more or less like this: [{ "Team": "Portugal", "Number": "7", "Position": "FW", "FullName": "Cristian

Score: 1.3857336

Gitana / 4.0 / Data Engine / Bulk Import / JSON

JSON The Cloud CMS Bulk Import tool makes it easy to import JSON content into a Cloud CMS content repository. JSON is a common format for content that has been exported from an existing database or legacy CMS system. Suppose that we have a JSON file containing an array of player information from the 2014 World Cup. This file is located at data/2014-world-cup-squads.json and looks more or less like this: [{ "Team": "Portugal", "Number": "7", "Position": "FW", "FullName": "Cristian

Score: 1.3857336

Gitana / 3.2 / Guide / Guide / Forms / Fields / Related Content

Related Content ID: related-content The related-content field type renders an upload field that is pre-configured to upload assets and store them as standalone document nodes within the content graph. This is useful, say, if you wanted to let end users upload images and store them in an /Images folder. Sample configuration: { "type": "related-content", "uploadPath": "/Images" } The related content control should be modeled on top of either an object or an array field. This is very simil

Score: 1.3715281

Gitana / 4.0 / Forms / CMS / Fields / Related Content

Related Content ID: related-content The related-content field type renders an upload field that is pre-configured to upload assets and store them as standalone document nodes within the content graph. This is useful, say, if you wanted to let end users upload images and store them in an /Images folder. Sample configuration: { "type": "related-content", "uploadPath": "/Images" } The related content control should be modeled on top of either an object or an array field. This is very simil

Score: 1.3715281

Definitions for Date format

Our 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: 1.3623428

Managing a large number of PDFs or images

In Cloud CMS everything is a node. A node has JSON properties and could also have binary attachments. What you would call a "file" is a node with properties describing it's folder location and a "default" attachment holding the payload (PDF file, image, MSWord doc, etc). Typically, for large number of PDFs, images, etc, we suggest individual nodes with a single attachment each (which is the PDF, image, etc). We have many customers who use Cloud CMS in this way and it essentially works like a doc

Score: 1.3592335