Found 136 results for "ui-dev ui-dev evaluators ui-dev evaluators other"

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

Modules / Create a Module / Evaluators / Other

Other tenant-has-plan If the platform owner (tenant) is subscribed to the given plan. { "evaluator": "tenant-has-plan", "condition": "{planKey}" } id If the current entity or viewed object has the given ID. { "evaluator": "id", "condition": "{id}" }

Score: 15.519169

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

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

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

Does Cloud CMS work with iOS, Android, Node.js, PhoneGap, JavaScript, HTML5 and any other popular frameworks?

You work with Cloud CMS just like you would any other ReSTful HTTP/OAuth2 service. In addition, we have a library of drivers and developer guides that you can look to for guidance on building apps for the web as well as iPhone, iPad, Android, PhoneGap, Titanium and many other frameworks.

Score: 2.3564177

Features / Related

Related QName: f:related This feature is applied internally to nodes that are on the other end of a relator association to indicate that the target node is related to the source node. This feature acts as a marker to tell Cloud CMS to consider the related nodes and the relator association at persistence time so the properties can be managed more efficiently in terms of mapping values from one end of the relationship to the other. There is no need to apply or work with this feature manually. For

Score: 2.188747

Cloud CMS Architecture

Cloud CMS has two clusters that we run for customers who host apps with us. One cluster is for the "app server" tier (*.cloudcms.net) and the other is the "API" tier (api.cloudcms.com). The app server cluster consists of Node.js servers, and the API is a Java-backend that is stateless and implements the full REST API: As such, the API doesn't manage connections directly. Any invocation to it is a one-shot where each request contains everything needed to assert the user's identity and proceed wit

Score: 2.121669

Integrations

Integrations Cloud CMS allows you to connect to external cloud-based services for purposes of things like: external data storage for binary data auto-record updates to dns servers event handling to cloud notification handlers To configure these services, you simply create a service descriptor via the main interface: Service descriptors are declared once and can be re-used multiple times within your platform, across different projects and applications. Service descriptors are encrypted on the ser

Score: 2.120444

Connecting via a Corporate Proxy

The Cloud CMS drivers support connectivity through a corporate proxy. The means of doing so are slightly different depending on which driver you're using. Node.js The Cloud CMS Node.js driver detects the following environment variable: HTTP_PROXY If this environment variable is specified, all API calls with be routed through the proxy server at that location. This proxy server may support either HTTP or HTTPS. For example, you may set the environment variable like this: HTTP_PROXY=http://127.0.0

Score: 2.0652032

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

Forms / References

References Forms may use a $ref variable to pull in or include the configuration of another Cloud CMS form (or sub-section of a form). This capability is designed to be compatible with the use of $ref within JSON schema for pulling in alternate schemas or definitions. $ref within schemas Cloud CMS allows you to use the $ref variable within your schemas or definitions to pull in JSON schema blocks from other definitions on the same branch. This is typically done using a QName loader and generally

Score: 2.012767

Application Server / Services / Awareness

Awareness The Awareness Service is responsible for tracking the location of users within a client-side application. As users navigate within a client-side application, they are seamlessly joined and removed from channels (or rooms). As users enter and leave a channel, event handling is triggered, allowing the client-side application to learn of other users who are in a channel or when other users enter or leave a channel. The Awareness Service uses Socket.IO under the hood to provide support for

Score: 2.002566

Application Server / Tags / @link

@link Links to another page. Syntax {@link [uri="uri"] [other token values]} Click me to go to the next page! {/link}

Score: 2.0010092

Workflow / Workflow Handlers / Sync Node

Sync Node Type: syncNode This handler "syncs" nodes that are part of a workflow's payload to a target branch. This handler can be used to have workflow payload nodes automatically copied to or deleted from a target branch. The full config for this handler is as follows: { "targetProjectId": "", "targetRepositoryId": "", "targetBranchId": "", "includeAllAssociations": , "delete": } Examples Sync nodes to another branch in t

Score: 1.9958754

Content Modeling / Content Model Builder / Edit An Existing Content Model

Edit An Existing Content Model Once you have Content Model Builder enabled, click into it and you will be able to see a list of existing Content Models. Click into one to edit it in the Content Model Builder. Select A Form If the content model has more than one forms, select the one you hope to edit: Then the builder will render with the settings in the selected form. Change Field Order Dragging a field and dropping it on top of another non-object field allows you to move it in front of the othe

Score: 1.9792647

Definitions for Date format

Our definitions are based on JSON schema and, as such, the default is to use strings for dates. The date controls in our forms engine let you customize the format string so that you can store ISO 8601 or other formats (perhaps simplified formats) as per your preference. The advantage here is simplicity with these controls and compatibility with JSON schema. The disadvantage is that MongoDB provides a lot of very powerful capabilities for range query and sorting that do not play as nicely with th

Score: 1.9792647

Content Modeling / References

References References provide a way for you to link two definitions together so as to reuse one of the definitions in the other. It gives you a way to centrally define something and then have that something's schema get reused in other definitions in your content model. For example, suppose you have an my:author definition that looks like this: { "type": "object", "properties": { "firstName": { "type": "string", "title": "First Name" }, "la

Score: 1.9484088

Access Cloud CMS content anonymously or as a guest user

This question often comes up from folks who are building HTML applications that run in a browser. They'd like the browser to connect to Cloud CMS to download content and display it. Usually this consists of things like images but also may consist of other types of content in Cloud CMS such as raw nodes, PDF files, video assets or more. OAuth 2.0 and Access Tokens Fundamentally, everything in Cloud CMS is secured from an access perspective using OAuth 2.0. This means that an OAuth 2.0 access toke

Score: 1.9297441

Application Server / Services / Cache

Cache The Cache Service is responsible for providing an application server cache that all processes, whether local or distributed, have access to for non-transactional caching. Objects stored in the cache are eventually available to other members of the cluster (if there are any), no matter whether running on the same server or on other servers in the cluster. Modes The Cloud CMS Application Server can run in one of three modes: single node cluster multiple nodes (on a single process) sticky-clu

Score: 1.9169978

Content Modeling / Definitions / Association Definition

Association Definition An Association Definition describes the schema of a relationship between two nodes. Fundamentally, association instances are JSON objects that conform to the JSON schema of their association definitions. Association definitions allow you to specify the schema of your associations so as to store properties on them. There are primarily two families of associations - a:linked and a:owned, describing linked and owned associations, respectively. A linked association is one in w

Score: 1.9154979

Publishing / Lifecycle States

Lifecycle States Cloud CMS contains four content Lifecycle States during the Publishing process of a content. These define the state of the Content in the Publishing Lifecycle. Each state will have an ID, Title and a Preview Endpoint The four states in the Publishing lifecycle are : - None - Draft - Live - Archived You can look at the lifecycle states as follows: Each state has a Preview Endpoint which can be defined or modified under Preview Servers. These gives a chance to instantly preview th

Score: 1.8961241