Found 170 results for "integrations sns-notifications configuration"

The search executed in 0.001 seconds

Integrations

Integrations Cloud CMS allows you to connect to external cloud-based services for purposes of things like: external data storage for binary data auto-record updates to dns servers event handling to cloud notification handlers To configure these services, you simply create a service descriptor via the main interface: Service descriptors are declared once and can be re-used multiple times within your platform, across different projects and applications. Service descriptors are encrypted on the ser

Score: 45.661476

Docker / Configuration

Configuration API Server

Score: 13.65567

API / Data Types / Billing Provider Configuration

Billing Provider Configuration Type billingProviderConfiguration Datastore Type application Supports authorities, permissions, transfer If this sounds familiar, it's because it's exactly what Cloud CMS uses to supports its own subscription plans for Cloud CMS customers. Just as we bill our customers for metered usage of the platform, you are free to pass those costs downstream to your own clients. And you can use the very same technical capabilities and facilities to do so. Cloud CMS offers bill

Score: 9.366771

Modules / 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: 1.8199859

Application Server / Services / Config

Config The Configuration Service loads JSON rules for the current application and composes them into a JSON configuration document that is served back. The Configuration Service considers JSON rules that are defined at application level as well as the project, platform and user level. { "config": { "remote": { "enabled": , "appKey": "" } } }

Score: 1.780455

User Interface / UI Views

UI Views Customized changes to the user interface configuration can be introduced through the use of UI Config documents. UI Config documents are JSON documents that contain one or more configuration blocks. The UI Config configuration blocks are loaded after the standard configuration document and therefore have the opportunity to either extend or override the base configuration. UI Configs are scoped either to the platform or to the project. As such, you can use UI Config objects to customize

Score: 1.7348398

Modules / 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: 1.7272918

Application Server / Services / Notifications

Notifications The Notifications service is responsible for receiving messages from the outside world. These are frequently transmitted via a message queue or broker and signal the cluster that it should take some action to update its state. This may include things like invalidating caches or re-syncing content. Essential Configuration { "notifications": { "enabled": , "type": "", "configuration": { ...configuration } } } There ar

Score: 1.71863

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

Modules / 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: 1.7079906

Modules / 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: 1.7023348

Modules / 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: 1.7023348

Modules / 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: 1.7023348

Modules / 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: 1.7023348

Modules / 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: 1.7023348

Features / Renditioned

Renditioned QName: f:renditioned Indicates that a f:renditionable node has been renditioned 1 or more times. Configuration This feature does need configuration. Renditioned Example { "title": "My Article", "_features": { "f:renditioned": { } } }

Score: 1.7017626

Modules / 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: 1.7015643

Forms / Fields / CK Editor

CK Editor ID: ckeditor The ckeditor field renders the popular CKEditor HTML control. This offers a fully-featured HTML editor on top of a string schema type. It is ideal for situations where you wish to provide your editorial team with the ability to edit HTML visually and offers a large range of plugins and behaviors that you can customize. For basic information of what is possible in terms of configuring this field type, please view the Alpaca Forms documentation for the CKEditor field. Config

Score: 1.6998718

Features / Titled

Titled QName: f:titled Indicates that a node should have the title and description JSON properties. Configuration This feature does need configuration. Titled Example { "title": "My Article", "description": "Hello World", "_features": { "f:titled": { } } }

Score: 1.6975479

Modules / 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: 1.6911346

Features / Behavior

Behavior QName: f:behavior This features indicates that a node provides the implementation of a behavior. This feature simply tags the node as a behavior implementation. The node must be a script or a rule. Configuration This feature does need configuration. Behavior Example { "title": "My JavaScript file", "_features": { "f:behavior": { } } }

Score: 1.6850287

Features / Relator

Relator QName: f:relator This feature is applied internally to relator associations within the content graph that connect two nodes via a relator property. There is no need to apply this feature manually. For information on relator properties, please see relator properties. Configuration This feature does require any configuration.

Score: 1.6808964

Features / Rendition

Rendition QName: f:rendition Applied to a node to indicate that its existence is the result of having been rendered automatically from the contents of another node (one that has the f:renditionable feature). Configuration This feature does need configuration. Rendition Example { "title": "Web Page Article", "_features": { "f:rendition": { } } }

Score: 1.6808964

Modules / 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: 1.6691706

Features / Audit

Audit QName: f:audit Marks a content node as auditable. Operations against this node will be logged and recorded by the Cloud CMS auditing service and stored as audit records on your platform. These audit records can then be viewed within the Cloud CMS user interface or downloaded for use in third-party reporting systems. Configuration This feature does need configuration. Audit Example { "title": "My Content Instance", "_features": { "f:audit": { } } }

Score: 1.6505393