Found 29 results for "ui-dev ui-dev evaluators ui-dev evaluators logic"

The search executed in 0.0 seconds

Modules / Create a Module / 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 evaluators

Score: 43.109238

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

Modules / Create a Module / Evaluators / Logic

Logic and If ALL of the contained condition blocks evaluate to true. { "evaluator": "and", "condition": [block1, block2...] } or If ANY of the contained condition blocks evaluate to true. { "evaluator": "or", "condition": [block1, block2...] } not If the contained condition evaluates to false. { "evaluator": "not", "condition": { ... } }

Score: 18.856337

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

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

Modules / Create a Module

Create a Module Common files that each module should have: module.json (where you give the module a name) install.js uninstall.js As soon as you have these files, the rest is up to you depending on what you would like to customize in the module. Take a look at some sample modules in our SDK Actions Bindings Config Service Evaluators Plugins Templates

Score: 12.564022

Modules / Create a Module / Evaluators / Page

Page These evaluators work against characteristics of the currently viewed page. uri-match If the currently dispatched page URI matches a given URI (with tokenized expressions). { "evaluator": "uri-match", "condition": "{uri}" } Example: { "evaluator": "uri-match", "condition": "#/projects/{projectId}/documents" } uri-starts-with If the currently dispatched page URI starts with a given URI (with tokenized expressions). { "evaluator": "uri-starts-with", "condition": "{uri}

Score: 12.514304

Modules / Create a Module / Evaluators / Project

Project These evaluators consider the current project and project observables. project-has-application If a Project is currently being observed and has at least one Application defined. { "evaluator": "project-has-application" } project-has-module If a Project is currently being observed and has the given module. { "evaluator": "project-has-module", "condition": "{moduleId}" } project-has-warehouse If a Project is currently being observed and has at least one Warehouse defined. {

Score: 12.037933

Modules / Create a Module / Evaluators / Document

Document These evaluators have access to a specific document and are used to determine actions and operations around a document. document-has-attachment If the document has a given attachment. { "evaluator": "document-has-attachment", "condition": "{attachmentId}" } document-has-qname If the document has the given qname. { "evaluator": "document-has-qname", "condition": "{qname}" } document-has-type If the document has the given type. { "evaluator": "document-has-type", "

Score: 11.5965

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

Modules / Create a Module / Evaluators / Context

Context These evaluators have access to everything that is currently being observed within the user interface. context-application If an Application is currently being observed (or not, see Boolean evaluators above). If condition is not supplied, it is assumed to be true. { "evaluator": "context-application" } Or { "evaluator": "context-application", "condition": false } context-application-has-warehouse If an Application is currently being observed and it has a warehouse associated

Score: 9.872789

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

Modules / Create a Module / Config Service

Config Service The configuration service evaluates a series of conditional configuration blocks and determines which blocks to keep in composing a final configuration document for the user interface. The configuration document consists of blocks that define JSON structures that are to be merged into a final JSON configuration that powers the user interface. The configuration service executes two phases - evaluate and merge. It essentially looks like this: [block1] --> --> [config1]

Score: 6.9408607

Conditions

Conditions 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 it also might consist of more complex logic chains utilizing and and or blocks. Cloud CMS provides a number of out-of-the-box Conditions: And Node Has Attachment Or Property Changed Property Comparison

Score: 4.571799

User Interface / Search

Search Content is automatically indexed when it is created, modified, or uploaded in Cloud CMS. The index is across the Content properties and any attached file eg Word, PDF,.. Platform At Platform level you can search for Content across all projects subject to your access permissions. Project Search at Project level provides more options and is configureble Project Search Settings Search for a Project can be configured. go to Project Settings (left nav). Note: To have the Project Settings as an

Score: 4.5083723

Search / Query String Reference

Query String Reference Cloud CMS lets you search for your content using either a text-based query string or a JSON block. These two methods are fairly equivalent for most typical operations. They provide two ways to express a search operation that will execute within Elastic Search. They are expressions of the Elastic Search DSL. This portion of the documentation goes into some of things you can do with the former, textual representation of an Elastic Search query string. In Cloud CMS, you can t

Score: 4.2423577

Modules / Create a Module / 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, associations an

Score: 4.180909

Projects

Projects In Cloud CMS, a Project is an isolated workspace in which your team can collaborate on the production and publication of content. You can create as many Projects as you wish. Within each Project, you can: Design your content model (types, features and associations) Build out editorial forms for easy-content entry Wire up "automagic" business logic consisting of Rules, Actions and Conditions to automatically do things like call out to web hooks, send emails or sanitize your data as edito

Score: 3.8515966

Workflow / Workflow Handlers / Web Hook

Web Hook Type: webhook This handler makes an HTTP(S) POST to a remote web service. It automatically passes along any relevant information about the workflow, task or transition so that your web service can get to work. The config for this handler looks like this: { "url": "http://myserver:port/controller" } In addition, you can supply username and password properties in support of Basic authentication to your listener endpoint: { "url": "http://myserver:port/controller", "username":

Score: 3.6594381

General / Locking

Locking Cloud CMS supports locking of nodes (or content instances). Locking allows content editorial team members to explicitly block other editors from working on content that they're already working on. When a piece of content is locked by a user, all other users in the project who have access to the piece of content will be prohibited from making modifications. They will be able to read the content but they will not be able to save any modifications. Once the lock is released by the user who

Score: 3.3274229

Forms

Forms Cloud CMS automatically generates and displays mobile-friendly forms using the Alpaca Javascript / HTML5 forms engine. The Alpaca Forms Engine was created by Cloud CMS and is available as an open source project. In addition to the standard library of 40+ controls provided by Alpacajs, Cloud CMS provides support for several additional controls that run within the Cloud CMS user interface. Schemas and Forms Cloud CMS separates the concept of a schema from a form. A schema (or definition) des

Score: 3.2536237

WCM and Caching

In Dust, there is the notion of a context which has a stack running underneath it. As you drill down into tags, a new context is pushed that can write new context variables as well as access previous variables from previous stack frames. What we're doing in cloudcms-server is providing a dependency tracker so that each tag gets to declare the output (the HTML that was generated) and the set of dependencies that it depended on in order to generate the output. As an example, a query might run an u

Score: 3.2536237

Content Modeling / Definitions / Feature Definition

Feature Definition A Feature Definition is a cross-cutting concern or Aspect that you can apply arbitrarily to content instances or content types (to apply to all instances of a type). A Feature Definition is used to optionally describe additional schema that should be applied to a content or association type. Feature Definitions also endow content instances with special behaviors. Feature Definitions are defined in much the same way as Types or Associations. Each Feature has a QName and the JSO

Score: 2.8163729

Deployment / Deployment Handlers / HTTP Deployment Handler

HTTP Deployment Handler Handles the deployment of one or more Deployment Packages to a custom HTTP endpoint. The custom HTTP endpoint is described by: url statusUrl username password Custom HTTP endpoints are useful for a large variety of purposes, including writing data into custom databases, synchronizing content from Cloud CMS with existing Content Management products, hooking into custom logic for CDN or cache invalidation and much more. Configuration { "url": "{url}", "statusUrl": "

Score: 2.6155176

Branches

Branches Cloud CMS stands apart from just about every other content management product on the market in that it offers a versioning model that is based around changesets. It is inspired by Git or Mercurial and provides a changeset versioning system that captures every touch - every create, update or delete - that you make. Nothing is ever lost. Every data operation is fully transactional with every transaction payload is fully captured into its own changsets. Transactions span multiple documents

Score: 2.0930681