Found 560 results for "gitana 4.0 forms api layouts-example1-template"

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

Gitana / 4.0 / Developers / Application Server / Services / Duster

Duster The Duster Service provides template rendering using the LinkedIn Dust.js template engine. The Duster Service loads output templates for you, executes Dust across them and outputs markup like HTML and JSON. It allows you to build full web sites or custom APIs using a powerful template engine. Tags The Cloud CMS Application Server provides a library of * Dust Tags available out of the box. These are listed in more detail on the left-hand side menu. Fragment Caching Some Dust tags support c

Score: 1.1034725

CEM - shuffling deck chairs on the titanic

Going back 15 years, we’ve seen the core of providing websites shift across various types of “platforms” - from Web Content Management (WCM) to Enterprise Content Management (ECM) to Customer Experience Management (CEM). Every iteration involved another set of technologies, and associated migration headaches. Each expansion also consumed more and more of the resulting presentation tier. At first, this was mostly a good thing as no standard mechanisms existed to facilitate efforts. However, in th

Score: 1.1034725

Gitana / 3.2 / Guide / Guide / Application Server / Services / Flow

Flow Provides API services for browser-side UI application wizards whose configuration is defined in JSON. { "flow": { "enabled": true } }

Score: 1.1016929

Gitana / 4.0 / Developers / Application Server / Services / Flow

Flow Provides API services for browser-side UI application wizards whose configuration is defined in JSON. { "flow": { "enabled": true } }

Score: 1.1016929

Gitana / 4.0 / Reference / Types / Node

Node An Object Platform Repository Node Table of Contents Overview Parent Objects Properties Methods Examples Schema All of the content in your branch is stored as Nodes. Nodes are vertexes in an arbitrarily structured graph. You store your content in Nodes and you relate Nodes to one another using Associations. Associations are a special kind of Node that points from one non-association Node to another. Nodes are also typed. Every node you create takes on a type. Types are identified by their Q

Score: 1.0992972

Gitana / 3.2 / Guide / Guide / User Interface / Releases

Releases Releases allow you to set up collaborative workspaces where future sets of content can be worked on in real-time. Content can be created, edited and deleted in the workspace and then scheduled for publishing at a future date. Scheduled publishing allows your content to "go live" automatically - merging your content changes back into the mainline while triggering release actions for things like: Email Notifications CDN Synchronization Web Hook Calls Releases give your content team the ab

Score: 1.094229

Gitana / 4.0 / User Interface / User Interface / Releases

Releases Releases allow you to set up collaborative workspaces where future sets of content can be worked on in real-time. Content can be created, edited and deleted in the workspace and then scheduled for publishing at a future date. Scheduled publishing allows your content to "go live" automatically - merging your content changes back into the mainline while triggering release actions for things like: Email Notifications CDN Synchronization Web Hook Calls Releases give your content team the ab

Score: 1.094229

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.0916189

Gitana / 4.0 / Content 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.0916189

Gitana / 3.2 / Guide / Guide / Features / Multilingual

Multilingual QName: f:multilingual When applied to a node, this indicates that you wish to have the contents of this node support multilingual behavior and translated content. This node then serves as the "master node" for translation support. Master nodes have a:has_translation associations to translation nodes that hold copies of the content (JSON and any attachments) in the target locale. Marking a node as f:multilingual does not automatically produce translations for you. However, once marke

Score: 1.0913842

Gitana / 4.0 / Content Engine / Aspects / Multilingual

Multilingual QName: f:multilingual When applied to a node, this indicates that you wish to have the contents of this node support multilingual behavior and translated content. This node then serves as the "master node" for translation support. Master nodes have a:has_translation associations to translation nodes that hold copies of the content (JSON and any attachments) in the target locale. Marking a node as f:multilingual does not automatically produce translations for you. However, once marke

Score: 1.0913842

Finding sanity by losing your head

There was a lot of chatter last year regarding a “headless” or “decoupled” CMS design. Zeitgeist, maybe… countermovement, definitely. Since their inception, every expansion of content management software along the continuum from managing basic websites to full-on digital experiences drove CMSes further and further into the application’s presentation tier. In parallel, we witnessed the maturity of frameworks such as Angular, Ember, and Ionic (just to name a few) - all pushing development out to t

Score: 1.0913842

How do I retrieve the folder path for my content?

In Cloud CMS, you may choose to associate nodes with folders. This allows the content to be worked with by editorial teams such that they can navigate to content within folders, move content between folders and generally organize their content as they wish. It also allows for content to be retrieved by path via the API, if you wish. Technically speaking, Cloud CMS does not require folders or paths. In fact, plenty of customers use Cloud CMS in such a way that they don't require folders at all. C

