Found 634 results for "gitana 4.0 developers api definitions application"
The search executed in 0.0027 seconds. That's fast.
![]() |
Gitana 4.0 / Content Engine / Single Sign On (SSO) / JWTDocumentation Reference Learn how to configure JWT with Cloud CMS for seamless Single Sign-On integration. Includes practical examples. (Gitana 4.0)
Score: 0.8146
|
![]() |
Gitana 3.2 / Guide / Guide / Features / ContainerDocumentation Reference Mark nodes as containers in Cloud CMS for path-based navigation without needing a folder structure. (Gitana 3.2)
Score: 0.8086
|
![]() |
Gitana 3.2 / Guide / Guide / Docker / Upgrades / 3.2.73Documentation Reference Upgrade to Cloud CMS 3.2.73 with a focus on ElasticSearch client configuration for optimal performance. (Gitana 3.2)
Score: 0.8086
|
![]() |
Gitana 3.2 / Guide / Guide / Docker / Upgrades / 3.2.74Documentation Reference Upgrade to Cloud CMS 3.2.74 and optimize with new ElasticSearch client; ensure smooth transition with our upgrade tool. (Gitana 3.2)
Score: 0.8086
|
![]() |
Gitana 3.2 / Guide / Guide / Docker / Upgrades / 3.2.76Documentation Reference Upgrade to Cloud CMS 3.2.76 smoothly. Use the Condor driver for ElasticSearch and our CLI tool for seamless updates. (Gitana 3.2)
Score: 0.8086
|
![]() |
Gitana 4.0 / Content Engine / Aspects / ContainerDocumentation Reference Transform your content organization with Cloud CMS containers, enabling flexible relationship modeling without folder constraints. (Gitana 4.0)
Score: 0.8086
|
![]() |
Gitana 3.2 / Guide / Guide / Docker / Configuration / SupportDocumentation Reference Optimize your Cloud CMS support by submitting detailed tickets with logs, dumps, or exports for faster resolutions. (Gitana 3.2)
Score: 0.8012
|
![]() |
Programmatically create content in a folder?Support Article The Cloud CMS content API lets you work with JSON to create any kind of content you'd like. It supports any JSON structure you desire and also supports a number of special properties that you can use to make life easier for you. These special properties are: _rootNodeId - The mount node ID of the root against which relatives path are computed. By default, this is the root of the repository. In general, it isn't necessary to use this property unless you have multiple mount nodes configured. And m
Score: 0.7841
|
![]() |
Gitana 3.2 / Guide / Guide / Docker / Upgrades / 3.2.77Documentation Reference Upgrade to Cloud CMS 3.2.77 seamlessly with our new tools and detailed release notes. (Gitana 3.2)
Score: 0.7611
|
![]() |
Gitana 3.2 / Guide / Guide / Docker / Upgrades / 3.2.78Documentation Reference Upgrade to Cloud CMS 3.2.78 with enhanced ElasticSearch and Redis support. Access our trusted upgrade tool for seamless integration. (Gitana 3.2)
Score: 0.7611
|
![]() |
Gitana 3.2 / Guide / Guide / API / System MetadataDocumentation Reference Cloud CMS tracks system metadata for object creation and modification, offering key insights for data management. (Gitana 3.2)
Score: 0.7601
|
![]() |
Gitana 4.0 / Developers / API / System MetadataDocumentation Reference Track and utilize system metadata in Cloud CMS with ease, including creation, modification, and edit details. (Gitana 4.0)
Score: 0.7601
|
![]() |
Gitana 3.2 / Guide / Guide / Features / RenditionableDocumentation Reference Optimize content with automated renditions using our advanced rendition engines for seamless updates. (Gitana 3.2)
Score: 0.7558
|
![]() |
Gitana 4.0 / Content Engine / Aspects / RenditionableDocumentation Reference Optimize your document management with f:renditionable feature for automated content updates and seamless synchronization. (Gitana 4.0)
Score: 0.7558
|
![]() |
Gitana 4.0 / Content Engine / Branch Overview / BranchesDocumentation Reference Enhance collaboration and content management with Cloud CMS Branches. Create, merge, and manage content in isolated environments. (Gitana 4.0)
Score: 0.7447
|
![]() |
Gitana 3.2 / Guide / Guide / UI Developers Guide / UI ViewsDocumentation Reference Optimize your user interface with customizable UI Views, allowing dynamic customization for platform and project configurations. (Gitana 3.2)
Score: 0.7425
|
![]() |
Gitana 3.2 / Guide / Guide / Docker / Upgrades / 3.2.75Documentation Reference Upgrade to Cloud CMS 3.2.75 for enhanced ElasticSearch support and improved data transfer schema efficiency. (Gitana 3.2)
Score: 0.7395
|
![]() |
Gitana 3.2 / Guide / Guide / Features / PrecompileDocumentation Reference Automatically transform Markdown to HTML with Precompile, streamlining text conversions for versatile frontend use. (Gitana 3.2)
Score: 0.7364
|
![]() |
Gitana 4.0 / Content Engine / Aspects / PrecompileDocumentation Reference Automatically compile Markdown to HTML with precompile feature for seamless content transformation. (Gitana 4.0)
Score: 0.7364
|
![]() |
Gitana 4.0 / Forms / API / TemplatesDocumentation Reference Discover Alpaca's dynamic templating system with powerful customization of views, layouts, and forms using Handlebars or your own engine. (Gitana 4.0)
Score: 0.7113
|
![]() |
Gitana 3.2 / Guide / Guide / WorkspacesDocumentation Reference Optimize your content workflow with Cloud CMS Workspaces. Collaborate efficiently, manage versions, and resolve conflicts seamlessly. (Gitana 3.2)
Score: 0.705
|
![]() |
How does security work in Cloud CMS?Support Article Cloud CMS provides two ways to describe access rights to things: Object-level / role-based authorities Team / role-based authorities With object-level / role-based authorities, you assign a principal (either a user or a group) a role against something. For example, you might give Joe the CONSUMER role against a content node. When Joe then interacts with the content node in the future, he will do so with the CONSUMER role which will allow him to "read" the node. With team / role-based authorities
Score: 0.6812
|
![]() |
Gitana 3.2 / Guide / Guide / User Interface / LockingDocumentation Reference Optimize document collaboration with Cloud CMS's transactional locking and manual lock/unlock features for seamless editing experience. (Gitana 3.2)
Score: 0.6638
|
![]() |
Gitana 4.0 / User Interface / User Interface / LockingDocumentation Reference Ensure secure editing with Cloud CMS's transactional locking, preventing data conflicts with manual document lock/unlock features. (Gitana 4.0)
Score: 0.6638
|
![]() |
CMS editor LockingSupport Article There are two levels of locking which usually come into play in a scenario like this. One is a "UI lock" which is taken out when a user begins editing something within the user interface. This lock is released when they finished editing (either by hitting save or canceling). The other lock is a "data lock" which is a transactional lock taken out when the write of multiple documents begins. This is a transactional lock in the sense that it blocks other write operations against those documents and
Score: 0.6638
|