TABLE OF CONTENTS

Explanation of terms

The history feature chronologically records actions and events in the system. This allows users to track workflows, communication history, and process progress.


Configuration

The history fills automatically. It cannot and does not need to be configured.


System behavior

  • History Data
    History entries include data such as:
    • Performed action
      e.g., an attachment was created, a message received, feedback given, or publication "XYZ" created.
    • Additional information
      e.g., links to system elements and emails, messages, and comments.
      For example, a link to an email sent to an applicant can be displayed, allowing users to track when and with what content the message was sent.
    • Date and time of the action or event
    • Trigger of the action or event
      e.g., user, system, applicant, API user.
  • System Areas with History
    • d.vinci Applicant Management

      The d.vinci applicant management system includes history records in the following areas:

    • d.vinci Onboarding

      The d.vinci onboarding system includes history records in the following areas:

  • Distinction from the Change Log
    While the history records events such as messages or performed actions, the change log specifically documents changes to system elements. For example, the change log records when user settings have been modified, whereas the history documents that an email related to an application has been received.


How our customers use this

Our customers primarily use the history feature to track important steps in the application and onboarding process. Some examples:

  • Tracking the application process: Many customers use the history to review the progress of individual applications, ensuring that emails have been answered or specific steps completed.
  • Checking communication: The history helps review the flow of messages and track whether messages were successfully delivered and processed.

Further articles on this topic