2024/10/30

Update Release (October 2024 Version)

We have released an updated version of CORRESSA (October 2024 Version).


We have released an updated version of CORRESSA (October 2024 Version). This update includes the addition of an internal review function for document management, workflow enhancements, and other enhancements in response to customer requests. The details are as follows.


General

  • Release Version: Ver. 4.297

[CORRESSA Correspondence]

  • Changed the "Save" Button on the Correspondence to the "Save Draft" Button
    Many users mistakenly believed that pressing the save button would issue the correspondence on saving correspondence. Therefore, we have renamed the “Save” button to “Save Draft.”
    *Please note that this feature has already been released to some customers.

[CORRESSA Document Management]

  • [Document Kanban] [Bulk Issuance of Documents] Interchangeable Screens
    We have added a button that enables switching between the document issuance routes of Kanban for Documents and Bulk Issuance of Documents. This makes screen switching more convenient.
    *Please note that this feature has already been released to some customers.
  • [Document Kanban] Additional Option to Show/Hide Previous Version Documents in View Settings
    We have added an option in the view settings to show or hide previous version documents.
  • [Document Kanban] Internal Review Function
    We have added a new feature that allows multiple internal users to input and record review results for documents. The internal review function can be configured during document registration, issuance, and return.
    Reviewers can be pre-set by the system administrator within designated reviewer groups, and users can also add reviewers as needed. The input of review results by reviewers can be set as optional or mandatory.
    If a workflow is configured, it will be executed after the completion of the internal review. In addition, the internal review function can be enabled or disabled in the company settings in the project settings.

corressa_InternalReview

  • [Document Kanban] Sharing Settings on Document Issuance
    When issuing a document, you can specify a company or group as a CC to grant access permissions to the document. Notification emails will be sent to the users within that company or group.
    Within this sharing setting function, it is possible to grant access permissions without sending notification emails. At the time of document issue, the CC can be selected and specified simultaneously.

corressa_IssueShare

  • [Document Kanban] Comment Notification to Document Issuers
    In the document comment feature, users can use the “@” mention to send notification emails to specific users and groups. However, we received feedback that issuers might miss comments if no mention is set. In this regard, we have updated the system to automatically send notification emails to the individual responsible for issuing the document (the user who executed the sending), regardless of the presence of mentions. Furthermore, comments on documents before issuance will automatically send notification emails to the creating department.

[CORRESSA File Sharing]

  • Bulk Download File Size
    In file sharing, when downloading multiple files or folders, a background process compresses them into a ZIP file. An email is sent once the files are ready. We have changed this process so that if the total file size is 10MB or less, the ZIP file will be available for immediate download, while the background process continues for files exceeding 10MB.

[CORRESSA Administrator Functions]

  • Deletion of Groups
    Previously, if a user within a group was the creator of a correspondence or document in an ongoing project, the user could be deactivated but not removed from the group, preventing the group’s deletion. We have now modified the function to allow group deletion regardless of whether users exist within the group.

[CORRESSA General]

  • Workflow Enhancements
    Workflows previously required “target functions” and “type,” however, these have been changed to optional settings. This allows workflow definitions to be applicable across multiple features rather than being restricted to specific ones like correspondence or document management. If a target function is specified without a type, the workflow can be used for all types within the specified function.
  • Global Workflow
    Workflows were required the creator, reviewer, and approver to belong to the same group. We have introduced a new type called “Global Workflow,” which allows reviewers and approvers to be selected even if they do not belong to the same group as the creator.
  • One-Time Workflow
    Workflows had to be predefined in the project settings. We have added a “One-Time Workflow” feature that allows specifying reviewers and approvers at the time of approval request, which can be enabled or disabled in the company settings.
  • Alert for Operations on Non-Current Projects
    The current project is the project that the user is logged into and actively working on. If operations are conducted on a project different from the current one (such as registering a document or submitting an approval request in a workflow), it may disrupt the sharing settings of the data. To prevent this, we have added a feature that displays an alert when performing operations on non-current projects, prompting users to explicitly switch projects.
    For example, if you are working on Project A and receive a notification email for a correspondence in Project B, clicking the link will open the correspondence in a new browser tab, changing your current project to Project B. Returning to incomplete work on Project A could result in errors. With this feature, an alert will prompt you to switch projects, and by refreshing the screen and reselecting the intended project, the project context will switch accordingly.