Found 499 results for "gitana 4.0 developers api resources conflict get-repositories-repositoryid-conflicts"
The search executed in 0.002781409 seconds. That's fast.
![]() |
Gitana 4.0 / Content Engine / Deployment / Deployment MappingsOptimize your content deployment with Cloud CMS using S3, FTP, and File System Handlers for precise file system mappings and strategies.
Score: 1.8507178
|
![]() |
Gitana 3.2 / Guide / Guide / BranchesOptimize your content management with Cloud CMS. Enjoy powerful features like changeset versioning, branching, and snapshots for seamless workflow transitions.
Score: 1.8404924
|
![]() |
Gitana 4.0 / Content Engine / Branch OverviewOptimize your content management with Cloud CMS branches. Enjoy unique, Git-like versioning, easy branching, and efficient content integration.
Score: 1.8404924
|
![]() |
Gitana 4.0 / Reference / Types / Access PolicyExplore our Access Policy guide to learn about creating, updating, and managing policies within the Gitana platform, complete with examples and schema details.
Score: 1.818124
|
![]() |
Gitana 4.0 / Getting Started / Working with Content / VersioningExplore Cloud CMS's changeset versioning, offering a Git-like, seamless, collaborative environment for content management without file locking issues.
Score: 1.8094352
|
![]() |
Gitana 3.2 / Guide / Guide / UI Developers Guide / SamplesDiscover essential UI extension samples for developers, featuring configurations, UI modules, views, and custom integration guides.
Score: 1.8046377
|
![]() |
Gitana 4.0 / Developers / User Interface Customization / SamplesExplore sample configurations for building UI extensions, including items for developer menus and releases, with detailed guides on UI services and modules.
Score: 1.8046377
|
![]() |
What is the reason for "Failed to index node"?If you scan your log entries and see "Failed to index node", this indicates that Elastic Search failed to update its index for a node. Cloud CMS tells Elastic Search to updates its index whenever a node is created or updated. When a node is deleted, Cloud CMS tells Elastic Search to remove the node from its index. This error message means that Elastic Search failed to update the index and therefore the index wasn't updated. If you open up the error, you may see further information that indicates
Score: 1.7577734
|
![]() |
Gitana 3.2 / Guide / Guide / Features / Auto Analyze TextAuto Analyze Text feature automatically analyzes binary attachments for full-text search insights, enhancing node functionality.
Score: 1.7551755
|
![]() |
Gitana 3.2 / Guide / Guide / Features / Auto OCR ExtractAutomatically convert attachments to searchable text with auto OCR extraction, enhancing full-text indexing and streamline content retrieval.
Score: 1.7551755
|
![]() |
Gitana 3.2 / Guide / Guide / API / PaginationOptimize data retrieval and display with pagination in Cloud CMS, organizing result sets into manageable pages for efficient sorting and querying.
Score: 1.7453365
|
![]() |
Gitana 3.2 / Guide / Guide / Integrations / OktaDiscover how Okta enhances security by integrating user authentication into modern applications with Cloud CMS Single Sign-On support.
Score: 1.742877
|
![]() |
Gitana 4.0 / Content Engine / Integrations / OktaSecure and manage user authentication with Okta and Cloud CMS, offering seamless SSO integration using SAML 2.0 and JWT.
Score: 1.742877
|
![]() |
Gitana 3.2 / Guide / Guide / Actions / Web HookOptimize your HTTP web hook calls with detailed configuration options for authentication, headers, and payloads, ensuring secure and effective communication.
Score: 1.7148502
|
![]() |
Gitana 4.0 / Content Engine / Behaviors / Actions / Web HookOptimize your HTTP web hook calls with detailed configuration options for authentication, headers, and payloads, ensuring secure and effective communication.
Score: 1.7148502
|
![]() |
Gitana 4.0 / Getting Started / Working with Content / FormsCreate and customize dynamic web forms with Cloud CMS’s intuitive engine, leveraging Alpaca.js for seamless integration with JSON Schema.
Score: 1.677275
|
![]() |
Gitana 3.2 / Guide / Guide / Docker / Kits / MongoDB Replica SetSet up a 3-node MongoDB Replica Set with ease, using our guide, Gitana SDK, and Docker Compose for optimal database performance.
Score: 1.6638719
|
![]() |
Gitana 4.0 / Content Engine / Access Policies / System Policies / project-managerDiscover Gitana's System Access Policy for project management. Enhance access control with JSON-based policies.
Score: 1.6629951
|
![]() |
Gitana 4.0 / Content Engine / Access Policies / System Policies / project-ownerExplore the Gitana System Access Policy for project-owner, detailing JSON configuration and role-based permissions.
Score: 1.6629951
|
![]() |
Gitana 3.2 / Guide / Guide / Getting Started / Web FormsEffortlessly create dynamic web forms with Cloud CMS using customizable, open-source controls powered by Alpaca.js and JSON Schema integration.
Score: 1.6616389
|
![]() |
Gitana 3.2 / Guide / Guide / TranscriptionAutomatically convert audio files to text with Cloud CMS transcription. Sync updates effortlessly. Ideal for search indexing and seamless content management.
Score: 1.6550726
|
![]() |
Gitana 3.2 / Guide / Guide / Features / Auto RecognizeEnhance images with Auto Recognize to detect faces, celebrities, labels, and text for deeper content insights. Configure your Recognition Service for seamless integration.
Score: 1.6550726
|
![]() |
Gitana 4.0 / Content Engine / Access Policies / System Policies / platform-connectorExplore Gitana's 'platform-connector' System Access Policy for seamless platform connectivity management.
Score: 1.6543355
|
![]() |
Gitana 4.0 / Content Engine / Access Policies / System Policies / project-read-all-contentExplore Gitana's project-read-all-content policy that allows content reading in projects under specific conditions.
Score: 1.6500393
|
![]() |
Gitana 4.0 / Content Engine / Access Policies / Templates / read-all-contentAccess Policy Template for Gitana 4.0: Allow project members to consume all content with JSON configuration.
Score: 1.6500393
|