Found 46 results for "manual topics transfer"

The search executed in 0.001 seconds

Transfer

Transfer Cloud CMS supports transfer (import and export) for all data stores and objects. Transfer allows you to export your data into Archives. An Archive is a ZIP file which contains a manifest file that fully describes the contents of the ZIP. Archives are automatically stored within Vaults. Transfer lets you import existing archives into new data stores. This lets you quickly restore the state of previous projects or reuse previous projects within new endeavors. You can download archives at

Score: 36.84415

Publishing

Publishing Content Types Example Publishing Setup Lifecycle States Preview Servers Publications Workflow

Score: 17.409336

Mitigating the OWASP Top 10

An explanation of how Cloud CMS addresses each of the Top 10 OWASP topics: Mitigating-the-OWASP-Top-10.pdf

Score: 7.87638

Actions / Start Workflow

Start Workflow ID: startWorkflow Starts a workflow with the given node placed into the payload. Configuration Property Type Required Default Description model text true The ID of the workflow model to be used. swimlanes object false Identifies principals to be assigned into workflow swimlanes. The structure is: { "swimlane1": ["domainId1/principalId1"], "swimlane2": ["domainId2/principalId2"] } runtime object false Allows for manual specification of runtime properties including applica

Score: 6.6986904

Application Server / Services / Broadcast

Broadcast The Broadcast service is responsible for relaying messages to members of the application server cluster. It provides an essential publish and subscription service so that application server members can broadcast messages, receive messages and subscribe to topics and events that occur throughout the system. Essential Configuration { "broadcast": { "enabled": , "type": "", "config": { ...configuration } } } There are two

Score: 6.1573853

API / Data Types / Changeset

Changeset Type changeset Datastore Type repository Supports authorities, permissions, transfer In this sense, a branch can be thought of as a stack of changesets. There is a root changeset (where the branch starts) and a tip changeset (where the branch ends). Everything in-between constitutes the changeset history of the branch. This portion of the API therefore is largely for advanced users. The Cloud CMS API lets you dig in and poke around at the changeset history of branches to do things like

Score: 4.726658

Sync from one environment to another

Within Cloud CMS sync capabiities are generally referred to as the "transfer system". They allow you to export individual objects, data stores or even collections of these as an archive (ZIP) within a vault. You can then move those archives to storage for backup or move them to new Cloud CMS server instances for restoration or replication. We have support for transfer within our API, our drivers and also within the user interface. The latter is useful in that you can script it pretty effectively

Score: 4.6318054

API / Data Types / Identity

Identity Type identity Datastore Type directory Supports authorities, permissions, transfer

Score: 4.3281994

API / Data Types / Plan

Plan Type plan Datastore Type registrar Supports authorities, permissions, transfer

Score: 4.3281994

API / Data Types / Settings

Settings Type settings Datastore Type application Supports authorities, permissions, transfer

Score: 4.3281994

API / Data Types / Tenant

Tenant Type tenant Datastore Type registrar Supports authorities, permissions, transfer

Score: 4.3281994

API / Data Types / Archive

Archive Type archive Datastore Type registrar Supports authorities, permissions, transfer TODO

Score: 4.3189783

API / Data Types / Auto Client Mapping

Auto Client Mapping Type autoClientMapping Datastore Type webhost Supports authorities, permissions, transfer

Score: 4.291551

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

Publishing / Content Types

Content Types Cloud CMS lets you customize the Publishing Behavior and the Workflow Per Content Type. You can now Enable/Disable the Preview and Publishing buttons for each Content Type. Customize Publishing Behavior Per Content Type You can disable the Publishing Behavior like Preview button or the Publishing buttons for all the Content types whose content or data you do not want to publish. To Disable the Publishing behaviors of the Content Types: Go to Project Go to Manage Project Go to Publi

Score: 3.8876822

Publishing / Publications

