Schedule Electronic Updates  

Access

STORIS 'Server' customers (that is, not Cloud customers) can use this routine to schedule times during the week to automatically download and install system updates to your system.  STORIS recommends you update your system once a week, and perhaps more frequently in the weeks following a new release. Since to run automatic updates, all users must be logged off the system, we suggest you schedule your updates to occur during off-peak hours.

After you complete the download, you can view the data via the Automatic Updates History in the Report Builder. The report is based on the file called PACKET.LOAD.HISTORY. This data remains available for viewing until you purge it from the system based on the setting at the Automatic History Purge Days field below.  

 You must coordinate your automatic update schedule with your operating system. If you have a Windows®-based operating system, click here for more information. If you have a Unix®-based operating system, contact your STORIS representative for more information.

Day to RunThis field consists of a prompt and check box for every day of the week. Check the boxes next to the days (if any) on which you want to run automatic updates. For each day you select, you must use the associated Time Scheduled field to enter the time of day at which to run the updates. Otherwise, an error message appears and you must remove the check from any boxes for which you have not entered corresponding times.

Time ScheduledFor each day selected for automatic updates (via the Day to Run field), enter the time of day at which to run the updates. Enter the time in 24-hour format. For example, for 11:00 PM, enter '23:00'.

Automatic Updates Warning System

To run automatic updates, all users must log off the system. If you attempt to run automatic updates and all users are logged off, updates proceed immediately. However, if users are logged onto the system, STORIS issues warning messages to both the users logged on and to the user running the updates. The prompts below allow you specify three different times when you want the system to issue warning messages to users still logged on. The messages advise them to log off in the amount of time you specify.

In addition to the warning message logged-on users receive, STORIS also issues messages to the user running the automatic updates via the Automatic Updates Notification Screen. The screen displays the names of the users still logged on as well as their telephone extensions (if available). After you initiate the auto updates process, the system checks for users still logged on to the system. If no users are logged on, the system proceeds to the updates process. If users are logged on, the system issues the first warning message. The system then checks every minute for users still logged on.  When the system finds no users logged on, the updates process begins immediately.

The first warning message appears immediately after a user attempts to run automatic updates. The second and third warning messages appear in the number minutes specified at the First Warning and Second Warning fields, respectively. The automatic updates process begins in the number of minutes specified at the Third Warning field, provided all users have logged off by then. If users are still logged on, the system may bump the users off the system and proceed with the update. However, if the system senses that the user is performing an important or sensitive task (for example, entering a sales order), the system aborts the update process and retries at the next scheduled time.  

 On UNIX-based servers, users running Automatic Updates do not have permissions that allow them to bump users off the system. Users running Automatic Updates must manually ensure that all users log off.

First WarningEnter the number of minutes you want users to have before they must log off to allow automatic updates to run. This is the first of three messages you can send users advising them to log off. The message appears on the screen only of users who are logged on to the system after you initiate the Automatic Updates process.

Second WarningEnter the number of minutes you want users to have before they must log off to allow automatic updates to run. This is the second of three messages you can send users advising them to log off. The message appears on the screen only of users who are still logged on to the system after first warning appears.

Type your expanding text here.Final WarningEnter the number of minutes you want users to have to log off the system. The system logs of users still logged on after the time expires. This is the last of three messages you can send users advising them to log off. The message appears on the screen only of users who are logged on to the system after the second warning appears.

Automatic History Purge DaysEnter the number of days you want the system to save the records of the updates you imported before purging them. You can view the update data via the Automatic Updates History in the Report Builder Formerly called Query Wizard - STORIS feature used to create custom reports until you purge it. The system purges the data via the first End of Day process that occurs after the number of days you specify here have expired. Otherwise, leave the field blank.

Contact Name

Email Address

The following fields display the average length of time the Automatic Updates process, End of Month (EOM (End-of-Month) Also known as month-ending processing, an automated process you run at the end of each month to update monthly files.,) and End of Day (EOD (End-of-Day) Also known as day-ending processing, an automated process you run at the end of a business day to update daily files.), respectively, take to run based on the last seven times each was run.

Average Automatic Updates LengthThe average length of time (in minutes) it takes to run this process appears.

Average End of Month LengthThe average length of time (in minutes) it takes to run this process appears.

Average End of Day LengthThe average length of time (in minutes) it takes to run this process appears.