Found 659 results for "gitana 4.0 developers api definitions email"
The search executed in 0.003356595 seconds. That's fast.
![]() |
Gitana 4.0 / Getting StartedExplore the Gitana Platform with our Getting Started Guide, featuring key concepts and links to detailed documentation. Dive in now!
Score: 1.6007314
|
![]() |
Gitana 3.2 / Guide / Guide / ReportsGenerate comprehensive reports in CSV, PDF, or ZIP with Cloud CMS, using export configurations tailored for your business needs.
Score: 1.5974855
|
![]() |
Gitana 4.0 / Content Engine / Nodes / ReportsGenerate comprehensive reports in CSV, PDF, or ZIP with Cloud CMS, using export configurations tailored for your business needs.
Score: 1.5974855
|
![]() |
Gitana 4.0 / Reference / Types / PlatformAccess Cloud CMS data stores and platform-scoped objects with authentication for robust data management and development.
Score: 1.5951924
|
![]() |
Gitana 4.0 / Content Engine / Access Policies / Templates / read-all-content-from-all-projectsExplore the Gitana Access Policy Template, enabling management of all content across projects using the identifier read-all-content-from-all-projects.
Score: 1.5925752
|
![]() |
Gitana 4.0 / Content Engine / Access Policies / Templates / edit-all-content-with-a-propertyLearn about Gitana's Access Policy Template for editing all content with a specific property value.
Score: 1.5925752
|
![]() |
Gitana 4.0 / Content Engine / Access Policies / Templates / read-all-content-in-a-folderExplore Gitana's Access Policy Template for reading all content in a folder, supporting consumer roles with path-specific permissions.
Score: 1.5925752
|
![]() |
Gitana 3.2 / Guide / Guide / Features / Auto TranslateAutomatically translate and synchronize content in multiple languages using Cloud CMS with AWS, Azure, or Google services.
Score: 1.5867221
|
![]() |
Gitana 4.0 / Content Engine / Aspects / Auto TranslateAutomatically translate and localize content with Cloud CMS, supporting seamless integration with major translation services for efficient multilingual workflows.
Score: 1.5867221
|
![]() |
Gitana 3.2 / Guide / Guide / Single Sign On (SSO) / Google GSuiteOptimize your Cloud CMS with this guide on configuring Google GSuite SSO using SAML 2.0 for seamless and secure authentication.
Score: 1.5863894
|
![]() |
Gitana 4.0 / Content Engine / Access Policies / Templates / read-all-content-from-a-single-projectDiscover how to implement a Gitana Access Policy Template for managing project content efficiently.
Score: 1.5765098
|
![]() |
Advanced Content Modeling options (example)Question. If I have the following collections: Categories Products Product_Description_Schemas Each Product is linked to a Category. Each Category is linked to a Product_Description_Schema. The outcome I want to accomplish is that the description schema for Product X I am entering, is defined by the Category it is linked to ( which in turn is defined by the Product_Description_Schema that the Category is linked to ). e.g. Product = Hilton Hotel London, Category = Hotel, Product_Description_Schem
Score: 1.5735868
|
![]() |
Gitana 4.0 / Content Engine / Access Policies / System Policies / project-collaboratorExplore the project-collaborator Gitana System Access Policy, detailing roles and conditions for granting Collaborator and Contributor permissions.
Score: 1.568598
|
![]() |
Gitana 4.0 / Content Engine / Access Policies / Templates / read-all-content-from-multiple-projectsOptimize access to multiple projects with Gitana's Access Policy Template. Manage and consume content easily from various sources.
Score: 1.568598
|
![]() |
Gitana 3.2 / Guide / Guide / Integrations / Amazon Web Services / Amazon Elastic TranscoderOptimize your media with Amazon Elastic Transcoder; scalable, cost-effective cloud transcoding integrated with Cloud CMS for seamless conversion.
Score: 1.5641022
|
![]() |
Gitana 4.0 / Content Engine / Integrations / Amazon Web Services / Amazon Elastic TranscoderOptimize media with Amazon Elastic Transcoder, the scalable, cost-effective solution for seamless cloud-based file conversion compatible with various devices.
Score: 1.5641022
|
![]() |
Gitana 3.2 / Guide / Guide / Branches / ActionsConfigure automated actions for release events with JSON settings. Supports Send Email and Web Hook with variables like releaseId and branchId.
Score: 1.5604843
|
![]() |
Gitana 4.0 / Content Engine / Branches / ActionsOptimize your release management with configurable actions, variables, email, and web hooks. Tailor JSON settings for precise execution.
Score: 1.5604843
|
![]() |
Gitana 4.0 / Content Engine / Access Policies / Templates / manage-content-of-a-type-in-a-folderExplore Gitana's Access Policy Template to manage content by type in specified folders efficiently.
Score: 1.5530105
|
![]() |
Gitana 3.2 / Guide / Guide / SecuritySecure your content with Cloud CMS. Our platform offers robust, multi-layered access controls ensuring only authorized users access your data.
Score: 1.5485454
|
![]() |
Gitana 3.2 / Guide / Guide / Workflow / Workflow HandlersExplore comprehensive workflow handlers, from adding features to sending Slack messages and handling webhooks, for efficient process management.
Score: 1.5376215
|
![]() |
Gitana 4.0 / Content Engine / Workflow / Workflow HandlersExplore comprehensive documentation for workflow handlers like Add Features, Copy Node, Email, and more to optimize your Gitana 4.0 engine tasks efficiently.
Score: 1.5376215
|
![]() |
How does Cloud CMS compare to DIY (do-it-yourself)?Not sure whether to build or buy? Review these points to help guide your selection. Why DIY: exact fit with your technology stack use existing in-house skills and resources build only the features you need able to add new features as required use existing developers for support cost / budget - internal no need for external services to deliver and support product can be a ‘skunk works’ project Why not DIY: Risk (more complex than it looks) time/effort/cost are all easy to under-estimate CMS requi
Score: 1.5365726
|
![]() |
Comparison: Cloud CMS vs DIYNot sure whether to build or buy? Review these points to help guide your selection. Why DIY: exact fit with your technology stack use existing in-house skills and resources build only the features you need able to add new features as required use existing developers for support cost / budget - internal no need for external services to deliver and support product can be a ‘skunk works’ project Why not DIY: Risk (more complex than it looks) time/effort/cost are all easy to under-estimate CMS requi
Score: 1.5365726
|
![]() |
Gitana 3.2 / Guide / Guide / Search / ExamplesExplore the power of Cloud CMS with Elastic Search integration for advanced, flexible content queries using ES DSL.
Score: 1.534106
|