Administrative Scheduled Downtime

During administrative scheduled downtime, invoices are prevented from being imported to the ERP system, and optionally users are not allowed to log in.

There are two configuration parameters that can enable a system downtime, one for the entire site/application, and another that schedules administrative downtime for a particular organization.

To schedule a downtime, create a parameter setting, set the parameter the value to Y and define Start Date and End Date. The administrative downtime is in effect in the defined period. If you omit an end date, the administrative downtime is permanent, until an end date is defined. This is true even if the parameter value is changed to N.

Disable User Access

The configuration parameter Disable user access during scheduled downtime controls whether users can log in during scheduled system downtime. The default value is Yes, meaning that access is disabled during downtime. This means that:

If the parameter is set to N, then:

Disabling user access onlt defines user access permissions during downtime. You still need to schedule an administrative downtime period using the parameters mentioned above.

Access During Scheduled Downtime

If you attempt to access PROCESSIT during scheduled down-time periods for Site level, and access is disabled during downtime, you receive a message telling you that the system is not currently available due to administration purposes.

When Downtime is specified for a particular Organization, users can still log in to the system, but are denied access to any tasks belonging to the particular organization.

Invoices being held from import or inserted in the interface tables during Administrative Downtime rechecks downtime status every 5 minutes and automatically continue once the downtime ends.

Access via email link during downtime

If a downtime is active, all users attempting to access the application via an email message are forced to the login screen, regardless of email notification security settings. Admin users are able to login, while standard users are denied access.

Working when Downtime begins

If a user is already active in the system once the downtime starts, they can finish the current task, but cannot open another invoice task once the downtime is active.

If the user had already started processing a task before the downtime started, they will be able to complete it but will not be able to start any new tasks from an email message