Found 157 results for "api api policies api policies attachment"

The search executed in 0.0 seconds

API Keys

API Keys For information on API Keys, please visit the Cloud CMS - API Keys Developer Page.

Score: 102.7168

API

API The Cloud CMS API consists of an HTTP/HTTPS endpoint that uses OAuth 2.0 authentication. It supports both REST concepts and asynchronous data operations. You can access this API using any of our drivers as well as curl or any HTTP client library. Our API provides functionality that covers all aspects of content production, publishing and presentation. 100% of the functionality of Cloud CMS is accessible from the API, including: Content Models, Creation and Editing Workflow, Scheduled Publish

Score: 91.99585

Policies

Policies Policies can be used to run custom code or fire off actions when an event, such as creating a content item or associating a content item into the content graph, occurs. Cloud CMS provides a wide array of policies that you can hook your custom logic into. By default, Cloud CMS provides sensible and useful content policy handlers to manage the lifecycle of you content. You can wire in new policy handlers. Policy handlers include scripts and rules. The following types of policies are avail

Score: 79.97879

Docker / Configuration / API Server

API Server The Cloud CMS API Server is a Java application that launches inside of a Java Servlet Container. The Java application surfaces a REST API as well as backend services and DAOs to support connectivity to Mongo DB, Elastic Search and a slew of Amazon services including S3, SNS, SQS, Route 53, Cloud Front and more. Properties File Cloud CMS is primarily configured via a properties file that is auto-detected and loaded when the underlying Spring Framework starts up. This properties file is

Score: 56.68102

Policies / Attachment Policies

Attachment Policies Attachment policies provide places where you can hook in behaviors that trigger when attachments are read, created, updated or deleted against a node. The following policies are available: Policy QName Description p:beforeReadAttachment Raised before a node's attachment is read p:afterReadAttachment Raised after a node's attachment is read p:beforeCreateUpdateAttachment Raised before an node's attachment is added to a node (either created or updated) p:afterCreateUpdateAttach

Score: 42.590744

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

Score: 33.64998

Policies / Node Policies

Node Policies Node policies provide places where you can hook in behaviors that trigger when nodes are created, updated or deleted within the graph. Nodes may either be entities or associations. This provides an ideal way to plug in your custom behaviors for any definition or content instance within your content graph. The following policies are available: Policy QName Description p:beforeCreateNode Raised before a piece of content is created p:afterCreateNode Raised after a piece of content has

Score: 32.131317

Policies / Association Policies

Association Policies Association policies provide places where you can hook in behaviors that trigger when associations are created or removed between two nodes in the Cloud CMS content graph. When two nodes are connected together via an association or an association is broken, these policies trigger and may fire into your custom handlers. The following policies are available: Policy QName Description p:beforeAssociate Raised before an association is created between two nodes p:afterAssociate Ra

Score: 28.54636

API / Tree

Tree 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: 27.928467

Policies / Property Policies

Property Policies Property policies provide places where you can hook in behaviors that trigger when a property is created, updated or deleted. They allow you to get very granular about when you custom code is invoked - such as only when a specific property in your content is affected. The following property policies are available: Policy QName Description p:beforeCreateProperty Raised before a property on a node is created p:afterCreateProperty Raised after a property on a node is created p:bef

Score: 27.61498

Policies / Data List Policies

Data List Policies Data List policies provide places where you can hook in behaviors that trigger when items within a data list are operated upon. When items are added to a data list, removed from a data list or updated, these policies trigger and may fire into your custom handlers. The following policies are available: Policy QName Description p:beforeAddListItem Raised before an item is added to a list p:afterAddListItem Raised after an item is added to a list p:beforeUpdateListItem Raised bef

Score: 25.628296

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.42315

Rules

Rules Content Rules provide a way for you to wire in business logic behind the content graph. Once they're set up, rules run automatically as content is created, updated and deleted within your branch. Rules are content nodes with a JSON payload the describes the Conditions and Actions to be triggered. As with all behaviors, Rule nodes must implement the f:behavior feature. They must be bound to a node upon which to act (either a definition node or a content instance) using a a:has_behavior asso

