Release v3.1.23

Summary Description Resolution
Created Case is not displayed in the Cases list 1. Log into the application
2. Click on new button
3. Click on case button
4. Fill in the mandatory fields and click save

The created case is not displayed in the cases list

Fixed
Sometimes the EcmFile CMIS versionSeriesId is an objectId instead While working on the ECMS demo site, I noticed some EcmFile records have a CMIS object ID where there should be a versionSeriesId. These EcmFile’s cannot be declared as records – the RMA integration requires a real versionSeriesId, not an objectId.

From looking at the code, it can only happen when a file is moved.

Steps to reproduce:
# Login to ArkCase as a user with rights to upload files to some case file
# Upload a file to a case file
# Move the file to some other folder
# Declare the file as a record

Expected: When you refresh the doc tree, the file still has RECORD status.

Actual: the file has ACTIVE status.

Fixed
Failed to create CASE/COMPLAINT Creating case fails due to rule: 35 in drools-assignment-rules. Note: Creating case/complaint is tested on empty database. Fixed
Primary People in Organizations 1. Log into the application
2. Click on Organization in the sidebar
3. Click on People sublink
4. Click on “+” icon.
5. Insert all required fields and click the “Yes” radio button of ” Set as primary ”
6. Click the Save person button

The person is added but “primary” label is not displayed in the people table

Fixed
Bad presentation in the Grid with selection field (check-box) Please check Grid component with “selection” column, like screen shots attached. There are probably other places
Row selection is not displayed in line for all columns.
Check-box icon (/) should be displayed instead of “…”
Fixed
Organization – Top Ribbon -Labels not aligned Please check the alignment of the labels on the header (top ribbon) on the Organization module. Fixed
Even though complaint title is mandatory, user can delete it 1: Login as user that have permissions to Complaints module
2: Click on Complaints link from left side menu.
3: Click on Complaint title
4: Clear the title and click checkmark.
Expected result: Notification message is displayed that complaint title is mandatory and can’t be empty.
Actual result: Complaint title is updated with empty value.
Fixed
Ad-Hoc Task Edit Assignee 1. Log into the application.
2. Click on the New button at the top of the screen.
3. Click on Task.
4 .Click on Assign To field.
5. Search for user (Ann) and click Confirm.
6. Search for user’s group (ACM_ADMINISTRATOR_DEV) and click Confirm button.
7. Fill in necessary fields and click Save task button.
8. Navigate to the created task and click the assignee name (In the information ribbon )
9. Search for user that’s not belongs to that group (e.g Samuel) (bug)

Searched users that does not belongs to that group is displayed and can be assigneed to the task, although the task belong to the ACM_ADMINISTRATOR_DEV group. Sam does not belong to that group

Fixed
FOIA – changes to requester information are not saved Any changes to requester data on the FOIA request details page are not saved. Request-level fields are saved OK, but any requester changes are not persisted. Fixed
Admin services should always close properties files In working on AFDP-3520 I found that the admin services don’t always close file input and output streams. With the below command on cloud.arkcase2021.arkcase.com (10.21.14.172) I can see many open file handles on applicationRolesPrivileges.properties…. although I can’t duplicate the leak anywhere else… but still all file streams should always be closed.

sudo ls -ltrh /proc/$ARKCASE_PID/fd | grep -i applicationRolesPrivileges.properties | wc -l

Fixed
Make Ad Hoc usergroup Names more user friendly Current display name for Ad Hoc usergroups are not user friendly since we are displaying their unique names containing the group id from the DB.

At this moment display name looks like this: Add – Hoc Group-UUID-7c186f10-66fb-11e7-bc94-b65c70efc050

As a user I would like more user friendly names, since the names are not unique I would like to see group name contained in path where it is located.

Fixed
Unclaiming a task doesn’t remove the ‘assignee’ participant, nor update the task’s solr data From PAHO-672:
{quote}
In test, log in as fda.begypt.

View tasks. Unclaim icon is shown on tasks that show an Active status (I thought there was an Unclaimed status ?)

Go to an active task. Click Claim.

Wait a while, click Unclaim

No unclaim icon shows on dashboard. .

Open the task again, Unclaim button is back.

Status is not updating?
{quote}

Tasks Solr data and listed ‘Assignee’ participants are not updated to show that there is no assignee for the task. Only the assignee field on the task object itself is removed. Solr still lists the previous assignee id and full name information

Replicated on Core with Task 9021: https://core.arkcase.dev.armedia.com/arkcase/home.html#!/tasks/TASK/9021/main

