Search Results

API / Content Models / Features

Features Features are aspect-oriented, cross-cutting concerns that can be applied to nodes. Once applied, they may introduce new behaviors and metadata to your content objects. You can use features to describe cross-cutting or aspect-oriented concerns that can be plugged onto your content nodes at any time. Features may participate in the inheritance tree of content types or they may be injected anywhere and at any point. There are a number of out-of-the-box features provided by Cloud CMS, inclu

Score: 15.301353

Using swimlanes in workflow

Workflow swimlanes are assigned the domain-qualified ID of a principal (which can be either a user or a group). If it is set to a user, then a transition of a workflow into that swimlane will result in a task being assigned to a specific user. If it is set to a group, then a transition of a workflow into that swimlane will result in a task being assigned to a group where none of the members of the group are assigned anything. Rather, the task appears in a list of available tasks that any of the

Score: 8.101879

API / Integrations / Amazon SQS

Amazon SQS The Amazon Simple Queue Service (SQS) is a fast, reliable, scalable, fully managed message queuing service. Amazon SQS makes it simple and cost-effective to decouple the components of a cloud application. You can use Amazon SQS to transmit any volume of data, at any level of throughput, without losing messages or requiring other services to be always available. Cloud CMS Application Server The Cloud CMS Application Server is a middle-tier cluster that sits between your mobile/web appl

Score: 7.82135

Fine Tuning User Management

Teams provide a very broad way to assign authorities. If a Team grants the Consumer authority, say, it grants that authority over everything in the project. That means all content is readable by anyone on the team. While this is useful in a number of cases, it is also too broad a stroke for more complex scenarios. In a more complex scenario where you wish to limit read access for specific types of content to specific users. To do this, you start by modifying your Teams so they no longer do that

Score: 7.6290264

Role-based security access

You can configure a Cloud CMS project to provide precise, role-based access to content types and content instances. Let's take a look at example of how this is done! Suppose that you have three users - Jim, Dwight and Michael - and two content types (my:article and my:news). We would like things to work like this: Michael is the boss. He is allowed to view, create, edit and delete content content of all types. Dwight is a worker. He is allowed to view, create, edit and delete content of type "my

Score: 7.249036

UI Guide / Projects / Create a Project

Create a Project You can create as many projects as you would like within Cloud CMS. Each project provides a collaborate space for your team. You use this collaboration space to: Work on content together Design your content schema, properties and forms Invite users into teams and assign roles and responsibilities Approve content and make it available on your web site or mobile app And much more. There are multiple ways to create a project. For example, you can: Create a Project from scratch -Cre

Score: 7.1429195

UI Guide / User Management / Create a new Team

Create a new Team The Teams for a Project can be managed on the Teams page: First Step is to create the Team In your project, select Teams in the left nav (near the botton of the Left Nav options) To Create a new Team click 'Create Team' Second Step is to add Roles to the team Under Teams, click on your newly created team Select Roles Click '+Grant Role' Select the Roles you want for the Team. Note: if you do not see the Role(s) needed for your Team you will need to create the Roles. Let's take

Score: 6.976562

Node Lifecycle Events

First, you configure your tenant with the AWS credentials of an IAM user and a SNS topic ARN that you wish to publish notification events to. This can be on your own AWS account so that you can work with these notifications any way you'd like. The notifications are for a variety of node lifecycle events. The primary one is "node_invalidation" which happens whenever a node's state changes. It's an indication that anyone caching anything downstream might want to reconsider their cache state. In te

Score: 6.625638

UI Guide / Projects / Deleted Items

Deleted Items Cloud CMS provides a "copy on write" mechanism for any creates, updates or deletes to the content in a branch. This means that whenever you delete something, you're actually masking it as deleted. The content itself is never destroyed or removed permanently. As such, it is always possible walk backwards in time and discover content that was deleted - all the way back to the moment when your branch or repository was created. To make things easier, Cloud CMS provides a "deletions" in

Score: 6.1734886

API / Security / 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: 6.1465893