Score: 1.0899745

Gitana / 3.2 / Guide / Guide / Application Server / Services / Virtual Driver

Virtual Driver Defines the virtual driver connection used to dynamically retrieve API keys on behalf of incoming tenants. { "virtualDriver": { "enabled": false, "clientKey": "", "clientSecret": "", "username": "", "password": "", "baseURL": "", "application": "" } }

Score: 1.0881557

Gitana / 4.0 / Developers / Application Server / Services / Virtual Driver

Virtual Driver Defines the virtual driver connection used to dynamically retrieve API keys on behalf of incoming tenants. { "virtualDriver": { "enabled": false, "clientKey": "", "clientSecret": "", "username": "", "password": "", "baseURL": "", "application": "" } }

Score: 1.0881557

Using the JavaScript driver to run an elasticsearch query

The Cloud CMS REST API allows for elasticsearch queries against a branch. The API endpoint is POST /repositories/{repositoryId}/branches/{branchId}/nodes/search The payload is a JSON object containing a top-level property called "search" which wraps the elasticsearch DSL query. The JavaScript driver exposes this call on the Branch object using the searchNodes() methods. Examples: 1) Search for nodes containing the keyword "hello" in any property: req.branch(function (err, branch) { branch.trap(f

Score: 1.0795579

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: 1.0795579

Tree Hierarchies

In Cloud CMS, there are no hard and fast rules regarding association types between nodes. And so, when dealing with things like tree structures, you usually have to first make some assumptions about the kinds of relationships between nodes that you want to traverse. For arbitrary relationships and traversals around nodes, Cloud CMS provides traversal methods which are a bit more intensive to use. However, if you're using typical a:child relationships between nodes (which is what Cloud CMS uses f

Score: 1.0743032

How can I retrieve content for a tree view?

The Cloud CMS API offers a number of convenience API methods that go beyond basic CRUD and bulk content operations. Among these methods are those that allow you to retrieve content from your repository branch in a tree-friendly format. A tree-organized format means that the data comes back in a such a way as to make it easy to load into front-end tree controls. Typical front-end tree controls requires the ability to load a "snapshot" of the tree as a starting point as well as iteratively grow or

Score: 1.0743032

Gitana / 3.2 / Guide / Guide / Applications / Public Services / Forgot Username Flow

Forgot Username Flow Registered users for your application may forget their username and lose the ability to log in to your app. Cloud CMS provides a "forgot username" flow that you can use to provide a way for end users to securely retrieve their username using their registered email address. On this page, we cover a public convenience method that applications can use to easily provide this functionality without having to through the most robust Cloud CMS object-level APIs. If you're interested

Score: 1.0701361

Gitana / 4.0 / Content Engine / Platform / Applications / Public Services / Forgot Username Flow

Forgot Username Flow Registered users for your application may forget their username and lose the ability to log in to your app. Cloud CMS provides a "forgot username" flow that you can use to provide a way for end users to securely retrieve their username using their registered email address. On this page, we cover a public convenience method that applications can use to easily provide this functionality without having to through the most robust Cloud CMS object-level APIs. If you're interested

Score: 1.0701361

Gitana / 4.0 / Forms / Fields / Select Field

Select 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: 1.0697439

Gitana / 3.2 / Guide / Guide / Deployment / Deployment Receivers

Deployment Receivers A Deployment Receiver acts as an endpoint for local and remote Deployment Handlers that seek to ship their Deployment Packages to a destination. These are frequently used to move content between data centers or across different parts of the world to solve for latency issues (or to simply move content to the correct side of a DMZ for security reasons or runtime-performance reasons). Cloud CMS lets you create Deployment Receivers from within its user interface. You can create

Score: 1.0590761

Gitana / 3.2 / Guide / Guide / Application Server / Tags / @query

@query Queries for nodes and makes those nodes available to the template. Parameters parameter required description type the type of node to query for (definition QName) sort the field to sort on sortDirection the direction to sort in (either 1 for ascending or -1 for descending) limit the number of records to return fields comma separated list of property names to include in query results skip a position to skip ahead to in the record set scope if "page", then only relatives related to the curr

Score: 1.0590761

Gitana / 4.0 / Developers / Application Server / Tags / @query

@query Queries for nodes and makes those nodes available to the template. Parameters parameter required description type the type of node to query for (definition QName) sort the field to sort on sortDirection the direction to sort in (either 1 for ascending or -1 for descending) limit the number of records to return fields comma separated list of property names to include in query results skip a position to skip ahead to in the record set scope if "page", then only relatives related to the curr

Score: 1.0590761