Score: 16.955378

Content Modeling / Behaviors

Behaviors Cloud CMS lets you wire in behaviors behind your content models so that rules automatically execute when your content is touched. Content editors work with simple forms to create content that conforms to your defined content models. When that content is created, updated or deleted, it automatically triggers policies (or events) which you use to bind in custom behaviors. In this way, the developers can wire up behaviors and the editorial team never needs to know about it. Furthermore, b

Score: 15.951376

Files

Files Antivirus Scanning Attachments Binaries

Score: 15.419928

Content Modeling / Scripts

Scripts Scripts are content nodes with a default attachment of type application/javascript. As with all behaviors, script nodes must implement the f:behavior feature. They must be bound to a node upon which to act (either a definition node or a content instance) using a a:has_behavior association. Script Interfaces If you elect to write scripts to implement custom behaviors, the following signatures can be used inside of your JavaScript: Association Policies function beforeAssociate(association)

Score: 14.763784

Security

Security Cloud CMS provides two ways to describe access rights to things: Object-level / role-based authorities Team / role-based authorities With object-level / role-based authorities, you assign a principal (either a user or a group) a role against something. For example, you might give Joe the CONSUMER role against a content node. When Joe then interacts with the content node in the future, he will do so with the CONSUMER role which will allow him to "read" the node. With team / role-based au

Score: 14.32583

How does security work in Cloud CMS?

Cloud CMS provides two ways to describe access rights to things: Object-level / role-based authorities Team / role-based authorities With object-level / role-based authorities, you assign a principal (either a user or a group) a role against something. For example, you might give Joe the CONSUMER role against a content node. When Joe then interacts with the content node in the future, he will do so with the CONSUMER role which will allow him to "read" the node. With team / role-based authorities

Score: 14.32583

Conditions / Node Has Attachment

Node Has Attachment The nodeHasAttachment condition tests whether a node has an attachment with a given attachmentId and optional contentType. It triggers if a matching attachment is found. JSON Schema { "title": "Node Has Attachment", "properties": { "attachmentId": { "type": "string", "title": "Attachment ID", "default": "default" }, "contentType": { "type": "string", "title": "Content Type" }

Score: 12.614274

Proxy API calls

Whenever a resulting URL looks something like: https://api.cloudcms.com/repositories/f0fb4efd3de07c54420a/branches/9bcdbfea8f2d900f0387/nodes//attachments/thumb.jpg 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: 11.250159

Auditing

Auditing Cloud CMS provides a built-in audit system that automatically logs the activity between users and content through API service methods. The audit system produces an audit trail consisting of audit records that document the access of every user, content object and service method. Audit records are created automatically if they are enabled for your tenant and for the repository against which the operation occurs. Auditing is only available for on-premise, Docker customers. How to Enable Au

Score: 11.238127

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: 10.00381

Application Server / URL Addressability / Node URLs

Node URLs The Application Server supports retrieval of nodes and node attachments via URLs and takes responsibility for setting headers and cache state for optimal performance. This method is the preferred method for dealing with binary payloads as it ensures compatibility with CDN edge caching. In addition, binary and JSON files that are retrieved from the Cloud CMS API are cached on the Application Server itself so that subsequent requests benefit from having a local copy. A notifications laye

Score: 9.84935

What is an Identity vs a User?

The concept of an Identity and a User is distinct in Cloud CMS. They are separate things. Essentially, a User holds the name, email address and other properties about a user and an Identity holds the password. A User may optionally have an identity associated with it but this isn't required. For any users that you want to give the ability to log in, you'll need to have an identity created and associated for them. This is as easy as editing the user and setting their password. When a password is

Score: 8.695962

Find

Find The Cloud CMS Find Service lets you discover and retrieve content using combinations of its three primary content retrieval mechanisms. These mechanisms are: Query (powered by Mongo DB) Search (powered by Elastic Search) Traversal (provides Graph Traversal) A "Find" operation provides a way for you to execute a single API lookup that runs one or more of the above and composes them into a single result set. How it Works When you make a "Find" call, you provide a recipe containing at least on

Score: 8.422701