Gitana / 4.0 / User Interface / Projects / Import a Project

Import a Project Backup on same Tenant available to import select the Archive and select Publish. Once the Archive has been set to Published the project is now available in the 'Create a New Project' list. From an external backup To import the backup file on the Target Tenant: Platform Manager Select Vaults Select Primary Vault Archives - Select "+Upload Archives" - Select the Zip file -> Upload Archive Now make Archive available when create a new Project. This is now the same process as describ

Gitana / 3.2 / Guide / Guide / Multifactor Authentication / Providers / Duo Security

Duo Security Cloud CMS supports [https://duo.com/](Duo Security) for Multifactor Authentication. Cloud CMS is not a listed in the Duo Admin Console when "Protecting" an application. Instead, use the "Auth API" type. To configure Duo Security, you will need to supply the following from the Duo "Auth API" "Details": integrationKey secretKey apiHost These values are available from your Duo Security Settings page. Service Descriptor If you're adding an Authenticator via a Service Descriptor: the Des

Gitana / 4.0 / Data Engine / Authentication / Multifactor Authentication / Providers / Duo Security

Duo Security Cloud CMS supports [https://duo.com/](Duo Security) for Multifactor Authentication. Cloud CMS is not a listed in the Duo Admin Console when "Protecting" an application. Instead, use the "Auth API" type. To configure Duo Security, you will need to supply the following from the Duo "Auth API" "Details": integrationKey secretKey apiHost These values are available from your Duo Security Settings page. Service Descriptor If you're adding an Authenticator via a Service Descriptor: the Des

Gitana / 3.2 / Guide / Guide / Features / Locked

Locked QName: f:locked Applied to a node to indicate that it has been locked. A locked node is one that a user has specifically requested the lock for. If the lock is granted, the node will only be editable by the owner of the lock. The lock may only be released by the owner of the lock or a manager/administrator of the branch. It is not necessary to work with the f:locked feature directly. Locking and unlocking are handled through specific API calls that check whether such modifications are all

Gitana / 3.2 / Guide / Guide / Application Server / Services / Locks

Locks The Locks Service is used internally by the Application Server to coordinate access to shared cluster resources. The Locks Service is automatically configured to use Redis when the server is running in "cluster" mode. A configuration block is only required if you do not use environment variables to define redis server configuration. Configuration { "locks": { "enabled": true, "type": "redis", "config": { "url": "" }

Gitana / 4.0 / Data Engine / Aspects / Locked

Locked QName: f:locked Applied to a node to indicate that it has been locked. A locked node is one that a user has specifically requested the lock for. If the lock is granted, the node will only be editable by the owner of the lock. The lock may only be released by the owner of the lock or a manager/administrator of the branch. It is not necessary to work with the f:locked feature directly. Locking and unlocking are handled through specific API calls that check whether such modifications are all

Gitana / 3.2 / Guide / Guide / Actions / Add Feature

Add Feature ID: addFeature Adds a feature to a node. The configuration for this feature is described using JSON Schema like this: { "title": "Add Feature", "properties": { "qname": { "title": "Feature QName", "type": "string" }, "config": { "title": "Feature Configuration", "type": "object" } } } See the examples below for more detail. Example #1 Let's say we want to automatically configure the filename

Gitana / 4.0 / Data Engine / Behaviors / Actions / Add Feature

Add Feature ID: addFeature Adds a feature to a node. The configuration for this feature is described using JSON Schema like this: { "title": "Add Feature", "properties": { "qname": { "title": "Feature QName", "type": "string" }, "config": { "title": "Feature Configuration", "type": "object" } } } See the examples below for more detail. Example #1 Let's say we want to automatically configure the filename

Gitana / 3.2 / Guide / Guide / Narration

Narration This section describes features that are coming in 4.0 With Narration in place, a content instance will automatically have the textual value of a source attachment or a source property sent to an audio processing service to be narrated. The narrated result converts the textual source to audio using text-to-speech. The resulting narration audio file stored back onto the content instance. Any content that you place into Cloud CMS will automatically detect the availability or modification

Gitana / 4.0 / Data Engine / Services / Narration

Narration This section describes features that are coming in 4.0 With Narration in place, a content instance will automatically have the textual value of a source attachment or a source property sent to an audio processing service to be narrated. The narrated result converts the textual source to audio using text-to-speech. The resulting narration audio file stored back onto the content instance. Any content that you place into Cloud CMS will automatically detect the availability or modification

How can I retrieve content for a tree view?

The Cloud CMS API offers a number of convenience API methods that go beyond basic CRUD and bulk content operations. Among these methods are those that allow you to retrieve content from your repository branch in a tree-friendly format. A tree-organized format means that the data comes back in a such a way as to make it easy to load into front-end tree controls. Typical front-end tree controls requires the ability to load a "snapshot" of the tree as a starting point as well as iteratively grow or

Gitana / 3.2 / Guide / Guide / User Interface / Multilingual / Customize Translations UI

Customize Translations UI Cloud CMS allows you to customize UI simply with configurations in your module. Here we will use the following example to demonstrate this feature. For multilingual documents with translations, if you go to the multilingual document's Edit Properties page, the default UI looks like this: In the above screenshot, the Edit Translations button allows you to select a translation of the multilingual document from the dropdown. It's a way to quickly edit the translated docume

Gitana / 4.0 / Forms / Fields / Map Field

Map Field The map field. Properties Title Map Description Field for objects with key/value pairs that share the same schema for values Field Type map Base Field Type array Schema Property Type Default Description items object Schema for array items. maxItems number Maximum number of items. minItems number Minimum number of items. uniqueItems boolean Item values should be unique if true. Options Property Type Default Description animate boolean true Up and down transitions will be animated collap

Gitana / 4.0 / User Interface / User Interface / Multilingual / Customize Translations UI

Customize Translations UI Cloud CMS allows you to customize UI simply with configurations in your module. Here we will use the following example to demonstrate this feature. For multilingual documents with translations, if you go to the multilingual document's Edit Properties page, the default UI looks like this: In the above screenshot, the Edit Translations button allows you to select a translation of the multilingual document from the dropdown. It's a way to quickly edit the translated docume

Gitana / 3.2 / Guide / Guide / Features / Knowledge Recipient

Knowledge Recipient QName: f:knowledge-recipient Used internally to identify that a node has received one or more knowledge properties from a source Knowledge Space. These properties exist on the JSON but may have their values overwritten at any time. The indicated properties are not "mastered" on this node but rather receive their values from elsewhere. Any node that is marked as a f:knowledge-recipient will have at least one a:shares-knowledge association binding it back to the source of the p

Gitana / 4.0 / Data Engine / Aspects / Knowledge Recipient

Knowledge Recipient QName: f:knowledge-recipient Used internally to identify that a node has received one or more knowledge properties from a source Knowledge Space. These properties exist on the JSON but may have their values overwritten at any time. The indicated properties are not "mastered" on this node but rather receive their values from elsewhere. Any node that is marked as a f:knowledge-recipient will have at least one a:shares-knowledge association binding it back to the source of the p

Gitana / 3.2 / Guide / Guide / Actions

Actions Cloud CMS provides an Action framework that lets you kick off Actions that perform content operations on your behalf. Actions are units of work that are typically fired off as a result of an event handler or listener. For example, you might register an Action that triggers when a piece of content is updated or when a workflow task transitions. The Action might do something like Send an Email or Fire off a Web Hook. The Cloud CMS Action framework aspires to provide complete units of work

Gitana / 3.2 / Guide / Guide / Actions / Send a Slack Message

Send a Slack Message ID: slackMessage Sends a Slack Message to a configured channel. For information on how to connect Slack and Cloud CMS, see Slack Integration. Configuration Property Type Required Default Description url text true The webhook URL provided by slack that will send messages to the configured channel. message text false Markdown message template of message that will be sent when action is fired. Required if template node is not provided. message text false Markdown message templa

Gitana / 4.0 / Data Engine / Behaviors / Actions

Actions Cloud CMS provides an Action framework that lets you kick off Actions that perform content operations on your behalf. Actions are units of work that are typically fired off as a result of an event handler or listener. For example, you might register an Action that triggers when a piece of content is updated or when a workflow task transitions. The Action might do something like Send an Email or Fire off a Web Hook. The Cloud CMS Action framework aspires to provide complete units of work

Gitana / 4.0 / Data Engine / Behaviors / Actions / Send a Slack Message

Send a Slack Message ID: slackMessage Sends a Slack Message to a configured channel. For information on how to connect Slack and Cloud CMS, see Slack Integration. Configuration Property Type Required Default Description url text true The webhook URL provided by slack that will send messages to the configured channel. message text false Markdown message template of message that will be sent when action is fired. Required if template node is not provided. message text false Markdown message templa

Gitana / 3.2 / Guide / Guide / Branches / Actions

Actions You can optionally configure Actions that execute when a release goes live. Some actions support variables. The following variables are always available: release - a JSON object of the release along with all metadata about the release releaseId - the ID of the release object branchId - the ID of the release branch snapshot - the ID of the snapshot that was generated after merge The following Actions are supported: Send Email Fire Web Hook For each action, you need to provide a configurat

Gitana / 4.0 / Data Engine / Branches / Actions

Actions You can optionally configure Actions that execute when a release goes live. Some actions support variables. The following variables are always available: release - a JSON object of the release along with all metadata about the release releaseId - the ID of the release object branchId - the ID of the release branch snapshot - the ID of the snapshot that was generated after merge The following Actions are supported: Send Email Fire Web Hook For each action, you need to provide a configurat

Gitana / 3.2 / Guide / Guide / API / System Metadata

System Metadata Cloud CMS automatically tracks system metadata for all of the objects that you create within it. System metadata consists of non-data values that describe things like who created an object and when it was modified. System Metadata This system metadata is tracked under the special _system key at the root of your objects. This system metadata is read-only in so far as it is tracked by Cloud CMS automatically. It is available for any object returned by any of the Cloud CMS APIs by s

Gitana / 3.2 / Guide / Guide / UI Developers Guide / Templates / List Items

List Items List Items exist in multiple places in CloudCMS UI. They consist of an icon on the left and some detailed descriptions on the right. Below is an example of some list items configured with the default template. You can customize the description on the right using Templates. The Default Template

{{title data}}

Gitana / 4.0 / Developers / User Interface Customization / Templates / List Items

List Items List Items exist in multiple places in CloudCMS UI. They consist of an icon on the left and some detailed descriptions on the right. Below is an example of some list items configured with the default template. You can customize the description on the right using Templates. The Default Template

{{title data}}