Jobs
Jobs can be created and used to process data stored in the online or archive repositories. Since these repositories can grow significantly over time, and due to restrictions on manipulating data while in use or at different stages of its lifecycle, directly copying, moving, or deleting storage files is not recommended.
To access the Jobs functionality:
- Navigate to Settings by pressing the settings button
in the top-right corner of the interface - Click Jobs > Jobs from the navigation menu
The Jobs page opens, displaying the list of existing jobs and providing the option to create a new one. Initially, no pre-defined jobs are available.
-
Execute a job: Click the start job
button to run a job. Job executions can be monitored in the Job Executions section. -
Delete a job: Click the delete
button next to a job. A confirmation dialog will appear to prevent accidental deletions. -
Activate/Deactivate a job: Click the status
button to enable or disable a job. Inactive jobs will not execute automatically.
An unlimited number of jobs can be created, with the primary consideration being the load their execution may impose on the solution environment. Jobs can be resource-intensive, potentially impacting the server’s processor, memory, storage, and network.
The list of existing jobs provides details on the job type, the server on which it is executed, and its active status. Further explanations of these details are provided in the section on creating a new job.
Creating a New Job
To create a new job navigate to Settings > Jobs > Jobs, click the add job 
button and the Job Configuration page will open
The following attributes are available in both Create and Edit Job configuration pages. Note that available options may vary based on the selected job type.
- Name: Enter a descriptive name that uniquely identifies the job. This name will appear in the Jobs list and execution logs.
-
Description: Provide a detailed explanation of the job's purpose and what it accomplishes. This helps with documentation and troubleshooting.
-
Server: Use the dropdown to select the target data server where the job will execute. Choose a server with adequate resources for the job's requirements.
-
Job Type: Select the type of operation to perform:
-
Import Job: Transfers events from a source repository to an online or archive repository. Import jobs are very useful for consolidation operations, or when decommissioning obsolete repositories.
-
Delete Job: Removes events from a repository to free up storage space. Common use cases include cleaning up data from obsolete applications, removing data following successful import operations, and performing compliance-driven data purges. Deletions are permanent, so proper backups and testing should be ensured before execution.
-
Copy Job: Duplicates data from one storage location to another, creating exact copies of the source data. Common use cases include creating offline backups, performing data analysis on copied datasets, and setting up testing environments with production-like data.
-
Right to be Forgotten (RTBF): Performs granular deletion of personal data based on specific criteria, supporting compliance with privacy regulations and fulfillment of data subject requests.
-
-
Data Storage: Always specifies the source data storage, regardless of job type. This is where the data will be read from during job execution.
-
Where to Import: Choose the destination for imported data:
-
Online repository: Data is extracted from the online repository and is governed by the repository’s retention period (Settings > Application Settings > Retention Period > RetentionPeriodEL). This also applies to archived data within the retention period of the online repository, for instance, when the online repository needs to be recovered after an issue.
-
Archive repository:Data is extracted from the online repository with a special tag and is subject to the RetentionPeriodArchive parameter (Settings > Application Settings > Retention Period > RetentionPeriodArchive). This applies to data older than the retention period set for the online repository, such as when data from six months ago is needed for investigation while the online repository’s retention period is only one month.
-
Configuration:
-
Check
RetentionPeriodArchiveparameter (in days) in Settings > Application Settings > Retention Period -
Ensure the parameter covers the time period of events to be extracted
-
-
To remove archived data, reduce the RetentionPeriodArchive value - data older than the new period will be automatically deleted
-
Period Spec. Type: Define the time range for job operations:
-
Start & End Date: Defines the exact date and time range for data processing. This is used when working with data from a specific period. Dates and times can be selected from a calendar or entered manually.
-
Last 'x' Units: Allows processing of the most recent data based on selected time units - seconds, minutes, hours, days, months, or years. This is useful for regularly handling recent data, for example, processing the last 7 days for weekly reports or the last 30 days for monthly data.
-
-
Active?: Enable or disable the job. Inactive jobs will not execute automatically but can still be run manually.
After configuring all attributes, click Save to create the job and add it to the Jobs list, or click Cancel to close the window without saving any changes.
For practical guidance on implementing specific job types, refer to these detailed examples:
Manage Jobs
To modify an existing job, locate it in the Jobs list, click the edit 
button, make the necessary changes on the Edit Job page, and then click Save to apply the updates and close the page.
Managing Job Executions
Go to Settings > Jobs > Job Executions. The Job Executions page opens, displaying the history of executed jobs, their results, and a summary of jobs currently in progress.
Deleting an execution from this list only has an effect if the job is still in progress. As a best practice, it is recommended to wait until an execution is complete before deleting it.