Found 225 results for "modules create evaluators context"

The search executed in 0.002 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: 46.61961

Modules / Module Development

Module Development 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 UI Actions Configuration Service Bindings Evaluators Plugins Templates

Score: 24.950195

Modules / Module Development / 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: 23.33054

Modules / Module Development / 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 associate

Score: 21.060074

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

Modules / Module Development / 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: 13.540407

Modules / Module Development / 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: 12.374615

Modules / Module Development / 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": tru

Score: 12.366802

Modules / Module Development / 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: 12.366802

Modules / Module Development / 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": tr

Score: 12.366802

Modules / Module Development / 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: 12.366802

Modules / Module Development / 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 Platfo

Score: 12.348513

Modules / Module Development / 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: 11.597582

Modules / Module Development / 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: 11.383278

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

User Interface / Projects / Create a Project

Create a Project You can create as many projects as you would like within Cloud CMS. Each project provides a collaborate space for your team. You use this collaboration space to: Work on content together Design your content schema, properties and forms Invite users into teams and assign roles and responsibilities Approve content and make it available on your web site or mobile app And much more. There are multiple ways to create a project. For example, you can: Create a Project from scratch -Cre

Score: 10.526054

Actions / Create Thumbnail

Create Thumbnail ID: createThumbnail { "title": "Create Thumbnail(s)", "properties": { "attachmentId": { "title": "Attachment ID", "type": "string", "default": "default" }, "thumbnails": { "type": "array", "items": { "type": "object" } } } }

Score: 10.421656

Documentation - Getting Started - Cloud CMS

Documentation - Getting Started - Cloud CMS System Status Videos Blog Support System Status Buy Now Features Quick Start Releases Pricing Documentation Developers Start a Free Trial Features Quick Start Releases Pricing Docs Dev Start a Free Trial Features Why Cloud CMS Releases Pricing Documentation Developers Ask a Question Start a Free Trial Getting Started Content Modeling Role-Based Editorial UI Instant Preview Platform Multiple Projects Publishing Web Forms Workflow Workspaces Access Contr

Score: 10.286181

User Interface / Security / Create a new Role

Create a new Role The Roles for a Project can be managed on the Roles page. For reference, here are the default Roles available: Let's take a look at the list of the default roles: Roles Description Collaborator “CONNECT”, “READ”, “CREATE_SUBOBJECTS”, “UPDATE”, “DELETE” Connector “CONNECT” Consumer "CONNECT”, “READ” Contributor “CONNECT”, “READ”, “CREATE_SUBOBJECTS” Editor “CONNECT”, “READ”, “UPDATE”, “DELETE” Impersonator “IMPERSONATE” Manager “CONNECT”, “READ”, “CREATE_SUBOBJECTS”, “UPDATE”, “

Score: 9.106402

User Interface / Security / Create a new Team

Create a new Team The Teams for a Project can be managed on the Teams page: First Step is to create the Team In your project, goto Manage Project and select Teams in the left nav To Create a new Team click 'Create Team' Second Step is to add Roles to the team Under Teams, click on your newly created team Select Roles Click '+Grant Role' Select the Roles you want for the Team. Note: if you do not see the Role(s) needed for your Team you will need to create the Roles. Let's take a look at the list

Score: 9.096736

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

Content Modeling / Content Model Builder / Create A New Content Type

Create A New Content Type Once you have Content Model Builder enabled, you can create a new content type from there. Click button "Create Definition" near the top left: Then give your content type a name in the pop up modal: Hit "Create" and you can find the new content model in the list. Click into it to make it more interesting with the Content Model Builder: As you can see in the above image, there are two tabs -- "UI" and "JSON". CloudCMS provides you with two ways to build a content type bu

Score: 7.927963

User Interface / Workflow / View/Create a Workflow Model

View/Create a Workflow Model Switch to Platform level Click 'Workflow Models' (left Nav). Note: You will need to have admin or owner permissions to see the Workflow options. If you select a Workflow model you can Deploy, Undeploy, delete a Workflow model View/Edit Workflow Model Click on the Workflow name, eg Adhoc Approval, to view the Workflow Model To view/edit the Workflow click JSON Manage Active Workflow To see active instances of the workflow model click on Workflow option Note: you can s

Score: 7.8644085

Create a Project - Cloud CMS

Create a Project - Cloud CMS System Status Videos Blog Support System Status Buy Now Features Quick Start Releases Pricing Documentation Developers Start a Free Trial Features Quick Start Releases Pricing Docs Dev Start a Free Trial Features Why Cloud CMS Releases Pricing Documentation Developers Ask a Question Start a Free Trial About Us Company Careers Customers Partners Contact Us Videos Datasheets Release Notes "The only difference between Cloud CMS and your current on-premise document repos

Score: 7.3729753

Modules / Module Development / Configuration Service

Configuration 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] --> --> [co

Score: 7.3498096