Feature - Deferred Processing Multiple Times Per Day

Feature - Deferred Processing Multiple Times Per Day

Release date: 03/31/2016

Some reports may need to be run multiple times each day.  Prior to this release, a separate deferred process had to be created for each time during the day that the report needed to be run.  This new feature allows for running a deferred report multiple times per day, at specified intervals within a specified time frame, all in one deferred process:



In the example above, the report will be run every 15 minutes between 7:00am and 5:30pm, Monday through Friday.  

You can specify minutes between running as low as 1 and as high as several hours (e.g., 120 is 2 hours).

Military times are specified, between 00:00 and 23:59.  The stop time must be greater than the start time.  If, for example, you want to schedule a report between 4:00pm and 2:00am the next morning, you need to set up two of these daily deferred processes, one repeating between 16:00 and 23:59 and one between 00:00 and 02:00.

If the report is generated many times per day, you may wish to consider modifying EL800U.CFG to separate these reports from others.  See the Knowledge Base article titled Feature - Automatic Archiving of Spooled Reports in Elliott v8.0.

Modified programs: BIDRPTW, BIDRPTM, NWSMDFRP, NWSMRPTP
JEG


    • Related Articles

    • Deferred Processing Icon Disappears from Task Tray and Multiple Deferred Sessions Are Running

      Release Date: 03/04/21 Modified Date: 02/08/24 Version: 7.5 & Up Q - Our Deferred Processing icon is disappearing from the task tray in the desktop bottom right corner. As a result, we thought Deferred Processing was not running and launched Deferred ...
    • Run Time Error 166 in Deferred Processing

      Release Date: 2/16/2022 Version: 7.5 & Up Q - I couldn't find documentation about error 166. Our deferred processes locked and had this error. Can you provide any information about what this message means? EL850RP.EXE - COBOL Text Window Execution ...
    • Btrieve Error 80 In Deferred Processing

      Q - In Deferred Processing, we encounter the following error: Btrieve Error 080 on Order Header File This has been happening for the last 30 days off and on. What might cause this to happen? A - This is what Btrieve Error 80 means based on PSQL ...
    • The Run Local or Hybrid Feature in Elliott 8.5

      Release Date: 12/3/2018 In Elliott 8.5, you can run Elliott in three different modes based on the location from which you execute Elliott application programs: Run Local: This is the recommended default method. Run Hybrid: This is designed to run for ...
    • Feature - Prompt ACH Deposit Effective Date to Avoid Non-Business Day

      Release Date - 3/14/16 Version: 8.2 & Up The purpose of this feature is to give the user the option to enter the ACH Effective Entry Date. This date defaults to the system date plus one day when you create the NACHA file. As a result, this day may ...