Search Results

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_behavio

Score: 14.726115

Overview

Overview Conditions provide a way for Rules to evaluate their content and their environment prior to determining whether to proceed with the execution of their Actions. A Condition might be a simple check such as checking to see whether the current content item has a certain property value. But they also might be more complex logic chains consisting of and and or blocks. Cloud CMS provides a number of out-of-the-box Conditions. Scroll down to see a list of available out-of-the-box Condition

Score: 13.705214

Overview

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

Score: 10.29046

Or

Or The or condition tests whether at least one of multiple sub-conditions are true. This joins the sub-conditions together in a logical OR. JSON Schema { "title": "Or", "properties": { "conditions": { "type": "array", "items": { "type": "object", "properties": { "type": { "type": "string" }, "config": { "type": "o

Score: 7.5578694

And

And The and condition tests whether one or more sub-conditions are all true. This joins the sub-conditions together in a logical AND. JSON Schema { "title": "And", "properties": { "conditions": { "type": "array", "items": { "type": "object", "properties": { "type": { "type": "string" }, "config": { "type": "objec

Score: 7.4052825

Config

Config The Configuration Service loads JSON rules for the current application and composes them into a JSON configuration document that is served back. The Configuration Service considers JSON rules that are defined at application level as well as the project, platform and user level. { "config": { "remote": { "enabled": , "appKey": "" } } }

Score: 6.0169992

Overview

Overview 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

Score: 5.948677

Plugins

Plugins Cloud CMS plugins let you enhance your editorial user interface with new features and capabilities that integrate to popular third-party services like YouTube, Vimeo and Google Docs. Plugins provision your editorial environment with things like: new form field types that integrate to third-party services new user interface pages for browsing and working with media from third-party services new actions or rules to enhance your repository's business logic new content types, associat

Score: 5.875848

Evaluators

Evaluators Evaluators are used to define conditions that determine whether a block of configuration should be included in the evaluated and merged configuration document. Evaluators work on different aspects of the runtime experience, including: what is being observed who is observed it what URL is being looked at what objects are known about at the time (i.e. observables) what permissions and authorities the current user has over things that are being observed There are many types of

Score: 5.7905946

Behavior Binding

Behavior Binding QName: f:behavior-binding Marks an association as pointing to the implementation of a behavior for a policy on the source node. Valid target nodes include script nodes and rules. By applying this feature, you indicate that the target node script or rule should execute when the policy triggers. The target node (script or rule) must implement the f:behavior feature. For example, you might upload a JavaScript file that provides an implementation of a method to handle the after

Score: 5.050112