Publications Publications tell the system whenever content on the "master" branch goes into the "live" state, it should be pushed out to the deployment target. Once you Add a Publication to the Project, the content from the Selected Branch will be published to the Selected Deployment Target and its Lifecycle State will change to Live. To Add Publication: Go to Manage Project Publication Settings Click on Publications Click on Add a Publication Select the Branch whose content you wish to deploy t

Score: 3.7600195

Publishing / Workflow

Workflow Cloud CMS lets you define your own Workflows and choose them for the Publish and Unpublish activities. Each activity like Publish and Unpublish will have a Workflow Model which will have a set of instructions on how the contents should be routed during each activity. The default Workflow models we use for the Publish activity is Simple Publish and for the Unpublish activity is Simple Unpublish. You can add your own Workflows and customize your publish and unpublish activities.

Score: 3.6404743

Publishing / Lifecycle States

Lifecycle States Cloud CMS contains four content Lifecycle States during the Publishing process of a content. These define the state of the Content in the Publishing Lifecycle. Each state will have an ID, Title and a Preview Endpoint The four states in the Publishing lifecycle are : - None - Draft - Live - Archived You can look at the lifecycle states as follows: Each state has a Preview Endpoint which can be defined or modified under Preview Servers. These gives a chance to instantly preview th

Score: 3.4228256

Publishing / Preview Servers

Preview Servers Before your changes go to Live website i.e. on the Production mode, to discover problems and fix them right away you can set up the Preview Servers and review the content changes instantly. You can look at the default Preview Servers under Manage Project : The default servers are Authoring and Production and are setup to a sample URL which can be modified with your website URL or some API or an Application. To add your Custom Server, you can click on Add Preview Server and set-up

Score: 3.323477

Query

Query Cloud CMS provides SQL-like, structured query for all of your content. The platform uses MongoDB under the hood to store the JSON for your content. MongoDB offers a powerful, unmatched query engine so that you can execute complex lookups of your content to support both your editorial and runtime application needs. The platform also offers "composite" query operations which let you layer MongoDB queries on top of Elastic Search DSL searches and traversals around node objects. Cloud CMS auto

Score: 3.0954607

API / Patching

Patching Cloud CMS supports the use of HTTP Patch (RFC 5789) along with JSON Patch (RFC 6902) to describe atomic updates to content objects. This allows for lighter JSON payloads by only requiring property-level differences to be sent over the wire instead of full document payloads. JSON Patch supports many property operations including add, remove, move and copy as well as insertion within arrays and key/field manipulation for objects. The HTTP Patch method is invoked like this: PATCH /reposito

Score: 3.0838623

Releases

Releases Releases allow you to set up collaborative workspaces where future sets of content can be worked on in real-time. Content can be created, edited and deleted in the workspace and then scheduled for publishing at a future date. Scheduled publishing allows your content to "go live" automatically - merging your content changes back into the mainline while triggering release actions for things like: Email Notifications CDN Synchronization Web Hook Calls Releases give your content team the ab

Score: 2.4921129

User Interface / Releases

Releases Releases allow you to set up collaborative workspaces where future sets of content can be worked on in real-time. Content can be created, edited and deleted in the workspace and then scheduled for publishing at a future date. Scheduled publishing allows your content to "go live" automatically - merging your content changes back into the mainline while triggering release actions for things like: Email Notifications CDN Synchronization Web Hook Calls Releases give your content team the ab

Score: 2.4921129

API / Data Types / Platform

Platform Configuration As with all data stores, this data store maintain a configuration document that contains system and custom properties. You can write your own properties onto this configuration document if you wish. You might use those properties to query and retrieve the directory at a later time. Some system properties are read-only and others are writable. You can adjust the writable properties to modify the behavior and characteristics of the directory. The following table presents you

Score: 2.432604

API / Data Types / Email Provider

Email Provider Type emailProvider Datastore Type application Supports authorities, permissions, transfer Configuration Email Providers maintain a configuration that you can adjust or consult as you create, update and query for them. The following table presents you the configuration properties. Property Type Default Read-Only Description host text The host address of the email server. Example: smtp.gmail.com port number The connection port on the email server. Example: 25 username text The usern

Score: 2.1813352