Found 352 results for "docs fields url"
The search executed in 0.007092663 seconds. That's fast.
![]() |
Gitana / 4.0 / Developers / Cookbooks / REST API CookbookLearn to build and query REST APIs with Gitana's detailed guide, authentication tips, code samples, and full-text search strategy.
Score: 16.9594
|
![]() |
Gitana / 4.0 / Content Engine / Content Models / ConnectorsIntegrate Cloud CMS content into your forms with Alpaca connectors, enabling dynamic data sourcing for fields like dropdowns easily.
Score: 15.557409
|
![]() |
Gitana / 4.0 / Content Engine / Content Models / Relator PropertiesExplore Relator Properties in Cloud CMS—auto-managing relationships between nodes for easy content modeling and dynamic web provisioning.
Score: 11.744646
|
![]() |
Gitana / 3.2 / Guide / Guide / Forms / FieldsExplore our comprehensive guide to form fields, including Attachment Picker, CK Editor, File Picker, Node Picker, Related Content, and Slug options.
Score: 8.201957
|
![]() |
Gitana / 4.0 / Forms / CMS / FieldsExplore comprehensive CMS field documentation: Attachment Picker, CK Editor, File Picker, Node Picker, Related Content & Slug.
Score: 8.201957
|
![]() |
Gitana / 3.2 / Guide / Guide / FormsOptimize your content management with Cloud CMS's mobile-friendly, role-based forms using the powerful Alpaca Forms engine.
Score: 8.123663
|
![]() |
Gitana / 4.0 / Forms / OverviewEnhance your web applications with Gitana's intuitive Forms engine, offering advanced schema management, role-based provisioning, and custom fields.
Score: 8.106238
|
![]() |
Gitana / 3.2 / Guide / Guide / Application Server / URL AddressabilityExplore comprehensive guides on login/logout, node, and principal URLs for effective URL addressability.
Score: 7.380849
|
![]() |
Gitana / 4.0 / Developers / Application Server / URL AddressabilityExplore URL addressability in Gitana 4.0: Learn about Login/Logout, Node URLs, and Principal URLs for app server documentation.
Score: 7.380849
|
![]() |
Gitana / 4.0 / Forms / Fields / URL FieldExplore the URL field in detail, covering its properties, schema, options, and usage examples for comprehensive web development.
Score: 7.3563194
|
![]() |
Gitana / 3.2 / Guide / Guide / Content Modeling / ConnectorsIntegrate Cloud CMS content into your forms with Alpaca connectors, enabling dynamic data sourcing for fields like dropdowns easily.
Score: 7.2539773
|
![]() |
Gitana / 4.0 / Forms / API / Custom FieldsCreate custom fields in Alpaca forms with ease. Extend field types, override methods, and access open-source code to customize UI components.
Score: 7.0051312
|
![]() |
Gitana / 4.0 / Forms / CMS / OverviewExplore 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 CookbookOptimize your REST API integration skills with our comprehensive Cloud CMS guide, including authentication, node creation, and sample queries.
Score: 5.6422663
|
![]() |
Gitana / 3.2 / Guide / Guide / UI Developers Guide / Contexts / documents-list-sort-fieldsOptimize your document management with sortable fields like Title, Description, Date, Author, and Size. Customize your experience today!
Score: 5.4302783
|
![]() |
Gitana / 4.0 / Developers / User Interface Customization / Contexts / documents-list-sort-fieldsOptimize your document management with sortable fields like Title, Description, Date, Author, and Size. Customize your experience today!
Score: 5.4302783
|
![]() |
Gitana / 3.2 / Guide / Guide / Content Modeling / Relator PropertiesOptimize your node relationships with Cloud CMS relator properties, auto-managing links between nodes for seamless content mapping.
Score: 5.39729
|
![]() |
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.8604054
|
![]() |
How to limit the fields that come back in a queryQuery 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.3273168
|
![]() |
REST based access callsThe 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.7440753
|
![]() |
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.3945954
|
![]() |
How to Retrieve content by their document library pathYou 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.0266912
|
![]() |
Gitana / 4.0 / Forms / Fields / OverviewExplore a comprehensive list of form fields with detailed documentation for multiple field types including text, date, email, and more.
Score: 2.8769846
|
![]() |
Gitana / 4.0 / Forms / API / Data SourcesOptimize your Alpaca data loading with flexible data sources for select, radio, and checkbox fields, supporting arrays, objects, URLs, and custom functions.
Score: 2.7592082
|
![]() |
Gitana / 4.0 / Developers / OverviewExplore comprehensive guides for integrating Gitana using drivers, frameworks, custom UI, and server extensions in multiple programming languages.
Score: 2.7411165
|