Found 937 results for "conditions or"
The search executed in 0.001595793 seconds. That's fast.
Gitana / 3.2 / Guide / Guide / Getting StartedGetting Started Welcome to the Cloud CMS Documentation center. Cloud CMS is an API-first content management system that provides everything you need on the back end to power web sites and mobile applications. Cloud CMS makes it easy for your business users to create, manage and publish amazing content to your users! You are reading the Getting Started guide. To learn more about Cloud CMS and what it does, select from the links provided below or use the tree on the left-hand side. We offer severa
Score: 0.36805704
|
|
Gitana / 3.2 / Guide / Guide / Application Server / Tags / @query@query Queries for nodes and makes those nodes available to the template. Parameters parameter required description type the type of node to query for (definition QName) sort the field to sort on sortDirection the direction to sort in (either 1 for ascending or -1 for descending) limit the number of records to return fields comma separated list of property names to include in query results skip a position to skip ahead to in the record set scope if "page", then only relatives related to the curr
Score: 0.36805704
|
|
Gitana / 3.2 / Guide / Guide / Docker / Maintenance / Container HooksContainer Hooks This page describes the configuration of HTTP hooks that can be wired into your container orchestration framework to facilitate container lifecycle events (such as shutdown). Lifecycle Hooks Your container orchestration framework likely supports the ability to signal a running API container when one of the following occurs: A container has finished starting up. A container is about to be shut down. In the Kubernetes world, there are two lifecycle hooks (postStart and preStop). Th
Score: 0.36805704
|
|
Gitana / 3.2 / Guide / Guide / Application Server / Authentication / Adapters / JWTJWT The JWT request adapter is similar to the default adapter in that it lets you pull a JWT token from either a named header or a cookie. JWT stands for JSON Web Token. JSON Web Tokens are an open, industry standard RFC 7519 method for representing claims securely between two parties. You can read more about them at the official JWT web site. Configuration Here are all of the properties that may be configured: { "adapters": { "{adapterId}": { "type": "jwt", "
Score: 0.36805704
|
|
Gitana / 4.0 / Developers / Application Server / Tags / @query@query Queries for nodes and makes those nodes available to the template. Parameters parameter required description type the type of node to query for (definition QName) sort the field to sort on sortDirection the direction to sort in (either 1 for ascending or -1 for descending) limit the number of records to return fields comma separated list of property names to include in query results skip a position to skip ahead to in the record set scope if "page", then only relatives related to the curr
Score: 0.36805704
|
|
Gitana / 4.0 / Developers / Application Server / Authentication / Adapters / JWTJWT The JWT request adapter is similar to the default adapter in that it lets you pull a JWT token from either a named header or a cookie. JWT stands for JSON Web Token. JSON Web Tokens are an open, industry standard RFC 7519 method for representing claims securely between two parties. You can read more about them at [jwt.io](the official JWT web site). Configuration Here are all of the properties that may be configured: { "adapters": { "{adapterId}": { "type": "jwt",
Score: 0.36805704
|
|
How does multi-tenancy work?How does multi-tenancy work? ie I want to have multiple companies with sub-groups of users in each company - to follow, how would we customize the interface for each company? There are two good ways to achieve multi-tenancy with Cloud CMS. - One is to use multiple "projects" - i.e. one per customer. Each project has it's own domain of users and groups, as well as it's own content definitions, instances and ACLs. As such, you can use each project to store the content on a per-client basis. You ca
Score: 0.36805704
|
|
Automatic Extraction from AttachmentsWhen you upload files into Cloud CMS all kinds of interesting things happen. For example, Cloud CMS automatically indexes your files for full-text search. All of the textual content is discovered and made available so your editorial teams can instantly search and find things after uploading. Did you know that Cloud CMS can also automatically extract metadata about uploaded files and make that information available? This is done via the Cloud CMS f:extractable feature. When you upload files, Clou
Score: 0.36805704
|
|
Gitana / 3.2 / Guide / Guide / TreeTree Content that is organized into folders can be retrieved using the Tree API. The Tree API lets you pull back an entire path-based folder and file structure of content within a single API call. The API call lets you specify a root node, a maximum depth to traverse down the path structure, paths that should be automatically expanded and query terms for filtering of root nodes. The Tree API is deal to support a variety of cases including: retrieval of multiple deeply-nested paths within a singl
Score: 0.36802325
|
|
Gitana / 4.0 / Data Engine / Discovery / TreeTree Content that is organized into folders can be retrieved using the Tree API. The Tree API lets you pull back an entire path-based folder and file structure of content within a single API call. The API call lets you specify a root node, a maximum depth to traverse down the path structure, paths that should be automatically expanded and query terms for filtering of root nodes. The Tree API is deal to support a variety of cases including: retrieval of multiple deeply-nested paths within a singl
Score: 0.36802325
|
|
Gitana / 3.2 / Guide / Guide / Docker / Maintenance / Datastore DeletionDatastore Deletion This page describes the process for manually removing MongoDB databases when a Cloud CMS datastore is deleted. When you delete a datastore within Cloud CMS, the datastore itself is marked as deleted. It will not longer be available for usage within Cloud CMS. That said, the MongoDB database itself will remain on disk. It is not automatically deleted. The MongoDB administrator will need to remove this database as a separate action. This provides a separation of concerns. Cloud
Score: 0.36640847
|
|
Careers - GitanaCareers - 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 curate con
Score: 0.36640847
|
|
Gitana / 3.2 / Guide / Guide / Binary Files / Azure Binary StorageAzure Binary Storage Cloud CMS supports Microsoft Azure's Blob Storage service by allowing it to serve as a backend provider for the storage of binary files within Cloud CMS. When files are uploaded to Cloud CMS, they are parsed and worked with and then eventually sent over to the Azure Blob Storage Service for persistence. When users seek to download those binary files, they are streamed back from Azure. Depending on how you elect to configure your binary storage providers, Cloud CMS may employ
Score: 0.3656564
|
|
Gitana / 3.2 / Guide / Guide / Binary Files / IBM COS Binary StorageIBM COS Binary Storage Cloud CMS supports IBM Cloud Object Storage (COS) by allowing it to serve as a backend provider for the storage of binary files within Cloud CMS. When files are uploaded to Cloud CMS, they are parsed and worked with and then eventually sent over to IBM COS for persistence. When users seek to download those binary files, they are streamed back from IBM COS. Depending on how you elect to configure your binary storage providers, Cloud CMS may employ an TTL cache in between to
Score: 0.3656564
|
|
Gitana / 3.2 / Guide / Guide / Binary Files / S3 Binary StorageS3 Binary Storage Cloud CMS supports Amazon S3 (Simple Storage Service) by allowing it to serve as a backend provider for the storage of binary files within Cloud CMS. When files are uploaded to Cloud CMS, they are parsed and worked with and then eventually sent over to Amazon S3 for persistence. When users seek to download those binary files, they are streamed back from S3. Depending on how you elect to configure your binary storage providers, Cloud CMS may employ an TTL cache in between to avo
Score: 0.3656564
|
|
Gitana / 3.2 / Guide / Guide / Features / Knowledge RecipientKnowledge 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
Score: 0.3656564
|
|
Gitana / 3.2 / Guide / Guide / Getting Started / Instant PreviewInstant Preview All of your content changes can be instantly previewed. Cloud CMS removes the need for IT to set up additional servers or deploy changes to content. Instead, you simply work on your content and click to preview the content in real-time. The reason why this is possible is because Workspaces are layered. When you create a workspace, your new workspace is connected to a parent workspace at some point in time in the past. All of your changes are automatically layered on top of the pa
Score: 0.3656564
|
|
Gitana / 3.2 / Guide / Guide / Getting Started / WorkspacesWorkspaces Everything you do with content is done within a workspace. When you create content or modify content definitions, it is all done inside of a workspace. Workspaces are isolated from one another so that different teams can make changes to things without stepping on each other's toes. By default, there is a master workspace where everything happens. You can create new workspaces at any time. When you create a workspace, Cloud CMS remembers the point in time when the new workspace was cre
Score: 0.3656564
|
|
Gitana / 3.2 / Guide / Guide / UI Developers Guide / Contexts / documents-list-item-actionsdocuments-list-item-actions [ { "evaluator": "document-is-favorite", "config": { "documents-list-item-actions": [ { "key": "favorite", "iconClass": "fa fa-star", "action": "remove-from-favorites", "order": 9000 } ] } }, { "config": { "documents-list-item-actions": [ { "key": "edit-document", "link": "/#/projects/{{project._doc}}/documents/{{document._doc}}/properties",
Score: 0.3656564
|
|
Gitana / 4.0 / Developers / User Interface Customization / Contexts / documents-list-item-actionsdocuments-list-item-actions [ { "evaluator": "document-is-favorite", "config": { "documents-list-item-actions": [ { "key": "favorite", "iconClass": "fa fa-star", "action": "remove-from-favorites", "order": 9000 } ] } }, { "config": { "documents-list-item-actions": [ { "key": "edit-document", "link": "/#/projects/{{project._doc}}/documents/{{document._doc}}/properties",
Score: 0.3656564
|
|
Gitana / 4.0 / Data Engine / Aspects / Knowledge RecipientKnowledge 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
Score: 0.3656564
|
|
Gitana / 4.0 / Data Engine / Platform / Binary Files / Azure Binary StorageAzure Binary Storage Cloud CMS supports Microsoft Azure's Blob Storage service by allowing it to serve as a backend provider for the storage of binary files within Cloud CMS. When files are uploaded to Cloud CMS, they are parsed and worked with and then eventually sent over to the Azure Blob Storage Service for persistence. When users seek to download those binary files, they are streamed back from Azure. Depending on how you elect to configure your binary storage providers, Cloud CMS may employ
Score: 0.3656564
|
|
Gitana / 4.0 / Data Engine / Platform / Binary Files / IBM COS Binary StorageIBM COS Binary Storage Cloud CMS supports IBM Cloud Object Storage (COS) by allowing it to serve as a backend provider for the storage of binary files within Cloud CMS. When files are uploaded to Cloud CMS, they are parsed and worked with and then eventually sent over to IBM COS for persistence. When users seek to download those binary files, they are streamed back from IBM COS. Depending on how you elect to configure your binary storage providers, Cloud CMS may employ an TTL cache in between to
Score: 0.3656564
|
|
Gitana / 4.0 / Data Engine / Platform / Binary Files / S3 Binary StorageS3 Binary Storage Cloud CMS supports Amazon S3 (Simple Storage Service) by allowing it to serve as a backend provider for the storage of binary files within Cloud CMS. When files are uploaded to Cloud CMS, they are parsed and worked with and then eventually sent over to Amazon S3 for persistence. When users seek to download those binary files, they are streamed back from S3. Depending on how you elect to configure your binary storage providers, Cloud CMS may employ an TTL cache in between to avo
Score: 0.3656564
|
|
Gitana / 4.0 / Getting Started / Working with Content / BranchesBranches Everything you do with content is done within a workspace. When you create content or modify content definitions, it is all done inside of a workspace. Workspaces are isolated from one another so that different teams can make changes to things without stepping on each other's toes. By default, there is a master workspace where everything happens. You can create new workspaces at any time. When you create a workspace, Cloud CMS remembers the point in time when the new workspace was creat
Score: 0.3656564
|