Found 43 results for "modules evaluators context"

The search executed in 0.001 seconds

Modules

Modules The Cloud CMS user interface is an HTML / JavaScript application that comes pre-configured with a base application that is feature complete and out-of-the-box. It includes a ready-to-run content management and collaboration tool set for managing documents, web sites, mobile content and more. It also makes some default assumptions about page layout, placement of buttons, availability of functionality and role-based provisioning that may or may not match your desired workflow. Chances are

Score: 43.435192

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

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

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

Modules / Register a Module

Register a Module All you need to build your own add-on modules is GitHub and some JavaScript / HTML skills. You can get started quickly by forking the Cloud CMS UI Sample Add-on Module repository on GitHub. This sample add-on works with the data set provided by the Sample Project (which is included with every free trial). Fork the Sample Module on GitHub Register your Module Note: To register your module, you must have Manager rights to your tenant. If you do not have Manager rights, you will e

Score: 13.035601

Modules / Create a Module / Bindings / Menus - Context

Menus - Context The context key defines the primary, left-hand menu that on every page within the user interface. The left-hand menu serves as a primary navigation root and is visible for everything within both the Platform and all Projects. To populate the context section, your configuration snippet should look like this: { "context": { "items": [] ] } Default Configuration The default UI configuration for the Platform looks a bit like this: { "context": { "items": [

Score: 12.229895

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

Menus - Workflow Context The workflow-context key defines the left-hand menu options for the Workflow pages. To populate the workflow-context section, your configuration snippet should look like this: { "workflow-context": { "items": [] ] } Default Configuration The default UI configuration for the Workflow pages looks a bit like this: { "workflow-context": { "items": [{ "key": "workflow", "title": "Workflow", "order": 1000,

Score: 11.121723

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

Menus - Releases Context The releases-context key defines the left-hand menu options for the Releases pages. To populate the releases-context section, your configuration snippet should look like this: { "releases-context": { "items": [] ] } Default Configuration The default UI configuration for the Releases pages looks a bit like this: { "releases-context": { "items": [{ "key": "project/releases", "title": "Releases", "header": true

Score: 11.113266

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

Menus - Reports Context The reports-context key defines the left-hand menu options for the Reports pages. To populate the reports-context section, your configuration snippet should look like this: { "reports-context": { "items": [] ] } Default Configuration The default UI configuration for the Reports pages looks a bit like this: { "reports-context": { "items": [{ "key": "project/reports", "title": "Reports", "order": 1000,

Score: 11.113266

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

Menus - Task Context The task-context key defines the left-hand menu options for the Workflow Task pages. To populate the task-context section, your configuration snippet should look like this: { "task-context": { "items": [] ] } Default Configuration The default UI configuration for the Workflow Task pages looks a bit like this: { "task-context": { "items": [{ "key": "task", "title": "Task", "order": 1000, "header": tru

Score: 11.113266

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

Menus - User Context The user-context key defines the left-hand menu options for the User/Member pages. To populate the user-context section, your configuration snippet should look like this: { "user-context": { "items": [] ] } Default Configuration The default UI configuration for the User/Member pages looks a bit like this: { "user-context": { "items": [{ "key": "user", "title": "User", "order": 1000, "header": true,

Score: 11.113266

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

Menus - Manage Context The manage-context key defines the left-hand menu options for the platform and project management pages. To populate the manage-context section, your configuration snippet should look like this: { "manage-context": { "items": [] ] } Default Configuration The default UI configuration for the Platform management pages looks a bit like this: { "manage-context": { "items": [{ "key": "platform/manage", "title": "Manage Platfor

Score: 11.090701

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

Modules / Create a Module / Bindings / Menus - My Preferences Context

Menus - My Preferences Context The mypreferences-context key defines the left-hand menu options for the My Preferences pages. To populate the mypreferences-context section, your configuration snippet should look like this: { "mypreferences-context": { "items": [] ] } Default Configuration The default UI configuration for the Platform my preferences pages looks a bit like this: { "mypreferences-context": { "items": [{ "key": "platform/mypreferences",

Score: 10.197242

Docker / Maintenance / Upgrades

Upgrades This document provides technical guidance for upgrades. Upgrade to Cloud CMS Version 3.2 The Elastic Search version in this release has been updated from 1.7.1 to 6.2.4. Steps to follow to set up Docker 3.2: Download the Docker release 3.2 here. Download the Zip or Tar file of Elastic Search 6.2.4 here and then Unzip the package. Unzip the Docker release package, Create a new folder and paste the kit you use from the package. You can also replace your existing kit with the new release's

Score: 9.695309

Docker / Configuration / API Server

API Server The Cloud CMS API Server is a Java application that launches inside of a Java Servlet Container. The Java application surfaces a REST API as well as backend services and DAOs to support connectivity to Mongo DB, Elastic Search and a slew of Amazon services including S3, SNS, SQS, Route 53, Cloud Front and more. Properties File Cloud CMS is primarily configured via a properties file that is auto-detected and loaded when the underlying Spring Framework starts up. This properties file is

Score: 8.296861

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

Content Modeling / Content Model Builder / Extend Field Templates

Extend Field Templates If you find the existing field templates still limited to your need, Modules allow you to add your own field template. In the following sample, we added a field template that provides a Summernote WYSIWYG editor. Default CKEditor WYSIWYG: Customized Summernote WYSIWYG: Get the code here in the SDK: https://github.com/gitana/sdk/tree/master/ui/modules/content-model/content-model-field

Score: 6.571232

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

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

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

How does multi-tenancy work?

How does multi-tenancy work? ie I want to have multiple companies with sub-groups of users in each company - to follow, how would we customize the interface for each company? There are two good ways to achieve multi-tenancy with Cloud CMS. - One is to use multiple "projects" - i.e. one per customer. Each project has it's own domain of users and groups, as well as it's own content definitions, instances and ACLs. As such, you can use each project to store the content on a per-client basis. You ca

Score: 4.9366374

Application Server / Tags / @debug

@debug Shows debug context information. Syntax {@debug/}

Score: 4.597206

Application Server / Tags / @value

@value Displays a value and allows for optional in-context editing. Syntax {@value node="_doc" property="propertyName"} {propertyValue} {/value}

Score: 4.519937

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