Skip to main content
Version: 2025 R1

Schedules

Configuration of schedules, i.e. the start times of the individual services in WEBCON BPS.

info

All dates should be specified in the time zone of the database (UTC +01:00).

Schedules

1. KPI time refresh​

The times at which the service will activate generation of statistical analyses for individual steps. You can edit the values using the Add and Delete buttons.

2. Time of currency rates download​

The times at which the service will update the table of exchange rates. You can edit the values using the Add and Delete buttons.

3. Substitution activation time​

The times at which the service will start task delegation substitutions in WEBCON BPS. You can edit the values using the Add and Delete buttons.

info

For more information on Task delegation substitutions, see THIS ARTICLE on our technical blog.

4. Data source​

The data source to be used when downloading the currency exchange rates.

Example

The National Bank of Poland option indicates the rates published to the official NBP API endpoint.

Note that exchange rate data sources will differ in data availability (some publish average prices, others only ask/bid prices etc.) and pricing system (direct/indirect quotation).
If there is no proxy, the synchronization with ECB is possible through port 443.

5. Rate download starting from​

The date from which exchange rates are to be loaded.

Example

For 01/01/2005 the rates will be loaded from the year 2005 up until the current day.

Maintenance plan​

Define any number of time frames during which the workflow service will enter an idle mode.
During this time, maintenance can be easily performed without receiving a series of error messages regarding the service not working as intended.

Maintenance plan

1. Night hours​

To reduce the load of the server on which certain operations are performed, WEBCON BPS makes it possible to run these operations at night. The configuration of the night hours allows you to create a flexible definition of hours, adjusted to the time when the server load is minimal.
The operations that can be performed during night time include:

  • timer actions,
  • asynchronous adding of text layers on attached scans (OCR).

Night hours are counted from the day and Start time specified, until the End time (which may be the following day, if the time period includes midnight).
Hours are defined using the 12-hour (AM/PM) clock.
The time frames are additive if they overlap.

Example

When defining:

  • Monday, 3:00 PM; 6:00 PM,
  • Monday, 5:00 PM; 1:00 AM,
    means that the Night hours period will last from Monday 3:00 PM until Tuesday 1:00 AM.

2. Service hours​

This functionality has been put in place to define a time frame in which the workflow service goes into idle mode. This allows for planned maintenance, (for example: Database backup) without the service registering copious amounts of errors during its period of unavailability.

  • Multiple time frames can be defined.
  • A time frame may be defined with an accuracy to the minute,
  • A time frame may be defined individually for each day of the week,
  • Time frames are defined globally for all services configured in the system,
  • By default, no Maintenance hours are defined (the service is continuously active).

3. Database maintenance hours​

During maintenance hours, the specified entries are deleted from the relevant database tables.

Synchronization​

Allows you to set the time intervals at which service will perform the BPS user list synchronization. You can edit the values using the Add and Delete buttons.

Synchronization

1. Hours during which full user synchronization is activated​

All user and group data is loaded and updated, regardless of changes. A full synchronization may be much more time consuming than an incremental one. Therefore, full synchronizations are recommended in special cases only.

2. Hours during which incremental user synchronization is activated​

User and group data is updated differentially. This means that only objects (users or groups) whose properties have changed since the last synchronization will be updated. Incremental synchronization also updates the state of modified and deleted objects. For performance reasons, this is the recommended default synchronization type.