Release 3.2.5

Home » Support Library » Customer Support » 3.2 Release Notes » Release 3.2.5

The newest point release of ArkCase, version 3.2, was released on February 19th, 2018.  This point version is v3.2.5.  For more information, please review the release notes below.

 

Title Summary Resolution
New Task – Must Select an Assignee and Group to Create Task New Task – Must Select an Assignee and Group to Create Task

Steps:
1. Login to Core Dev
2. Select New Task from Global new menu
3. Search for Assignee and pick a user
4. See that the groups for that user show up, but the confirm button is already active before a group has been selected

Expected: the button shouldn’t be active till the assignee and group selections have been made.

 Fixed
Internal server error occurs 500 when user try to upload correspondence document 1: Login as user that have permissions to Cases
2: Click on Cases from left side menu.
3: Right click on root folder and Add new correspondence
4: Select some correspondence type from list.
Expected Result: Correspondence document is successfully uploaded.
Actual Result: 500 error occurs, document is not uploaded.		 Fixed
User can insert not valid email address in email field 1: Login as user that have permissions to People module
2: Click on People from left side menu.
3: Click on Email Addresses sublink under some person.
4: Click on “+” icon
5: Insert not valid address in email field, select Email type and click “Save Email” button.
Expected result:Validation message should be displayed informing that email is not valid.
Actual result: not valid email is saved.		 Fixed
Cannot update user profile picture Changing picture in user profile throws error – Uploading picture failed (500-Internal server error) Fixed
Document Level – ACL Implementation Document-level security is already working from a service perspective, so first we need to identify what is missing that needs to be added.

Like all objects, first the parent security is evaluated, so you can only see documents for case files, tasks, and complaints you can see. Do we want to allow access to child objects when the parent is not accessible? If so this should be governed by policy.

I believe the user interface may need fixing so you can actually set participants on files. Also we have no default assignee or access rules for files. But once the participants are set, the access controls are applied, within the scope of the parent object as I said above.

 Fixed
Missing some label configurations for event names when adding participants on documents 1: Login as user that have permissions to Cases.
2: Click on Cases from left side menu.
3: Click on Documents sublink.
4: Right click on some document and click Open.
5: Click on Participants tab.
6: Add new participant.
7: Refresh page and click on Event History page.
Expected result: New event is added for added participant with name that is configured in label configuration.
Actual result: Label Id is displayed instead of value		 Fixed
Allow admin to trigger differential or full sync on demand From admin module an admin user should be able to trigger differential ldap sync. Fixed
LDAP User Management 3-panel view – search/filter functionality Implement Search/Filter functionality on LDAP User management 3-panel view Fixed
When creating new Costsheet, status field is empty (not editable) …it should be predefined as “Draft” 1: Login as user that have permissions to Cost Tracking
2: Click on New/Costsheet
3: Select Case or Complaint in Type
4: Click on Code
5: Search some case/complaint id, select it in grid and click “OK” button
Expected result: Status drop down is filled with “Draft” status.
Actual result: Status drop down is empty.		 Fixed
Issue loading ArkCase home page (Dashboard) in Internet Explorer After sucessfull logging in the log-in page application (Dashboard page) is not loaded in Internet Explorer.
Works fine in Chrome.		 Fixed
Hyperlink in email doesn’t redirect to file, 500 error occurs 1: Login as user that have permissions to Cases.
2: Click on Cases from left side menu.
3: Click on Documents sublink.
4: Right click on some document and click Email.
5: Insert some email address, select “Send Email with Hyperlink ” and click “Send Email.”
6: Open hyperlink in received email.
Expected result: file is opened in browser.
Actual result: 500 error occurs		 Fixed
Cannot upload document on root folder due to Document ACL There is a problem uploading document on the ROOT folder in document repository for any object (Case, complaint…). Creating sub-folders and Uploading documents in the sub-folder works fine. There is an issue only for Root folder Fixed
Preference – Module Name need to be control by Admin Labels Preference – Module Name need to be control by Admin Labels Fixed
Cannot create folders in Alfresco When creating a subfolder in /Sites/rm/documentLibrary/ACM/ (also another place) we get an error, see the attachment.
This is Alfresco installation in our docker container		 Fixed
Drag and Drop into Document Management Files Section Issue Drag and Drop into Document Management Files Section Issue

– When a user drags and drops a file from a location outside of ArkCase, they can drag to the folder level, which creates the document as a new file in that folder and that works now.
– The issue is when a user drags a document to the files, it prompts the user to ‘replace’ or ‘create new’ and those options don’t function.
– I want to change that modal box to the standard create new modal box that works, no matter whether the user drags to the folder level of files section of the document management

 Fixed
Description entered from new case form is not displayed in the created case Steps to reproduce:

1. Go to new case page
2. Fill in all necessary fields and enter some description.
3. Submit the new case
4. Go to details section of the created case

 Fixed
When user click on “+” to add new task under case/complaint, there is spinner in “Save Task” button 1: Login as user that have permissions to Cases/Complaints
2: Click on Complaint s link from left side menu.
3: Click on Tasks sublink.
4: Click on “+” in grid.
Expected result: Spinner icon should be not displayed since the user haven’t clicked “Save” .
Actual result: spinner icon is displayed in “Save Task” button.		 Fixed
When user create group with {, ( or & in name without empty spaces between, the group can’t be expanded 1: Login as user that have permissions to Admin module
2: Click on Admin from left side menu.
3: Expand Security/Organizational Hierarchy
4: Add new group with brackets or “&” in it. (For example (TEST), {TEST} or TEST&TEST – don’t leave empty spaces in group name
5: Add some member to added groups.
6: Refresh page.
7: Try to expand added groups.
Expected result: Groups are successfully expanded and members can be viewed.
Actual result: Exception occurs, groups are not expanded.		 Fixed
Report of Investigation form is cut in right top and down corner 1: Login as user that have permissions to Cases.
2: Click on Cases from left side menu.
3: Click on Documents sublink.
4: Right click on folder and click Add/New Document
5: Select Report of Investigation.
Expected Result: Report of Investigation form is displayed and is not cut in right top and down corners.
Actual result: Form is cut in top and down right corners.		 Fixed