Found 145 results for "modules evaluators page"

The search executed in 0.001 seconds


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

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

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

Actions / Invalidate Page Renditions

Invalidate Page Renditions ID: invalidatePageRenditions This action invalidates page renditions in one or more applications. You can target a single page rendition or a broad set of page renditions using a custom query. { "title": "Invalidate Page Renditions", "properties": { "applicationDeployments": { "title": "Application Deployments", "type": "array", "items": { "type": "object", "properties": {

Score: 10.189495

API / Pagination

Pagination Pagination allows you to control the result set that comes back from Cloud CMS for any operations that produce a list of items. It is called pagination because it gives you a way to organize your record set into pages and then get those pages back, one at a time. Pagination gives you a way to adjust the result set before it is sent over the wire (and back to you) so that you can have smaller "paged" payloads. Pagination is useful because, most of the time, unless the result set is ver

Score: 7.198076

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:

Score: 6.571232

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

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

Application Server / Tags

Tags @associations @block @content @debug @dependency @expand @form @fragment @include @iter @layout @link @nodeAttachmentValue @params @processTemplate @query @queryOne @relatives @resource @search @value

Score: 5.862587

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

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

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

Modules / Create a Module / Bindings

Bindings Actions Each action supports a binding like this: { "key": "{key}", (required) "title": "{title}", (required) "action": "{action}", "module": "{module}", "iconClass": "{iconClass}", "order": {order}, "allowPermission": [], "rejectPermission": [], "allowAuthority": [], "rejectAuthority": [] } The properties are defined as shown below: Property Type Required Description key string yes a unique key for the me

Score: 3.8620498

Docker / UI Extensions

UI Extensions The Docker-based Cloud CMS UI provides additional extension patterns beyond the AMD-driven mechanism for user interface components and screens. Since Docker allows you to run on-premise, you can use these extension patterns to influence more foundational changes to the way the application works. Environment Variables When the Cloud CMS user interface starts up, it looks to environment variables to tell it whether there are any extensions available to be loaded. Extensions are store

Score: 3.8203287

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

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

Application Server / Web Content Management

Web Content Management The Application Server provides the runtime for the Cloud CMS Web Content Management solution. Web Content Management is a term that enterprise vendors have been using for years to distinguish between the role that a CMS (content management system) plays for an organization - it may be used to collaborate around your internal documents, legal records, digital assets and many other content items in addition to your web and mobile content. Cloud CMS provides a Web Content Ma

Score: 2.508824

Application Server / Services / Web Content Management

Web Content Management Whether to support dynamic loading of web pages from Cloud CMS. This enables the Cloud CMS web content management solution. Here is what a full configuration set looks like: { "wcm": { "enabled": true, "cache": true, "cacheKey": { "params": { "includes": [], "excludes": [], "excludeAll": false } }, "pageCacheTTL": undefined, "pageCacheRetryTimeout": u

Score: 2.384607

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

Modules / Create a Module / Bindings / Type Pages

Type Pages The type-pages key lets you define routes that serve as landing pages for entity types. Specific pages within Cloud CMS serve as landing pages for an entity that is being viewed. Type Page configurations allow you to specify which URI should be dispatched to when viewing. Each type page has a very simple binding like this: { "uri": "{uri}" } Example - Dispatching a Workflow Task to the Overview Page { "evaluator": "entity-is-type", "condition": "Gitana.WorkflowTask", "

Score: 2.3266678

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

User Interface / Menu

Menu Although having the ability to do a lot of stuff is great, sometimes too many things to do can be overwhelming. So we provide you with a way to configure menus on all the different pages. You can Customize menus to display Change menu titles Customize Menus to Display Here's a screenshot of "Manage Platform" page. On the left hand side, you can see a super long menu separated into two blocks: "MANAGE PLATFORM" and "DEVELOPERS", each with quite a few submenus. An editorial manager may not wa

Score: 2.2941384

Application Server / Tags / @dependency

@dependency Indicates that the cache state for a WCM-generated page has a dependency. Dependencies play two important roles within Cloud CMS. First, they indicate to the runtime whether the previously cached output for a page may be used to service a future request ("requirements"). And second, they identify which data objects were used to build the page output ("produces"). This latter information is then be used to invalidate page objects when content items change within the Cloud CMS editoria

Score: 2.2846363