Found 46 results for "ui-dev ui-dev actions overview"

The search executed in 0.001 seconds

Actions

Actions Cloud CMS provides an Action framework that lets you kick off Actions that perform content operations on your behalf. Actions are units of work that are typically fired off as a result of an event handler or listener. For example, you might register an Action that triggers when a piece of content is updated or when a workflow task transitions. The Action might do something like Send an Email or Fire off a Web Hook. The Cloud CMS Action framework aspires to provide complete units of work

Score: 33.428608

Getting Started

Getting Started Welcome to the Cloud CMS Documentation center. Cloud CMS is an API-first content management system that provides everything you need on the back end to power web sites and mobile applications. Cloud CMS makes it easy for your business users to create, manage and publish amazing content to your users! You are reading the Getting Started guide. To learn more about Cloud CMS and what it does, select from the links provided below or use the tree on the left-hand side. We offer severa

Score: 27.73021

Rules

Rules Content Rules provide a way for you to wire in business logic behind the content graph. Once they're set up, rules run automatically as content is created, updated and deleted within your branch. Rules are content nodes with a JSON payload the describes the Conditions and Actions to be triggered. As with all behaviors, Rule nodes must implement the f:behavior feature. They must be bound to a node upon which to act (either a definition node or a content instance) using a a:has_behavior asso

Score: 19.400984

Application Server / Services / Overview

Overview For more information on configuration of the Cloud CMS application server, please visit Cloud CMS App Server on GitHub. { "name": "Cloud CMS Application Server", "setup": "single", // single, cluster, sticky-cluster "socketFunctions": [], "routeFunctions": [], "configureFunctions": {}, "beforeFunctions": [], "afterFunctions": [], "viewEngine": "handlebars", "storeEngines": { "app": { "type": "fs", "config": {

Score: 18.485733

Branches / Actions

Actions You can optionally configure Actions that execute when a release goes live. Some actions support variables. The following variables are always available: release - a JSON object of the release along with all metadata about the release releaseId - the ID of the release object branchId - the ID of the release branch snapshot - the ID of the snapshot that was generated after merge The following Actions are supported: Send Email Fire Web Hook For each action, you need to provide a configurat

Score: 14.634769

Releases / Actions

Actions You can optionally configure Actions that execute when a release goes live. Some actions support variables. The following variables are always available: release - a JSON object of the release along with all metadata about the release releaseId - the ID of the release object branchId - the ID of the release branch snapshot - the ID of the snapshot that was generated after merge The following Actions are supported: Send Email Fire Web Hook For each action, you need to provide a configurat

Score: 14.483027

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

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

Modules / Create a Module / Bindings / Documents - List Selected Actions

Documents - List Selected Actions The documents-list-selected-actions key defines actions that are available for selected items within the documents browsing page. These actions appear under the Selected... dropdown and apply to items that are selected (using checkboxes or radio buttons) on the page. The base configuration looks like this: { "config": { "documents-list-selected-actions": [] } } Default Configuration The base configuration looks like this: { "config": {

Score: 10.4776945

User Interface / Workflow / Your Task Dashboards

Your Task Dashboards Tasks assigned to you in a Workflow process can be seen in your Platform Dashboard, Project Dashboard, or an email may have been sent to you with the Task link Platform Dashboard - Tasks asigned to you for all Projects will be listed Project Dashboard - Tasks asigned to you for the Project only will be listed Task Overview If you click on a task, or open the Task link in the email, the Task Overview page is opened - From here you can perform the following actions on the task

Score: 9.657214

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

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

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

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

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

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

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

Application Server / Services

Services Awareness Broadcast Cache Config Driver Config Duster Flow Insight Local Notifications Overview Performance Server Tags Virtual Driver Virtual Hosts Web Content Management Welcome

Score: 5.390639

User Interface / Workflow / View Active/Inactive Workflow

View Active/Inactive Workflow You can view both the Active and Inactive workflow from the Platform and Project levels. The Platform level will show all workflow for all Projects and at Project level it will show all workflow for that Project. Click Workfow Title to open the Workflow Overview page

Score: 5.238607

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

Content Modeling / Scripts

Scripts Scripts are content nodes with a default attachment of type application/javascript. As with all behaviors, script nodes must implement the f:behavior feature. They must be bound to a node upon which to act (either a definition node or a content instance) using a a:has_behavior association. Script Interfaces If you elect to write scripts to implement custom behaviors, the following signatures can be used inside of your JavaScript: Association Policies function beforeAssociate(association)

Score: 4.5281897

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

Modules / Create a Module / Bindings / Project Bar - Buttons

Project Bar - Buttons The projectbar-buttons key defines actions that should appear in the project button bar at the top of project pages. This bar is used to convey project information and also provides a workspace selector allowing users to toggle between workspaces. The base configuration looks like this: { "config": { "projectbar-buttons": [] } } Example - Add an Action { "config": { "projectbar-buttons": [{ "key": "open-website", "title":

Score: 4.507319

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

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