From 85600746e36ccba83803178be077b5478d306554 Mon Sep 17 00:00:00 2001 From: Donald Oakes Date: Tue, 25 Feb 2020 10:29:15 -0700 Subject: [PATCH] docs --- docs/_docs/help/assetPersistence.html | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/docs/_docs/help/assetPersistence.html b/docs/_docs/help/assetPersistence.html index 4c7c55f9ca..f91ccc7f23 100644 --- a/docs/_docs/help/assetPersistence.html +++ b/docs/_docs/help/assetPersistence.html @@ -6,10 +6,9 @@

Asset Persistence

-In MDW, the process definitions and other design-time resources assets are saved in a version control repository (GitHub) and -the runtime data is stored in a MySQL, Oracle or MongoDB database. This persistence model has the key advantage for delivering flexible, powerful branching and merging capabilities. -This is especially important to ensure the integrity of in-flight processes when multiple versions of an MDW workflow coexist in a production environment. The VCS Assets option -also offers dramatically improved performance in MDW Studio project access, as well as reduced server startup times. +MDW runtime data is stored in a MySQL, Oracle or MongoDB database, while process definitions and other design-time assets +are saved in a version control repository (Git). This asset persistence approach makes for powerful branching and merging capabilities. +This is especially important to ensure the integrity of in-flight processes when multiple versions of an MDW workflow coexist in a production environment.

Motivation

As more and more of an application's business value moves into workflow, it's imperative that users have the tools to: