- Added a realtime workflow option for content publishing.

- Added switches to auto request commit operations and skip adding comments.

lib/WebGUI/i18n/English/VersionTag.pm

@@ -7,6 +7,12 @@ our $I18N = {
 		lastUpdated => 0 
 	},
 
+	'bad commit' => {
+		message => q|Something bad happened while trying to commit your content. Please contact your system
+        administrator.|,
+		lastUpdated => 0 
+	},
+
 	'back to home' => {
 		message => q|Back to home.|,
 		lastUpdated => 0 

lib/WebGUI/i18n/English/WebGUI.pm

@@ -1,6 +1,28 @@
 package WebGUI::i18n::English::WebGUI;
 
 our $I18N = {
+	'skip commit comments' => {
+		message => q|Skip commit comments?|,
+		lastUpdated => 0,
+	},
+
+	'skip commit comments help' => {
+		message => q|Do you wish to be prompted to add comments to your content commits?|,
+		lastUpdated => 0,
+	},
+
+	'auto request commit' => {
+		message => q|Automatically request commit?|,
+		lastUpdated => 0,
+	},
+
+	'auto request commit help' => {
+		message => q|Would you like the system to automatically request commits for you so that you don't have to
+        remember to hit "Commit My Changes"? Note that when using this in conjunction with "Skip commit comments?"
+        and a realtime commit workflow it effectively hides the whole versioning and workflow process from users.|,
+		lastUpdated => 0,
+	},
+
 	'select' => {
 		message => q|Select|,
 		lastUpdated => 0,

lib/WebGUI/i18n/English/Workflow.pm

@@ -49,27 +49,47 @@ our $I18N = {
 		lastUpdated => 0,
 	},
 
-	'is singleton help' => {
-		message => q|If yes is selected then only one instance of this workflow will be allowed to be created at one time. Generally speaking this would be a bad idea for approval workflows, but is probably a good idea for workflows that download emails from a remote server, to avoid getting duplicates.|,
-		context => q|the hover help for the is singleton field|,
-		lastUpdated => 0,
-	},
+    'singleton' => {
+        message => q|Singleton|,
+    },
 
-	'is singleton' => {
-		message => q|Is a singleton?|,
-		context => q|A question that asks the user whether this workflow may be instanciated multiple times concurrently or not.|,
-		lastUpdated => 0,
-	},
+    'serial' => {
+        message => q|Serial|,
+    },
 
-	'is serial help' => {
-		message => q|If yes is selected then only one instance of this workflow will be allowed to be run at one time, while new instances get queued up and wait for the running one to complete. This is generally bad for a workflow, but it can be good when multiple instances of workflow have to operate on the same data.|,
-		context => q|the hover help for the is serial field|,
-		lastUpdated => 0,
-	},
+    'parallel' => {
+        message => q|Parallel|,
+    },
 
-	'is serial' => {
-		message => q|Is serial?|,
-		context => q|A question that asks the user whether this workflow may be instanciated multiple times concurrently or not.|,
+    'realtime' => {
+        message => q|Realtime|,
+    },
+
+    'mode' => {
+        message => q|Mode|,
+    },
+
+	'mode help' => {
+		message => q|The mode of a workflow determines the precidence of when and how a workflow is run.
+        <p>Parallel workflows may run as many instances of the workflow as there are in existence. This is what you 
+        want for most workflows. This mode is asynchronous.</p>
+        <p>Singleton means only one instance of this workflow will be allowed to be created at one time. Generally 
+        speaking this would be a bad idea for approval workflows, but is probably a good idea for workflows that 
+        download emails from a remote server, to avoid getting duplicates. This mode is asynchronous.</p>
+        <p>Serial means that you can create as many instances of a workflow that you like, but they will run 
+        sequentially one after the other. Two instances of the same workflow will not run a the same time. This 
+        is generally bad for approval processes, but it's good for maintenance functions or other things that need 
+        to operate on the same data. Processing sequentially will ensure that the workflows don't overwrite each 
+        other's data. This mode is asynchronous.</p>
+        <p>Realtime workflows run immediately and in parallel, meaning there can be more than one workflow of this
+        type in existence at one time and it will run at the same time as others. Realtime workflows are good for 
+        publishing operations that don't have an approval needed and other functions that you want to ensure happen 
+        immediately. This mode is synchronous. <b>NOTE:</b> Do not include any activities which may return a
+        waiting status, such as those that require human approval or an external event to occur. Doing so will
+        cause this workflow to run indefinitely and could lead to a crashed system. In addition, not all triggers
+        support realtime workflows. If they do not, then workflows with a mode of realtime won't show up in their
+        workflow select list.|,
+		context => q|the hover help for the mode field|,
 		lastUpdated => 0,
 	},