The newest point release of ArkCase version 3.2 was released on June 4th, 2018. This point version is v3.2.11. For more information, please review the release notes below.
|Dashboard - Add a Save Prompt||Dashboard - Add a Save Prompt if the user tries to navigate away from their dashboard, before losing unsaved changes.||Fixed|
|When admin user add permissions only to group, the dashboard widget is not available for adding||1: Login as user that have permissions to Admin module.
2: Click on Admin from left side menu.
3: Click on Dashboard Configuration.
4: Click on some widget for example Team Workload
5: In authorized add only one group to which logged in account is member for example ACM_ADMINISTRATOR_DEV@ARMEDIA.COM
6: Click on Dashboard from left side menu.
7: Try to add Team Workload widget.
Expected result: Widget can be clicked and added.
Actual result: Widget is not available for adding.
|When first location/phone number/fax number/email address/url/dba/id etc, "primary" should be selected by default||1: Login as user that have permissions to Organization
2: Click on Organizations from left side menu.
3: Click on Locations sublink
4: Click on "+"
Expected Result: By default only for first inserted record "Primary" is set to "Yes" and there is no possibility to select "No".
Actual Result: User can select "No".
This is how was working previously. Now user can select "No", but the record inserted is always primary.
Same happens for Phone Numbers, Fax Numbers, Email Addresses, Urls, DBAs, IDs (Works for People sublink).
Also for People module.
|FOIA - Default Initiator or Requestor Email in the Send Email Window||o The system shall automatically default the email recipient with the initiator or requesters email address every time an email is created.
The email receiptent user picker needs to search ArkCase users and people in the system.
|Create state of ArkCase report||State of ArkCase report should be created
The system shall capture the follow information in the State of ArkCase Report
o Capturing the Universal Unique ID (UUID) on startup
o Email Domain?
o How many ACM user accounts?
o How many case files total in system?
o How many documents total in system?
o Any exceptions
§ All Exceptions in application that are fired daily
|A more user-friendly error message should be provided||Implement more user-friendly error messages.
When special type delete button is clicked from the Participants table, incomprehensible notification message is displayed.
|Parent Permission bug - permission not evaluated on front-end||Parent Permission bug - permission not evaluated on front-end.||Fixed|
|"TypeError: taskCache.clear is not a function" when user click "Approve Document"||1: Login as user that have permissions to Cases module.
2: Click on Cases from left side menu.
3: Open some draft case.
4: Click on "Change Case Status" button, select some status, add approver and save it.
5: Click on Tasks sublink.
6: Click on automatic generated task.
7: Click on "Approve Document" button.
Expected Result: "Approve Document" button is removed from UI after click. Task status is changed to Closed, Case status is changed to appropriate status.
Actual Result: Console log error occurs: TypeError: taskCache.clear is not a function
|User can't activate older workflow version, row and "Make Active" button is always disabled||1: Login as user that have permissions to Admin module.
2: Click on Admin from left side menu.
3: Click on Workflow Configuration under Workflow
4: Select on third icon for some workflow with history.
5: Select some older version and click "Make Active" button.
Expected result: Older version is successfully set as active workflow.
Actual result: row can't be selected and also button is not clickable.
|500 error occurs when user try to add supervisor to ad hoc group||1: Login as user that have permissions to Admin module.
2: Click on Admin from left side menu.
3: Click on Organizational Hierarchy under Security.
4: Click on "Add/Edit supervisor" button next to some Ad hoc group.
5: Search some user and click "Add" button.
Expected result: supervisor is added.
Actual result: 500 (Internal Server Error) occurs
|Participants are not shown in Participants Grid||Cannot access participants in Participants Table for all objects (Cases, Complaints...)
Also on document level, participants grid is empty.
|Translation for Reports Module||All missing (untranslated) labels in the Reports module should be translated in different languages||Fixed|
|Translation for People Module||All missing (untranslated) labels in the People module should be translated in different languages||Fixed|
|Translation for Organization Module||All missing (untranslated) labels in the Organization module should be translated in different languages||Fixed|
|Translation for Documents and My_Documents Module||All missing (untranslated) labels in the Documents and My Documents module should be translated in different languages||Fixed|
|Translation for Time Tracking Module||All missing (untranslated) labels in the Time Tracking module should be translated in different languages||Fixed|
|Translation for Audit Module||All missing (untranslated) labels in the Audit module should be translated in different languages||Fixed|
|Create AcmAcquireObjectLock and AcmReleaseObjectLock annotations and AcmObjectLockTypes enumeration||Create AcmAcquireObjectLock and AcmReleaseObjectLock annotations and AcmObjectLockTypes enumeration||Fixed|
|Create locking interaction classes (which lock prevents another lock)||Create locking interaction classes||Fixed|
|Create Aspect to acquire and release locks||Create Aspect to acquire and release locks||Fixed|
|Annotate services throughout Arkcase code with the locking annotations||Annotate services throughout Arkcase code with the locking annotations||Fixed|
|Implement Folder locking provider||Implement Folder locking fucntionality.||Fixed|
|On some startups, no one can login due to null pointer exception in the MDC library||java.lang.NullPointerException
The issue is that ArkCase has two jar files that both include the org.apache.log4j.MDC class. One of them works fine. If the JVM happens to load the other one, this error happens.
|ArkCase full Solr re-indexing failure||On Projects, where we have huge amounts of data, doing the full Solr re-indexing quickly leads to Solr inability to process further requests.
The issue there is caused by the rate we are sending batch updates to Solr, which is much higher than Solr is able to cope with. That's why we refrain from doing full re-index, otherwise we end up with OOM errors on Solr and a lot of non-indexed data.
|Upgrade Snowbound Version 4.10||Upgrade ArkCase with Snowbound Version 4.10||Fixed|
|ArkCase Documentation||New ArkCase documentation on the Product Support Site:
1. New Form (Frevvo and HTML Forms)
2. New Workflow
3. Linking Workflow and Forms
4. Extending Data Module
5. Configuring Search Facets
6. Extend UI
|User Profile > Subscriptions - hyperlink the Title...||User Profile > Subscriptions - hyperlink the Title of the Subscription so the user can quickly navigate to the item they have subscribe.||Fixed|
|PDF.js support in core||For ArkCase customers only storing PDF files, and no annotation requirements on those PDFs, simple PDF.js embedded viewer will work better than the OOTB viewer.||Fixed|
|Increase ArkCase (Tomcat) context cache||On ArkCase projects, on application boot we are seeing log entries like the following one:
23-Mar-2018 08:04:11.023 WARNING [localhost-startStop-1] org.apache.catalina.webresources.Cache.getResource Unable to add the resource at [/resources/custom_modules/upload-new-order/views/upload-new-order.client.view.html] to the cache because there was insufficient free space available after evicting expired cache entries - consider increasing the maximum size of the cache
for almost all static resources.
This is not critical, but I increased the cache just to get rid of these