Found 78 results for "ui-dev ui-dev evaluators ui-dev evaluators document"

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

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

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

Modules / Create a Module / Bindings / Document Actions

Document Actions The document-actions key defines actions that are available on a per-document basis. When working on an individual document, this key defines the actions that will appear as operations that can be performed. The base configuration looks like this: { "config": { "document-actions": [] } } Example - Add an Action { "config": { "document-actions": [{ "key": "do-something-awesome", "title": "Do Something Awesome", "modu

Score: 12.970455

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 / 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: 8.5943985

User Interface / Multilingual

Multilingual When applied to a node, this indicates that you wish to have the contents of this node support multilingual behavior and translated content. This node then serves as the "master node" for translation support. Master nodes have a:has_translation associations to translation nodes that hold copies of the content (JSON and any attachments) in the target locale Marking a node as f:multilingual does not automatically produce translations for you. However, once marked, the Cloud CMS user i

Score: 3.7593112

Modules / Create a Module / Bindings / Menus - Subcontext

Menus - Subcontext The subcontext key defines the secondary, left-hand menu that sometimes appears on pages that require it. One such example is the Document page which shows a document-specific menu on the left-hand side. To populate the subcontext section, your configuration snippet should look like this: { "subcontext": { "items": [] ] } Default Configuration The default UI configuration for the Document looks essentially like this: { "subcontext": { "items": [{

Score: 3.656197

User Interface / Tags

Tags Cloud CMS lets you manage your tag hierarchy and assign those tags to your content. Content that is tagged is automatically marked with the tag information (within the tags property) and will also maintain an a:has_tag association in the content graph that points back to the tag instance. Tags are first class citizens within Cloud CMS. They are content like everything else. Once content is tagged, you will see it reflected in the user interface as such. You will be able to navigate your con

Score: 3.6486197

Modules / Create a Module / Actions

Actions Cloud CMS provides a large number of actions that can be bound to links sections within configuration blocks. This allows you to customize dropdowns, button toolbars and action links at various places within the user interface. It also provides a way for you to override action implementation classes for your own users. For a list of these actions, see Actions on the lower left-hand menu. account change-password addon install-addon uninstall-addon applications delete_applications new_appl

Score: 3.5221698

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

User Interface / Awareness

Awareness Awareness service allows you to see who's viewing/editing the same document with you in realtime, just like google docs. In the above screenshot, there are three user avatars showing in the top right corner. That indicates that there are three people (including yourself) viewing/editing this document right now. Hover on each avatar to see the detail -- find out whom they are if you don't recognize the avatar. Auto Lock on Document Editing There are three possible phases you might see i

Score: 3.4827156

User Interface / Multilingual / Customize Translations UI

Customize Translations UI Cloud CMS allows you to customize UI simply with configurations in your module. Here we will use the following example to demonstrate this feature. For multilingual documents with translations, if you go to the multilingual document's Edit Properties page, the default UI looks like this: In the above screenshot, the Edit Translations button allows you to select a translation of the multilingual document from the dropdown. It's a way to quickly edit the translated docume

Score: 3.4775612

Content Modeling / Default Paths

Default Paths Your content types define schemas that Cloud CMS uses to render intuitive forms for content entry. In addition, content types let you configure persistence paths so that JSON documents created using these forms are automatically saved in a directory structure that you intend. Paths support templated variables so that the path can be dynamic. It can depend on the values having been entered. For example, let's suppose I have the content type for an article, like this: { "title":

Score: 3.3854027

Managing a large number of PDFs or images

In Cloud CMS everything is a node. A node has JSON properties and could also have binary attachments. What you would call a "file" is a node with properties describing it's folder location and a "default" attachment holding the payload (PDF file, image, MSWord doc, etc). Typically, for large number of PDFs, images, etc, we suggest individual nodes with a single attachment each (which is the PDF, image, etc). We have many customers who use Cloud CMS in this way and it essentially works like a doc

Score: 3.32935

Features / Extractable

Extractable QName: f:extractable Indicates that a node should have metadata properties extracted from its primary binary attachment. When applied to a node, Cloud CMS will look at the attachment's MIME type and consider the binary object as a potential source of JSON properties that should be extracted and set onto the JSON of the document ahead of write. This capability is triggered at write time whenever the binary attachment is updated. It does not necessarily indicate that the JSON document

Score: 3.302105

User Interface / Favorites

Favorites Cloud CMS allows users to add documents to Favorites. Add to Favorites To add to favorites, click "Add to Favorites" under "Document Actions" in a Document Overview page. Remove from Favorites To remove from favorites, click "Remove from Favorites". Manage All Favorite Documents Navigate to "Manage Favorites" from your account drop-down menu and view all of your personal favorite documents. You can, for instance, remove selected items from Favorites (this action only removes the docume

Score: 3.302105

Modules / Create a Module / Bindings / Menus - Tab Context

Menus - Tab Context The tabcontext key defines a tertiary menu structure consisting of tabbed elements. These tabs aren't used often but are used presently on the Merge Conflict Resolution pages. To populate the tabcontext section, your configuration snippet should look like this: { "tabcontext": { "items": [] ] } Example - Add a Tab Item We can add a new menu option under the Document header by introducing a config block like this: { "tabcontext": { "items": [{

Score: 3.1203043

User Interface / Workflow / How to Start a Workflow

How to Start a Workflow Note: A Workflow model is defined at Platform level and is available within all projects See workflow video: https://www.cloudcms.com/resources/introduction-to-workflow.html Example Start a workflow from a ‘document’ There are a number ways to start a workflow. Here is just one: open a document Click 'Workflows' and then ‘+Start Workflow’ This will bring up the Start Workflow Form. Complete the fields in the form. Notes: In our example, the Adhoc Workflow, you will need a

Score: 3.0783856

User Interface / Create/Edit Content

Create/Edit Content In a Project you can find your content a number of ways: Content (left Nav) - Content listed under Content Types Folders (left Nav) - Folder/File view of the content Search (left Nav for a detailed search or top right for a keyword search) Viewing a Content item With any of the options above, to find or list the content, click on the 'title' of the content item to open the 'Document Overview': Note: your tenant may be configured such that the options available in the left nav

Score: 2.995177

Modules / Create a Module / Bindings / Documents - List Buttons

Documents - List Buttons The documents-list-buttons key defines actions that are available at buttons at the top of the documents browsing page. These actions are defined relative to the currently viewed document or folder. The base configuration looks like this: { "config": { "documents-list-buttons": [] } } Default Configuration The base configuration looks like this: { "config": { "documents-list-buttons": [{ "key": "new", "title": "Actions.

Score: 2.9848228

CMS editor Locking

There are two levels of locking which usually come into play in a scenario like this. One is a "UI lock" which is taken out when a user begins editing something within the user interface. This lock is released when they finished editing (either by hitting save or canceling). The other lock is a "data lock" which is a transactional lock 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

Score: 2.9616032

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