Built-in Scheduled Tasks
A set of scheduled tasks specific to the Deyel environment is described below.
Environment Scheduled Tasks
These tasks are executed as required by Deyel to ensure its proper functioning. They start automatically along with Deyel and cannot be paused by the environment administrator.
The task monitor displays their execution only when there is an error, so it can be noticed by the administrator.
Debugger for Files Uploaded to Repositories
This task is responsible for permanently deleting content that is no longer in use. For example, files or images that were contained within a form field and were replaced by another. Or files of different types that were attached to a case and are no longer so. When this task is executed, it detects such situations and deletes the contents that can be considered obsolete or unused.
Old Environment Log Debugger
This task deletes old log files. The age of the data to be cleaned can be specified in the environment configuration.
LogFilePersistence: Sets the age in days of the application log files that should be deleted by this task.
In cloud environments, this property must assume values greater than zero and less than 30. In On-Premise environments, an age greater than 30 days can be indicated. If the value is zero, files are never deleted.
Log Console Debugger
This task deletes items from the log console. The age of the data to be cleaned can be specified in the environment configuration.
LogConsolePersistence: Sets the age in hours of the log console items that should be deleted by this task. If the value is zero, items are never deleted.
Environment Temporary File Debugger
This task deletes the temporary directories of Deyel (Temp, BusinessRuleDeployment, BusinessRuleXML, EventFiles, Export, Import, IntegrationDeployment, IntegrationXML, and Upload) It executes every 24 hours, starting from the environment startup time or the scheduled tasks restart time.
Report Manager
This task ensures the execution of reports in the background and the delivery of results to the user.
User Token Debugger
This task deletes user token records for terminated sessions. It executes every 12 hours, starting from the environment startup time or the scheduled tasks restart time.
Debugger of Scheduled Task Execution History
This task deletes the execution history records of scheduled tasks.
It executes daily and considers the property ScheduledTaskHistoryPersistence, which establishes the number of days that should pass before the information is deleted.
Optional Scheduled Tasks
These tasks allow the environment administrator to activate, deactivate, or configure the execution frequency, according to their needs..
Mail Sending Manager
This task ensures the sending of emails from the various facilities of Deyel that can generate them, such as automatic email-sending actions, advanced rules, and notifications, among others. If there are connection errors with the email server, a retry scheme is implemented to overcome failures and ensure that emails are sent.
For Deyel to effectively send emails, this scheduled task must be running, and email sending must also be enabled in the environment configuration.
Mail Reader
This task generates email type events. It is initially inactive in the environment of Deyel. It should be activated when modeling processes that use this type of event. Deyel checks the receipt of emails in the account indicated in the configuration of email reception.
File Reader
This task generates File type events. It is initially inactive in the environment of Deyel. It should be activated when modeling processes that use this type of event.
This task generates alerts for activities. It is initially inactive in the environment of Deyel. It must be activated if the execution of the alerts modeled in the activities and the sending of the relevant notifications via email is required.
This task is based on business rules. It is initially inactive in the environment of Deyel and executes every 10 minutes. Its goal is to take all updates on cases and activities recorded since the last execution of this task and automatically update the information in the module of BAM (Business Activity Monitoring). The execution of this task causes both the BAM information (cases and activities in execution) and the Process Analysis information (completed cases and activities) to be updated.
Information on new or modified activities and cases is detected by this task so that it incrementally impacts the BAM module. Therefore, every 10 minutes, any change or new development is detected and transmitted to the BAM module, to obtain recent and updated information when BAM reports are displayed.
Daily Update of BAM Cases and Activities in Progress
This task is based on business rules. It is initially inactive in the environment of Deyel and runs only once a day. However, this task can be scheduled to run more frequently, such as every 4 hours, as required. Its objective is to keep the duration (execution time) and the status (delayed, at risk, on time) of all ongoing cases and activities updated, according to the frequency with which the task was scheduled: daily or every 4 hours. So, this task only includes the update of cases and activities in progress, which are not covered by the previous task that runs every 10 minutes.
For example, an ongoing case that was uploaded yesterday and was taken by the incremental update every 10 minutes will remain without updated duration and status until it is modified again and detected by the incremental load. To prevent information from becoming outdated, this task is responsible for sweeping all ongoing information and updating its duration and status. Thus, this task is complemented by the previous one to display BAM reports and obtain complete and updated information.
This task is based on business rules. Notifies users in advance of their password expiration. The administrator must trigger the execution of this scheduled task, as it is initially inactive in the environment.
Once activated, it runs daily and analyzes the configuration of the Password expiration time and Password expiration notification environment properties.
If either property is set to -1, no notifications are issued and the task ends. Otherwise, for each active user, the task calculates the alert date, which is the password expiration date minus the number of days in advance that the notification should be sent. If the calculated alert date corresponds to the current day, then the user is notified by email about the upcoming expiration of their password.
It is important to consider the configuration of the emailing so that these notifications can be issued.
