Scheduler - Revision history

Rkahn: /* Overview */

2011-10-04T20:47:10Z

‎Overview

2011-10-03T15:52:40Z

2011-10-03T15:51:55Z

2011-09-27T19:41:19Z

‎Code Update - 2011-09-27

2011-09-27T19:40:21Z

‎Code Update - 2011-09-27

2011-09-27T17:45:19Z

‎Code Update - 2011-09-27

2011-09-27T17:11:00Z

‎Code Update - 2011-09-27

2011-09-27T17:07:40Z

‎Code Update - 2011-09-27

2011-09-27T17:06:06Z

‎Code Update - 2011-09-27

2011-09-27T17:05:17Z

‎Code Update - 2011-09-27

@@ Line 1: / Line 1: @@
 == Overview ==
-TODO - Write overview.
+The scheduler is used to run a series of commands in different server requests. This prevents too much load on the server and allows a long process to have a progress bar instead of simply waiting for the page to load forever. The scheduler can call commands/urls and has the ability to set a wait interval between batches. It also has the ability to render a pause/resume button along with a progress bar.
 == Code Update - 2011-09-27 ==

@@ Line 1: / Line 1: @@
-__NOTOC__
+== Overview ==
 == Code Update - 2011-09-27 ==
@@ Line 92: / Line 90: @@
 It will render a progress bar and give you the ability to pause/resume the process.

@@ Line 25: / Line 25: @@
 <pre>
 NOTE: Using the getSchedulerVars() method call from within Apps and Site Code will insure
 that your code remains compatible even if this variable name changes or is moved in the future.
 <!-- Also this scheduler variable may be included in a common ADF variable scope
 location along with other application level ADF variables that are stored outside of the
 standard 'application.ADF' scope.-->
 *It is recommended that you update any App code that uses the Scheduler to reflect these changes before the ADF 1.5 truck code is updated with these updates.

@@ Line 7: / Line 7: @@
 == Code Update - 2011-09-27 ==
 <pre>
-!!! IMPORTANT: NEW CODE UPDATE MAY BREAK CURRENT SCHEDULER IMPLEMENTATIONS !!!
+!!! IMPORTANT: UPDATE MAY BREAK CURRENT SCHEDULER IMPLEMENTATIONS !!!
 </pre>

@@ Line 23: / Line 23: @@
 Now to access the task information stored within the 'application.ADFscheduler' variable from within your Apps and/or Site code it is a '''best practice''' to call this Scheduler LIB method: application.ADF.scheduler.getSchedulerVars();
-<pre>NOTE: Using the getSchedulerVars() method call from within Apps and Site Code will insure
+<pre>
 that your code remains compatible even if this variable name changes or is moved in the future.
-Also this scheduler variable may be included in a common ADF variable scope
+<!-- Also this scheduler variable may be included in a common ADF variable scope
 location along with other application level ADF variables that are stored outside of the
-standard 'application.ADF' scope.</pre>
+standard 'application.ADF' scope.-->
 *It is recommended that you update any App code that uses the Scheduler to reflect these changes before the ADF 1.5 truck code is updated with these updates.

← Older revision	Revision as of 15:51, 3 October 2011
(No difference)

@@ Line 23: / Line 23: @@
 Now to access the task information stored within the 'application.ADFscheduler' variable from within your Apps and/or Site code it is a '''best practice''' to call this Scheduler LIB method: application.ADF.scheduler.getSchedulerVars();
-NOTE: Using the getSchedulerVars() method call from within Apps and Site Code will insure that your code remains compatible even if this variable name changes or is moved in the future.
+ NOTE: Using the getSchedulerVars() method call from within Apps and Site Code will insure that your code remains compatible even if this variable name changes or is moved in the future.
 Also this scheduler variable may be move to be included in a common ADF variable scope location along with other application level ADF variables that are stored outside of the standard 'application.ADF' scope.

@@ Line 20: / Line 20: @@
 #Reduces the risk of conflicting with other custom code
 #Added a getSchedulerVars() method
-**Now to access the task information stored within the 'application.ADFscheduler' variable from within your Apps and/or Site code it is a '''best practice''' to call this Scheduler LIB method: application.ADF.scheduler.getSchedulerVars();
 NOTE: Using the getSchedulerVars() method call from within Apps and Site Code will insure that your code remains compatible even if this variable name changes or is moved in the future.