Solr data after unclaiming: !image-2017-07-11-14-00-04-914.png|thumbnail!
UI for Task showing that it should be unclaimed: !image-2017-07-11-14-01-17-640.png|thumbnail!
Browser Console demonstrating the Participants, listing the former assignee of the task: !image-2017-07-11-14-03-47-766.png|thumbnail!

The task is still listed on the Task list under the ‘Tasks for me’ filter, as well.

Fixed
Rename “Change Outlook Password” to “Store Outlook Password” Since we are only storing user Outlook password and not actually updating it directly on Outlook server, it would improve user experience if we rename the functionality to “Store Outlook Password”. Fixed
Organizations – Overview Widgets Need to create and add the below widgets to the Organizations module and the preference section. The widgets for this module should show in the below order on the Overview page in the Organizations module and in the Preference list under Organizations.

New Overview Widgets to be added:
– Locations
– X Axis = Row (Data)/ Y Axis = Columns (Address, Date Last Modified, User Last Modified)

– Phone Numbers
– X Axis = Row (Data)/ Y Axis = Columns (Type, Phone Number, Modified By, Last Modified)

– Fax Numbers
– X Axis = Row (Data)/ Y Axis = Columns (Fax Type, Fax Number, Modified By, Last Modified)

– Email Addresses
– X Axis = Row (Data)/ Y Axis = Columns (Email Address Type, Email Address, Modified By, Last Modified)

– URLs
– X Axis = Row (Data)/ Y Axis = Columns (Type, URL, Modified By, Last Modified)

– DBAs
– X Axis = Row (Data)/ Y Axis = Columns (DBA, Type, Modified By, Last Modified)

– People
– X Axis = Row (Data)/ Y Axis = Columns (First Name, Last Name, Organization)

– IDs
– X Axis = Row (Data)/ Y Axis = Columns (Type, ID, Number, Modified By, Last Modified)

– Complaints
– X Axis = Row (Data)/ Y Axis = Columns (ID, Title, Status, Assignee, Modified)

– Cases
– X Axis = Row (Data)/ Y Axis = Columns (ID, Title, Status, Assignee, Modified)

– Related Organizations
– X Axis = Row (Data)/ Y Axis = Columns (Relationship, Organization, Type, Primary Contact)

Confirm the Order of Widgets for Organizations Module is in the order of the list below:
1. Details
2. Locations
3. Phone Numbers
4. Fax Numbers
5. Email Addresses
6. URLs
7. DBAs
8. People
9. IDs
10. Complaints
11. Cases
12. Related Organizations
13. History

Fixed
People – Overview Widgets Need to create and add the below widgets to the People module and the preference section. The widgets for this module should show in the below order on the Overview page in the People module and in the Preference list under People.

New Overview Widgets to be added:
– Pictures
– X Axis = Row (Data)/ Y Axis = Columns (Thumbnail, Filename, Description)

– Locations
– X Axis = Row (Data)/ Y Axis = Columns (Address, Date Last Modified, User Last Modified)

– Phone Numbers
– X Axis = Row (Data)/ Y Axis = Columns (Type, Phone Number, Modified By, Last Modified)

– Email Addresses
– X Axis = Row (Data)/ Y Axis = Columns (Email Address Type, Email Address, Modified By, Last Modified)

– URLs
– X Axis = Row (Data)/ Y Axis = Columns (Type, URL, Modified By, Last Modified)

– Aliases
– X Axis = Row (Data)/ Y Axis = Columns (Alias, Type, Modified By, Last Modified)

– Organizations
– X Axis = Row (Data)/ Y Axis = Columns (Role, Organization Name, Organization Type)

– IDs
– X Axis = Row (Data)/ Y Axis = Columns (Type, ID, Number, Modified By, Last Modified)

– Complaints
– X Axis = Row (Data)/ Y Axis = Columns (ID, Title, Status, Assignee, Modified)

– Cases
– X Axis = Row (Data)/ Y Axis = Columns (ID, Title, Status, Assignee, Modified)

– Related People
– X Axis = Row (Data)/ Y Axis = Columns (Relationship, First Name, Last Name, Organization)

Confirm the Order of Widgets for People Module is in the order of the list below:
1. Details
2. Pictures
3. Locations
4. Phone Numbers
5. Email Addresses
6. URLs
7. Aliases
8. Organizations
9. IDs
10. Complaints
11. Cases
12. Related People
13. History

Fixed
Tasks – Overview Widgets Need to create and add the below widgets to the Tasks module and the preference section. The widgets for this module should show in the below order on the Overview page in the Tasks module and in the Preference list under Tasks.

New Overview Widgets to be added:
– Rework Details
– X Axis = Row (Data)/ Y Axis = Columns (Rework Details, Date Last Modified, User Last Modified)

