Reports

The following reports are available.

Infected Documents

A virus scan is carried out regularly. Here you will find a list of all infected documents of your organization.

Failed Background Tasks

Background tasks are used to execute actions at a specific point in time. If a background task could not be executed successfully (for example, if the object concerned is locked), the system tries to execute the background task again later. After ten unsuccessful attempts, the background task is suspended and no longer executed automatically. App administrators are informed by e-mail about suspended background tasks in the context of an app. Otherwise, the organization administrators are informed by e-mail.

You can perform the following manual actions for background tasks:

• Define Next Execution (only visible if you have full control on the object)
  Defines a time at which the background task is executed again.
• Send Link
  The background task can be forwarded to a user with appropriate access rights.
• Delete (only visible if you have full control on the object)
  Deletes the background task on the affected object. The task is no longer executed.

E-Mail Dispatch Errors

If the Log E-Mail Dispatch Errors option is enabled in the SMTP settings (organization > “Advanced Settings” > “Define SMTP Settings”), a dispatch error is stored for e-mails that cannot be sent successfully in the background.

You can perform the following manual actions for e-mail dispatch errors:

• Send Test E-Mail
  You can send a test e-mail to a freely definable recipient.
• Resend E-Mails
  You can resend the e-mails associated with the dispatch error. You can see the recipients affected in the Error Messages field. As soon as all e-mails have been sent successfully, the e-e-mail dispatch error is deleted.
• Delete
  Deletes the e-mail dispatch error.

Note:

• If more than 20 dispatch errors occur in two hours, logging is suspended for two hours. . If “Resend E-Mails” has been carried out successfully, logging may also be resumed prematurely.
• The “E-Mail Dispatch Errors” area is only displayed if the Log E-Mail Dispatch Errors option is enabled or an e-mail dispatch error already exists.
• E-mail dispatch errors that occur in the context of an app configuration are also displayed in the corresponding app configuration.

Reports on Unused Teamrooms

The “Create Report” button can be used to identify unused Teamrooms. Teamrooms are considered unused if they were created and last changed before the specified period of time and no access has taken place since that time. The accesses are determined on the basis of the audit log.

With the “Request Teamroom Administrators to Review” action, Teamroom administrators can be requested by e-mail to review the unused Teamrooms and delete old, no longer needed data, if applicable.

Teamroom administrators have the following options via the link in the e-mail:

• “Reviewed” or “All Teamrooms Reviewed” button respectively
  Teamrooms can be marked as “Reviewed”. You can specify a date until which the Teamrooms are to be excluded from the reports (one year by default). If the date is removed, the Teamroom will be checked again for the next report.
• “Dissolve” button
  Teamrooms that are no longer needed can be dissolved directly.