Operations in yuuvis® RAD
Operations in yuuvis® RAD have the following functions:
- System control
- System maintenance
Operations are created for report generation and e-mailing with general parameters or as tasks with specific technical parameters. For each operation, several tasks can be created with individual parameters.
Tasks can be performed directly or integrated as a task with a schedule for periodic execution.
The operations are called in yuuvis® RAD management-studio via the Main menu > Operations. They are divided into operation groups.
Several operations are created and activated as tasks with a schedule with the installation.
Users need the Manage scripts functional right to configure operations.
List of Operations
Depository operations |
Statistical database queries from file operations are cleaned up. Compares the retention period specified on a medium with the retention period in the database and adjusts the database accordingly. The cache for document files is cleaned up. The task execution history is deleted. Deleted document files are permanently deleted. Integrity check of a storage media. Nodes of a storage that has duplicates on other media are deleted. A source storage is synchronized with a destination storage. Files on media are checked. |
DMS Operations |
Deletes objects that have not been filed from users’ in-trays. Deletes objects using an eSQL statement. Cleans the recycle bin for individual users or for all users. An operation called 'Clean up recycle bins' with a value of seven days is created for all users during installation by default. Deletes access logs. |
Finalization operations |
Objects are finalized. |
Message Operations |
Notifications about subscriptions are executed. Notifications about follow-ups are executed. |
Organization Operations |
Organization data for the user administration are imported from a directory service. Organization data for the user administration are imported from a directory service. |
Repository operations |
|
Full-Text Operations |
The consistency of the index is checked. Objects are subsequently full-text indexed. The index is updated, if needed, after changes have been made to the schema, the organizational structure, the object type rights and the metadata. |
An eSQL statement is specified when configuring certain operations. You can use the actions menu to open a dialog for testing eSQL statements.
Configured Operations
The following operations are created and activated as tasks with a schedule with the installation:
-
Follow-up, Subscription, Clean up cache, Clean up history, Permanently delete files, Clean up access logs, Clean up pre-existing objects, Clean up recycle bins, Clean up security logs, Technical update.
These tasks can be edited, suspended, and deleted.