Found 345 results for "docs fields url"

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

Gitana 4.0 / Developers / Cookbooks / REST API Cookbook

Optimize your REST API usage with Gitana's comprehensive guide, covering OAuth2 for authentication, sample queries, node creation, and associations.

Score: 16.9594

Gitana 4.0 / Content Engine / Content Models / Connectors

Integrate Cloud CMS content into your forms with Alpaca connectors, enabling dynamic data sourcing for fields like dropdowns easily.

Score: 15.553138

Gitana 4.0 / Content Engine / Content Models / Relator Properties

Explore Relator Properties in Cloud CMS—auto-managing relationships between nodes for easy content modeling and dynamic web provisioning.

Score: 11.741304

Gitana 3.2 / Guide / Guide / Forms / Fields

Explore our comprehensive guide to form fields, including Attachment Picker, CK Editor, File Picker, Node Picker, Related Content, and Slug options.

Score: 8.184945

Gitana 4.0 / Forms / CMS / Fields

Explore comprehensive CMS field documentation: Attachment Picker, CK Editor, File Picker, Node Picker, Related Content & Slug.

Score: 8.184945

Gitana 3.2 / Guide / Guide / Forms

Optimize your content management with Cloud CMS's mobile-friendly, role-based forms using the powerful Alpaca Forms engine.

Score: 8.118458

Gitana 4.0 / Forms

Enhance your web applications with Gitana's intuitive Forms engine, offering advanced schema management, role-based provisioning, and custom fields.

Score: 8.101091

Gitana 3.2 / Guide / Guide / Application Server / URL Addressability

Explore comprehensive guides on login/logout, node, and principal URLs for effective URL addressability.

Score: 7.403657

Gitana 4.0 / Developers / Application Server / URL Addressability

Explore URL addressability in Gitana 4.0: Learn about Login/Logout, Node URLs, and Principal URLs for app server documentation.

Score: 7.403657

Gitana 4.0 / Forms / Fields / URL Field

Explore the URL field in detail, covering its properties, schema, options, and usage examples for comprehensive web development.

Score: 7.3787575

Gitana 3.2 / Guide / Guide / Content Modeling / Connectors

Integrate Cloud CMS content into your forms with Alpaca connectors, enabling dynamic data sourcing for fields like dropdowns easily.

Score: 7.177459

Gitana 4.0 / Forms / API / Custom Fields

Create custom fields in Alpaca forms with ease. Extend field types, override methods, and access open-source code to customize UI components.

Score: 6.98828

Gitana 4.0 / Forms / CMS

Explore our comprehensive guide to forms, designed to simplify data collection and enhance user experience on your website.

Score: 6.3583345

Gitana 3.2 / Guide / Guide / Cookbooks / REST API Cookbook

Optimize your REST API integration skills with our comprehensive Cloud CMS guide, including authentication, node creation, and sample queries.

Score: 5.570419

Gitana 3.2 / Guide / Guide / UI Developers Guide / Contexts / documents-list-sort-fields

Optimize your document management with sortable fields like Title, Description, Date, Author, and Size. Customize your experience today!

Score: 5.415423

Gitana 4.0 / Developers / User Interface Customization / Contexts / documents-list-sort-fields

Optimize your document management with sortable fields like Title, Description, Date, Author, and Size. Customize your experience today!

Score: 5.415423

Gitana 3.2 / Guide / Guide / Content Modeling / Relator Properties

Optimize your node relationships with Cloud CMS relator properties, auto-managing links between nodes for seamless content mapping.

Score: 5.3296647

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

How to limit the fields that come back in a query

Query 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.3464565

REST based access calls

The authentication mechanism in Cloud CMS is OAuth 2.0. While you can use any of the flows, the easiest one to begin with is "password". We've outlined a basic example here using Advanced REST Client to show our API-first platform in action. First, from your Cloud CMS platform home page, navigate to "Manage Platform" and select the "API Keys" section to list all available projects for remote access: If you have no keys for your project then create a new "Application" from "Manage Platform" and t

Score: 3.7796254

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

How to Retrieve content by their document library path

You 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: 3.053615

Gitana 4.0 / Forms / Fields

Explore a comprehensive list of form fields with detailed documentation for multiple field types including text, date, email, and more.

Score: 2.8996387

Gitana 4.0 / Forms / API / Data Sources

Optimize your Alpaca data loading with flexible data sources for select, radio, and checkbox fields, supporting arrays, objects, URLs, and custom functions.

Score: 2.7879612

Gitana 4.0 / Developers

Explore comprehensive guides for integrating Gitana using drivers, frameworks, custom UI, and server extensions in multiple programming languages.

Score: 2.7627506