Found 563 results for "ui-dev configuration"
The search executed in 0.001424678 seconds. That's fast.
Migrating Binary files to S3By default, on-premise installations of Cloud CMS are configured with a GridFS (`gridfs`) Binary Storage Provider. This allows Cloud CMS to read and write binary files (such as attachments) to GridFS. At some point, as your installation grows, you may want change this. Suppose you wanted to move your binary files into S3 and use S3 as a Binary Storage Provider for Cloud CMS. To do so, we recommend the following steps: 1. Make a backup of your Cloud CMS database. 2. Create an S3 bucket and IAM us
Score: 0.70333767
|
|
Gitana / 3.2 / Guide / Guide / IntegrationsIntegrations Cloud CMS allows you to connect to external cloud-based services for purposes of things like: external data storage for binary data auto-record updates to dns servers event handling to cloud notification handlers To configure these services, you simply create a service descriptor via the main interface: Service descriptors are declared once and can be re-used multiple times within your platform, across different projects and applications. Service descriptors are encrypted on the ser
Score: 0.6986328
|
|
Gitana / 3.2 / Guide / Guide / Features / LockedLocked 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
Score: 0.6986328
|
|
Gitana / 3.2 / Guide / Guide / Features / Propagates AuthoritiesPropagates Authorities QName: f:propagates-authorities Flags an association as one that propagates inherited authorities from the source to the target. If a parent has authorities assigned to it, those authorities are propagated to the children as masked a:hasRole associations. These associations have inherited set to true and inheritsAssociation set to the association ID being masked. Cloud CMS uses this feature to model propagation of authorities in a containment model within the graph. When y
Score: 0.6986328
|
|
Gitana / 3.2 / Guide / Guide / Access Policies / Conditions / AndAnd This section describes features that are coming in 4.0 The and condition lets you perform a logical AND operation across multiple sub-conditions. Configuration { "type": "and", "config": { "conditions": [ ... subconditions ] } } Sample #1 This policy document allows a principal to read content from the /products so long as it is of type my:article. { "title": "My Sample Policy", "statements": [{ "action": "grant", "roles": ["co
Score: 0.6986328
|
|
Gitana / 3.2 / Guide / Guide / Access Policies / Conditions / BranchBranch This section describes features that are coming in 4.0 The branch condition allows you to constrain a policy statement so that it applies to nodes and/or associations that are on a matching branch. The branch can be matched using its ID (_doc), title or alias. This condition supports regular expressions, allowing you to focus in on a single value or wildcard expressions for matches. Configuration To match a branch by ID: { "type": "branch", "config": { "id": "{value regex}
Score: 0.6986328
|
|
Gitana / 4.0 / Data Engine / Aspects / LockedLocked 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
Score: 0.6986328
|
|
Gitana / 4.0 / Data Engine / Aspects / Propagates AuthoritiesPropagates Authorities QName: f:propagates-authorities Flags an association as one that propagates inherited authorities from the source to the target. If a parent has authorities assigned to it, those authorities are propagated to the children as masked a:hasRole associations. These associations have inherited set to true and inheritsAssociation set to the association ID being masked. Cloud CMS uses this feature to model propagation of authorities in a containment model within the graph. When y
Score: 0.6986328
|
|
Gitana / 4.0 / Data Engine / Integrations / OverviewIntegrations Cloud CMS allows you to connect to external cloud-based services for purposes of things like: external data storage for binary data auto-record updates to dns servers event handling to cloud notification handlers To configure these services, you simply create a service descriptor via the main interface: Service descriptors are declared once and can be re-used multiple times within your platform, across different projects and applications. Service descriptors are encrypted on the ser
Score: 0.6986328
|
|
Gitana / 4.0 / Data Engine / Security / Access Policies / Conditions / AndAnd This section describes features that are coming in 4.0 The and condition lets you perform a logical AND operation across multiple sub-conditions. Configuration { "type": "and", "config": { "conditions": [ ... subconditions ] } } Sample #1 This policy document allows a principal to read content from the /products so long as it is of type my:article. { "title": "My Sample Policy", "statements": [{ "action": "grant", "roles": ["co
Score: 0.6986328
|
|
Gitana / 4.0 / Data Engine / Security / Access Policies / Conditions / BranchBranch This section describes features that are coming in 4.0 The branch condition allows you to constrain a policy statement so that it applies to nodes and/or associations that are on a matching branch. The branch can be matched using its ID (_doc), title or alias. This condition supports regular expressions, allowing you to focus in on a single value or wildcard expressions for matches. Configuration To match a branch by ID: { "type": "branch", "config": { "id": "{value regex}
Score: 0.6986328
|
|
Gitana / 3.2 / Guide / Guide / Features / Dublin CoreDublin Core QName: f:dublincore Applies metadata properties to your definition to enable it to support the Dublin Core Metadata Initiative standard. For information on Dublin Core, please visit: http://dublincore.org/. The feature is defined as shown here: { "_qname": "f:dublincore", "_type": "d:feature", "type": "object", "title": "Dublin Core", "properties": { "dublincore": { "type": "object", "title": "Dublin Core Properties", "p
Score: 0.6914487
|
|
Gitana / 3.2 / Guide / Guide / Access Policies / Conditions / Data StoreData Store This section describes features that are coming in 4.0 The datastore condition allows you to constrain a policy statement so that it applies to datastores and/or objects within a datastore. The datastore can be matched using its Type, ID and/or a title. This condition supports regular expressions, allowing you to focus in on a single value or wildcard expressions for matches. Configuration To match a changeset by Type: { "type": "datastore", "config": { "typeId": "{val
Score: 0.6914487
|
|
Gitana / 3.2 / Guide / Guide / Access Policies / Conditions / FeatureFeature This section describes features that are coming in 4.0 The feature condition allows you to constrain a policy statement so that it applies to content nodes that have a particular feature. Configuration { "type": "feature", "config": { "qname": "{qname regex}" } } Samples This policy grants the Consumer role to all content with feature f:thumbnailable: { "title": "My Sample Policy", "statements": [{ "action": "grant", "roles": ["consumer"],
Score: 0.6914487
|
|
Gitana / 4.0 / Data Engine / Aspects / Dublin CoreDublin Core QName: f:dublincore Applies metadata properties to your definition to enable it to support the Dublin Core Metadata Initiative standard. For information on Dublin Core, please visit: http://dublincore.org/. The feature is defined as shown here: { "_qname": "f:dublincore", "_type": "d:feature", "type": "object", "title": "Dublin Core", "properties": { "dublincore": { "type": "object", "title": "Dublin Core Properties", "p
Score: 0.6914487
|
|
Gitana / 4.0 / Data Engine / Security / Access Policies / Conditions / Data StoreData Store This section describes features that are coming in 4.0 The datastore condition allows you to constrain a policy statement so that it applies to datastores and/or objects within a datastore. The datastore can be matched using its Type, ID and/or a title. This condition supports regular expressions, allowing you to focus in on a single value or wildcard expressions for matches. Configuration To match a changeset by Type: { "type": "datastore", "config": { "typeId": "{val
Score: 0.6914487
|
|
Gitana / 4.0 / Data Engine / Security / Access Policies / Conditions / FeatureFeature This section describes features that are coming in 4.0 The feature condition allows you to constrain a policy statement so that it applies to content nodes that have a particular feature. Configuration { "type": "feature", "config": { "qname": "{qname regex}" } } Samples This policy grants the Consumer role to all content with feature f:thumbnailable: { "title": "My Sample Policy", "statements": [{ "action": "grant", "roles": ["consumer"],
Score: 0.6914487
|
|
Product Releases - GitanaProduct Releases - Gitana Status Releases Registry Blog Cloud CMS Platform Content Management Create, Approve and Publish quality content to production on-time. Easy editorial and workflow tools let your best work reach your customers. Enterprise Data Engine Manage, collaborate, search and distribute your highly-structured data across branches, versions and workflow-driven lifecycle. Automate Automate your content creation and approval flows while taking advantage of AI services to enhance and c
Score: 0.69104844
|
|
Gitana / 3.2 / Guide / Guide / Docker / Maintenance / UpgradesUpgrades This document provides technical guidance for upgrades. Upgrade to Cloud CMS Version 3.2 The Elastic Search version in this release has been updated from 1.7.1 to 6.2.4. Steps to follow to set up Docker 3.2: Download the Docker release 3.2 here. Download the Zip or Tar file of Elastic Search 6.2.4 here and then Unzip the package. Unzip the Docker release package, Create a new folder and paste the kit you use from the package. You can also replace your existing kit with the new release's
Score: 0.69044363
|
|
Gitana / 4.0 / Self Managed / Maintenance / UpgradesUpgrades This document provides technical guidance for upgrades. Upgrade to Cloud CMS Version 3.2 The Elastic Search version in this release has been updated from 1.7.1 to 6.2.4. Steps to follow to set up Docker 3.2: Download the Docker release 3.2 here. Download the Zip or Tar file of Elastic Search 6.2.4 here and then Unzip the package. Unzip the Docker release package, Create a new folder and paste the kit you use from the package. You can also replace your existing kit with the new release's
Score: 0.69044363
|
|
Gitana / 3.2 / Guide / Guide / Features / AWS TranscodeAWS Transcode QName: f:aws-transcode Applying this feature allows a piece of content's default attachment to be automatically transcoded from one filetype to one or more other filetypes. This is done to the specification of custom or AWS predefined presets. Once a transcoding is finished, an array of S3 paths for the transcoded files will be saved back to the content. To use this feature, you will need to have an AWS account with S3 and Amazon Elastic Transcoder setup. You will also need to conf
Score: 0.6889254
|
|
Gitana / 4.0 / Data Engine / Aspects / AWS TranscodeAWS Transcode QName: f:aws-transcode Applying this feature allows a piece of content's default attachment to be automatically transcoded from one filetype to one or more other filetypes. This is done to the specification of custom or AWS predefined presets. Once a transcoding is finished, an array of S3 paths for the transcoded files will be saved back to the content. To use this feature, you will need to have an AWS account with S3 and Amazon Elastic Transcoder setup. You will also need to conf
Score: 0.6889254
|
|
Gitana / 3.2 / Guide / Guide / Applications / Public ServicesPublic Services Cloud CMS provides a special set of application services methods that provide convenience functions for your front-end mobile or web applications to accomplish things like user registration, password resets and more. Technically speaking, everything that you can do with these convenience functions can be done using the Cloud CMS API in other ways, however doing so is often multi-step and involves lots of interactions. The convenience methods make this easier by letting you pre-wi
Score: 0.68441075
|
|
Gitana / 3.2 / Guide / Guide / Integrations / SlackSlack Slack is a powerful instant messaging and team collaboration tool, and you can easily integrate it with Cloud CMS to get real-time updates about your content. Setting up your Bot To get notifications from Cloud CMS, you will need to set up a bot user in your Slack platform. Go to https://api.slack.com/apps and create a new app. Assign it to your team's workspace Under "Add features and functionality", click "Incoming Webhooks", and enable this. Click the "Add New Webhook to Workspace" butt
Score: 0.68441075
|
|
Gitana / 3.2 / Guide / Guide / User Interface / Multilingual / Customize Translations UICustomize 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
Score: 0.68441075
|