Found 601 results for "docs fields object"
The search executed in 0.002503462 seconds. That's fast.
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.473981
|
|
Gitana / 4.0 / Reference / Types / OverviewExplore various schema types including Cluster, Stack, Release, and more, with comprehensive documentation on Gitana 4.0.
Score: 12.683435
|
|
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: 12.517126
|
|
Gitana / 4.0 / Content Engine / Bulk Import / JSONImport JSON content into Cloud CMS repositories easily with the Bulk Import tool. Use JSON Schema for custom content types, like World Cup players.
Score: 12.156607
|
|
Gitana / 4.0 / Forms / Fields / Object FieldComprehensive guide on using the 'object' field in schemas, with examples and customization options for properties, types, and styles.
Score: 8.592871
|
|
Gitana / 4.0 / Reference / Types / ObjectExplore our comprehensive guide on object properties, methods, and schema for enhanced development, featuring useful links to accelerate your coding journey.
Score: 8.312934
|
|
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.160984
|
|
Gitana / 4.0 / Forms / CMS / FieldsExplore comprehensive CMS field documentation: Attachment Picker, CK Editor, File Picker, Node Picker, Related Content & Slug.
Score: 8.160984
|
|
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.072142
|
|
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.055029
|
|
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.5681076
|
|
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.2849417
|
|
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.308136
|
|
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: 6.276107
|
|
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.3908105
|
|
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.3908105
|
|
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: 5.0439873
|
|
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.847765
|
|
Gitana / 3.2 / Guide / Guide / Bulk Import / JSONEasily import JSON content into Cloud CMS with our bulk import tool, creating structured content from legacy systems.
Score: 3.4564195
|
|
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.3840632
|
|
Gitana / 3.2 / Guide / Guide / Binary Files / GridFS Binary StorageOptimize MongoDB storage with GridFS for binary files in Cloud CMS, featuring integration with Amazon S3 and other cloud solutions.
Score: 3.2272613
|
|
Gitana / 4.0 / Content Engine / Platform / Binary Files / GridFS Binary StorageOptimize your binary storage with Cloud CMS and MongoDB GridFS, ensuring efficient, scalable, and cost-effective file management.
Score: 3.2272613
|
|
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.0208197
|
|
Gitana / 4.0 / Forms / Fields / Date FieldEnhance your date fields with Bootstrap Datetime Picker and Moment.js formatting for versatile and user-friendly data input.
Score: 2.9616942
|
|
Gitana / 3.2 / Guide / Guide / Forms / Fields / CK EditorEnhance your forms with CKEditor, a customizable HTML editor with plugins, for intuitive visual editing and streamlined content management.
Score: 2.8513286
|