Found 46 results for "manual topics attachments"

The search executed in 0.0 seconds


Files Antivirus Scanning Attachments Binaries

Score: 19.746502

Files / Attachments

Attachments Cloud CMS provides support for the storage and retrieval of binary assets. These assets are stored as attachments on an object. Unlike some CMS systems which start with the binary asset, Cloud CMS considers all of your objects and content to be JSON documents. The JSON document then has N number of binary BLOBs attached to it. Each attachment has a unique name and retains information such as mimetype, filename and content length. The following kinds of objects support attachments: Co

Score: 18.539164

Content Modeling / Attachment Properties

Attachment Properties Cloud CMS provides support for properties that auto-manage the creation, update and deletion of binary attachments for a node. These are known as "attachment properties". They provide an easy way for editorial users to manage binary attachments from within a form. Attachment properties provide the following benefits: They provide an easy form-driven way for editorial users to upload and manage named attachments of a node. They automatically reflect important attachment info

Score: 10.812238

Mitigating the OWASP Top 10

An explanation of how Cloud CMS addresses each of the Top 10 OWASP topics: Mitigating-the-OWASP-Top-10.pdf

Score: 7.5173526

Actions / Start Workflow

Start Workflow ID: startWorkflow Starts a workflow with the given node placed into the payload. Configuration Property Type Required Default Description model text true The ID of the workflow model to be used. swimlanes object false Identifies principals to be assigned into workflow swimlanes. The structure is: { "swimlane1": ["domainId1/principalId1"], "swimlane2": ["domainId2/principalId2"] } runtime object false Allows for manual specification of runtime properties including applica

Score: 6.7646923

User Interface / Locking

Locking Cloud CMS locking is a "data lock" approach which is a transactional lock is taken out when the write of multiple documents begins. This is a transactional lock in the sense that it blocks other write operations against those documents and fails entirely with rollback if any of the documents fail individually. We have transactional writes for multiple documents. We have a changeset-driven versioning model where each transaction writes onto it's own changeset. N number of documents may wr

Score: 6.611619

Forms / Fields / Attachment Picker

Attachment Picker ID: attachment-picker The attachment-picker field type renders a modal picker for an attachment. Definition configuration: { "type": "object", "_attachment": { "id": "default" } } Form configuration: { "type": "attachment-picker" } Create a Document with an Attachment Define a content model with an attachment-picker field: Preview content model: Create a content instance: Then the document will be created, and since the attachment's id is "default", the

Score: 5.971515

Application Server / Services / Broadcast

Broadcast The Broadcast service is responsible for relaying messages to members of the application server cluster. It provides an essential publish and subscription service so that application server members can broadcast messages, receive messages and subscribe to topics and events that occur throughout the system. Essential Configuration { "broadcast": { "enabled": , "type": "", "config": { ...configuration } } } There are two

Score: 5.9021983

Files / Binaries

Binaries Cloud CMS supports the storage of binary files into one of three possible storage locations: MongoDB GridFS Amazon S3 Local file system Binary files are stored using directory structures (key prefixes) that allow for fast object retrieval from any of these systems. These storage paths are optimized for retrieval and write speed and are subject to implementation changes. The actual API retrieval of these files, on the other hand, utilizes a simple filename convention. You simply retrieve

Score: 5.0306387

Features / Previewable

Previewable QName: f:previewable Automates the creation and updating of "preview" attachments for one or more attachments on this node. Preview attachments are secondary binary attachments that are the result of one or more transformation operations to the original attachment. As an example, you might apply the f:previewable feature to a node that holds a PDF. The preview configuration lets you split the PDF into multiple pages and store snapshots of those pages as image/jpeg attachments on the

Score: 4.9581957

Deployment / Deployment Handlers / Amazon S3 Deployment Handler

Amazon S3 Deployment Handler Handles the deployment of one or more Deployment Packages to an Amazon S3 bucket. The Amazon S3 bucket is described by: accessKey secretKey region bucketName The contents of the Deployment Packages will be deployed sequentially to the target location. If any of the content within the Deployment Packages fails to copy, it will simply be skipped. Other content objects will be allowed to proceed unabated. Nodes are written to disk like this: {deploymentPath}/{nodeId}/no

Score: 4.8738756

Deployment / Deployment Handlers / File System Deployment Handler

File System Deployment Handler Handles the deployment of one or more Deployment Packages to a file system. A file system is described by a local path on disk, such as: /www/files /data /Users/joesmith/files These paths, in turn, my describe mounts that are ephemeral or non-ephemeral (such as Amazon EBS mounted drives or shared network storage). The contents of the Deployment Packages will be deployed sequentially to the target location. If any of the content within the Deployment Packages fails

Score: 4.850227

Deployment / Deployment Handlers / FTP Deployment Handler

FTP Deployment Handler Handles the deployment of one or more Deployment Packages to an SFTP or FTP server. The remote S/FTP server is described by a URL, username and password. The contents of the Deployment Packages will be deployed sequentially to the target location. If any of the content within the Deployment Packages fails to copy, it will simply be skipped. Other content objects will be allowed to proceed unabated. Nodes are written to disk like this: {deploymentPath}/{nodeId}/node.json No