– Documents Under Review
– X Axis = Row (Data)/ Y Axis = Columns (Title, Created, Author, Status)

– Parent Documents
– X Axis = Folder Name(s)/ Y Axis = Count of document in that folder

– Tags (Same widget as the ones in AFDP-3836, AFDP-3837, AFDP-3839, AFDP-3840, AFDP-3841, AFDP-3842)
– X Axis = Row (Data)/ Y Axis = Columns (Tag, Created, Created By)

Confirm the Order of Widgets for Tasks Module is in the order of the list below:
1. Details
2. Rework Details
3. Documents Under Review
4. Parent Documents
5. Documents
6. Notes
7. References
8. Workflow Overview
9. History
10. eSignature
11. Tags

Fixed
Case Files – Overview Widgets Need to create and add the below widgets to the Case Files module and the preference section. The widgets for this module should show in the below order on the Overview page in the Case Files module and in the Preference list under Case Files.

New Overview Widgets to be added:
– Organizations (Same widget as the ones in AFDP-3637, AFDP-3843)
– X Axis = Row (Data)/ Y Axis = Columns (Role, Organization Name, Organization Type)

– Tags (Same widget as the ones in AFDP-3836, AFDP-3838, AFDP-3839, AFDP-3840, AFDP-3841, AFDP-3842)
– X Axis = Row (Data)/ Y Axis = Columns (Tag, Created, Created By)

– Approval Routing (Same widget as the one in AFDP-3637)
– X Axis = Row (Data)/ Y Axis = Columns (Title, Assignee, Due) – Need a column for each assignee

Confirm the Order of Widgets for Case Files is in the order of the list below:
1. Details
2. People
3. Organizations
4. Documents
5. Participants
6. Notes
7. Tasks
8. References
9. History
10. Time
11. Cost
12. Tags
13. Calendar
14. Approval Routing

Fixed
Compliant – Overview Widgets Need to create and add the below widgets to the Complaint module and the preference section. The widgets for this module should show in the below order on the Overview page in the Complaints module and in the Preference list under Complaints.

New Overview Widgets to be added:
– Organizations (Same widget as the ones in AFDP-3637, AFDP-3843)
– X Axis = Row (Data)/ Y Axis = Columns (Role, Organization Name, Organization Type)

– Tags (Same widget as the ones in AFDP-3837, AFDP-3838, AFDP-3839, AFDP-3840, AFDP-3841, AFDP-3842)
– X Axis = Row (Data)/ Y Axis = Columns (Tag, Created, Created By)

– Approval Routing (Same widget as the one in AFDP-3637)
– X Axis = Row (Data)/ Y Axis = Columns (Title, Assignee, Due) – Need a column for each assignee

Confirm the Order of Widgets for Complaints is in the order of the list below:
1. Details
2. Locations
3. People
4. Organizations
5. Documents
6. Participants
7. Notes
8. Tasks
9. References
10. History
11. Time
12. Cost
13. Tags
14. Calendar
15. Approval Routing

Fixed
AFDP-2907 Copy existing reports and write them in MySQL for all extensions All existing reports in all extensions should be written in MySQL (same as it works for the Core) Fixed
Reference created between a case and another case Reference created between a case and another case, only shows the reference in the case that the user was in.

When you navigate to the referenced case, I did not see a link back to the original case.

Fixed
User can update Request with mandatory fields not filled 1: Login to application with user that have permissions to open FOIA Requests module
2: Click on FOIA requests from left side menu.
3: Open some existing request
4: Update first name and last name with empty strings and click Save.
Expected result: First Name and Last Name are mandatory and user should not be able to save the request.
Actual result: Request is successfully saved with empty first name and last name.
Fixed
Edit Assignee in Case/Complaint 1.Log into the application.
2. Click on new button.
3. Click on new case button.
4. Fill in necessary fields and click submit. (By default the assignee is “None ” and the owning group is ACM_INVESTIGATOR_DEV);
5. Click on assignee link.
6. Search for user with name “sally” .
Bug: There is not result after searching. But if i edit assignee from participant table in the search result sally supervisor is displayed.
Fixed
Configure Drools Rules to configure logic for making the Assignee null Moving (or porting) the logic for making the Assignee null (or appear as None in the UI) for when the Task/Case/Complaint is reassigned to an Owning Group that the current Assignee is not a member of to the backend (Drools rules engine). Essentially this logic described should be manage by the Drools rules Engine. Fixed
The Priority control is not aligned correctly The Priority control is not aligned within the row for New Tasks

New > Tasks

Fixed