Score: 4.850227

Features / Indexable

Indexable QName: f:indexable Informs a node of how it should be indexed. Cloud CMS maintains multiple indexes including a search index, a database index and special indexes for things like path-based retrieval. By default, all n:node instances have the f:indexable feature applied to them. The default behavior is for search to be enabled and for search-indexes to be updated synchronously upon a write. Nodes that are indexed for search will take a little extra time on write (create or update) sinc

Score: 4.2310996

Features / Watermarkable

Watermarkable Cloud CMS lets you configure your content so that watermarks are automatically applied when content is created and updated. This lets you systematize the watermarking of your images to ensure consistency across your project. You can maintain a single watermark or multiple watermarks and divide up how they are applied on both a per-content instance and per-content type basis. To start, you simply upload a watermark image to Cloud CMS. Typically, watermark images are image/jpeg or im

Score: 4.0291276

Proxy API calls

Whenever a resulting URL looks something like: It works great as an API URL but not necessarily as one that can be resolved by the end user's browser. In a typical Node.js-based architecture, you have the User’s browser Node.js application server Cloud CMS backend API The URL generated above is the URL directly to the resource in the backend API. What you really would pre

Score: 3.8960876

User Interface / Create/Edit Content

Create/Edit Content In a Project you can find your content a number of ways: Content (left Nav) - Content listed under Content Types Folders (left Nav) - Folder/File view of the content Search (left Nav for a detailed search or top right for a keyword search) Viewing a Content item With any of the options above, to find or list the content, click on the 'title' of the content item to open the 'Document Overview': Note: your tenant may be configured such that the options available in the left nav

Score: 3.836278

Features / Thumbnailable

Thumbnailable QName: f:thumbnailable Configures a node to automatically generate thumbnails for the node content or attachments. With this feature applied, one or more thumbnail images will be generated based on the node's JSON or attachment content. These thumbnails can be of various sizes and are automatically generated when the node's content is created, updated or deleted or its relevant attachment is updated. Thumbnail generation is always synchronous. Thumbnails are generated when the node

Score: 3.6673813

Single Sign On (SSO) / Keycloak

Keycloak This page provides an example of how to configure Cloud CMS Single Sign On (SSO) for JBoss KeyCloak. Keycloak is an open-source Identity and Access Management product provided by JBoss/RedHat. Keycloak plays the role of an Identity Provider that speaks SAML 2.0 and/or JWT. Cloud CMS integrates via either of these mechanism and can therefore integrate to Keycloak straight away as an identity provider. Cloud CMS provides Single Sign On (SSO) Enterprise support for a variety of Identity Pr

Score: 3.6425714

Features / AWS Dominant Language

AWS Dominant Language QName: f:aws-dominant-language Empowers a node to automatically determine the dominant language of the node's properties and attachments. The dominant language is specified by the language portion of a locale key (such as en for English or es for Spanish). To determine the dominant language, the textual composition of the node is sent to the AWS Comprehend Service for processing. Once the dominant language is determined, the f:locale feature is applied to the node along wit

Score: 3.5127292

Features / AWS Sentiment

AWS Sentiment QName: f:aws-sentiment Empowers a node to automatically determine the sentiment of content that it contains. This takes into account the node's properties and any binary attachments it may contain. The sentiment is the populated onto a property of the node. By default and unless overwritten, this will default to sentiment. This features uses Amazon's Comprehend Service to perform Natural Language processing over your node's content. To learn about Amazon's Sentiment analysis, see:

Score: 3.5127292


Reports All of the objects that you place into Cloud CMS can be operated against to produce exports that consist of consolidated or reported information. You can use this capability to generate reports in CSV (comma-separated value) format as well as merged PDFs and ZIP archives. Exports are generated from collections of objects. These objects might be collected by hand or they might consist of results sets from a document list, search page or report record set. The Cloud CMS user interface prov

Score: 3.3626053

Bulk Import

Bulk Import Cloud CMS provides a bulk import tool that makes it easy to load content into Cloud CMS from a variety of external file formats and data sources. The bulk import tool ingests this data and writes it into a Cloud CMS branch within a single transaction so that you don't suffer from partial imports due to a failure along the way. The Cloud CMS bulk import tool is designed to help you migrate existing content into Cloud CMS. This may include desktop files or structured data from legacy c

Score: 3.3459592

Features / Multilingual

Multilingual QName: f:multilingual When applied to a node, this indicates that you wish to have the contents of this node support multilingual behavior and translated content. This node then serves as the "master node" for translation support. Master nodes have a:has_translation associations to translation nodes that hold copies of the content (JSON and any attachments) in the target locale. Marking a node as f:multilingual does not automatically produce translations for you. However, once marke

Score: 3.2296386

Forms / Fields / File Picker

File Picker ID: file-picker The file-picker field type renders a modal picker for a file. This uses the File Folder service within Cloud CMS to let you browse through folder-based navigation. A breadcrumb is rendered at the top to help users step through the folder hierarchy. Sample configuration: { "type": "file-picker" } As with the node picker, the file picker should be modeled on top of either an object or an array field. The former is used for selection of a single node whereas the latt

Score: 3.157645