Release v3.1.26

Summary Description Resolution
Automated Task Routing Approval 1.Log into the application.
2. Navigate to Case Files.
3. Click on change case status button.
4. Select status closed and click submit.
5. Navigate to the automated task.
6. Click on approval routing.
7. Click on Add future approvers btn. (bug)

When i click on the add future approvers button the popup modal is not displayed and i got error in the console.

Fixed
When new object is created, notification is not displayed “Object with ID {ID} was created for cases, complaints, documents, tasks, costsheets, timesheets 1: Login as user that have permissions to Cases/Complaints/Documents/Time Tracking/Cost Tracking
2: Click on New/Case or other object from mentioned
3: Insert all required data and click Save.
Expected result: Notification message is displayed informing that object is created. For cases: “Case with ID {id}} was created”.
Actual result: Notification message is not displayed for successful saving, for cases, complaints, documents, time sheets and cost sheets.

Please note that this is working for organization and people.

Fixed
Cannot create a Complaint if you fill in Step 1: Initiator details Create a New Complaint
Add details beyond the name

When you save, the Complaint is not created.

Fixed
Complaint can be inserted without initiator if user click on “Search Existing Initiator” during insert 1: Login as user that have permissions to Complaints module
2: Click on New/Complaint
3: Select “Search Existing Initiator”.
4: Click “Next” button,

Expected result: Step:1 Initiator is marked with red color
Actual result: Step 1: Initiator is not marked as mandatory not filled

5: Click “Previous” button,
6: Click on Name field and exit

Expected result: Field is marked with yellow background color and message is displayed informing that field is mandatory.
Actual result: Nothing on page is marked as mandatory

7: Click on Incident tab, insert all mandatory data and click “Submit” button,

Expected result: Complaint can’t be saved without initiator
Actual result: Complaint is saved without initiator.

Fixed
Organizations/People page 1. Log into the application
2. Click on Organizations or People module in the sidebar

Lots of errors are displayed in the console when user lands on the organization/people page

Fixed
Can’t authorize role to see module in Admin/Security/Modules 1: Login as user that have permissions to see Admin module
2: Click on Admin/Security/Modules
3: Select some module and try to authorize some role,
Expected result: Role is successfully authorized to view module
Actual result: User have no granted permissions for this action message is displayed, there is 403 error in console
Fixed
When Case/Complaint/Timesheet/CostSheet is created, the newest object is not displayed at top and selected by default in the tree 1: Login as user that have permissions to Cases/Complaints
2: Click on New/Case or Complaint
3: Insert all required fields and submit.
Expected result: New created case/complaint is placed at the top in the tree and selected by default
Actual result: New created case/complaint is not presented at all in the tree. If user search or refresh the tree, record will be displayed
Fixed
Concur not working for Automated Task on Creating Complaint 1. Log into the application.
2. Click on the New button at the top of the screen.
3. Click on Complaint button
4. Fill out all required information, assign the Complaint to the current user, and click Submit at the bottom of the page.
5. Click on Tasks of the created Complaint
6. Click on the “Review” + id task in the task name (User is redirected to the tasks page)
7. Click on Concur button (bug)
Fixed
Integrate Person Picker with frevvo forms Integrate Person and Organization Picker with frevvo forms Fixed
Module widget can’t be enabled or disabled – 403 Forbiden error occurs 1: Login as user that have permissions to Admin module
2: Click on Application/Module Configuration
3: Click on some module
4: Click on label “Disabled” or “Enabled” on some widget.
Expected result: Notification message is displayed “Action was successfull”
Actual Result: Notification message is displayed: “User does not have permissions for this action” – 403 forbiden error in console log, see attachment
This action is not done on backend also, because if user refresh the changes are not saved.
Fixed
Tasks Dates are behind by one day Reported on Sharecare PROD site as SSP-335:

Click New
Select Task
Set Start Date as 8/11/2017
Set Due Date as 8/15/2017
Click Save Task
!Dates on Create.png|thumbnail!

View Task in Tasks module
Start Date is 8/10/2017
Due Date is 8/14/2017

Fixed
Claim/Unclaim task button does not toggle the value after initial change When user unclaims a task the UI does not update the button due to the unclaim REST call returning HTTP 500 error.

Steps to Reproduce:

Authenticate as jscott
Navigate to tasks module
Click on Unclaim button for a claimed task  Verify the REST call for unclaim returned HTTP 500 error

Actual Result: The task is unclaimed but UI did not update due to HTTP 500 error

Expected Result: If task status has been changed from Claimed/Unclaimed then UI should update and REST call should not return error.

Fixed
Created People record in Audit 1. Log into the application
2. Click on New button
3. Click in person button
4. Fill in necessary fields and click the Save person button
After the person is created navigate to the Audit page

5. From the Report name dropdown select “People”
6. In the Id fields enter the created person Id
7 Click the Generate Audit Report Button

Record for the created person is missing in the generated audit report

Fixed
Organization module-Adding people – not set as Primary When adding person to organization (Ether when creating new organization, or to existing one), it is not set as “primary” by default, when it’s the only one.
The issue is also on the top ribbon for Organizations (it doesn’t show the primary contact, if there is no primary contact set)
Fixed
Complaint/Case – Approval Routing – Major Issues Complaint – Approval Routing

Click on Approval Routing node and the page is completely messed up (See attached SS)

Case – Approval Routing

Steps
1. Login to Dev App
2. Create new Case
3. Go to Approval Routing Tab and see that Ann has a Review task
4. Go to that task and click concur

Expected Result: Task is completed and closed and new review task is create for next person in the review process
Actual Result: Error (See below)

Fixed
Automatic generated task can’t be approved, error occurs Steps to reproduce:
1. Login as user that have permissions to cases
2. Open some draft case
3. Click on change case button
4. Insert all required data and submit it (change it to closed)
5. Navigate to tasks
6. Click on automatic generated task
7. Click “Approve document”
Expected result:
Task is successfully closed and case status is changed into closed
Same error occurs when user try to close complaint
Fixed
Approval routing issue in Complaints On Complaints – Approval routing node error is thrown and bad presentation in application window Fixed
Snowbound v4.7 – Remaining Issues Two issues:

1. When saying an annotation, and then burning, the image doesn’t refresh to the new version that has the burn on the viewer page the current user is on.
2. When you move back to the previous version prior to the burned version, the user should see the prior version with the annotation overlay on the image and currently that is not showing at all.

Fixed
FOIA: dashboard label catchup to core Core has some dashboard label changes that need to be propagated to FOIA. Fixed
Fix v4.7 Snowbound Viewer – Hover over issues Fix Snowbound Viewer – Hover over issues Fixed
Internationalization – Navigating to a second browser window defaults to English Internationalization – Navigating to a second browser window defaults to English

Steps:
1: Login as ann
2: Click on Language(English) from the right top menu.
3: Choose any other language other than english.
4: Language updates on browser window
5. Now navigate to a document and open it
6. New browser window opens and the labels are default back to english

Expected result: Updated language should show on all new browser windows opened for that user

Actual result: Resets to English language.

Fixed
FOIA: doc tree file type list in request details page and queue details page always shows “Undefined” Actual:
* define file types in admin / lookups, being careful to use existing labels
* open a FOIA request in either the request or queue module
* right click a folder in doc tree
* for every file type, the drop down menu shows “Undefined”

Expected:
* In Step 4, you should se the file types just defined

Fixed
Delete button (icon) is missing in the tables 1.Log into the application.
2. Click on Organization from the left side menu.
3. Open some Organization.
4. Click on Locations sublink.
5. Click on “+” icon.
6. Insert all required fields and click the Save Location Button.
7. Add another location that is set as no for primary

Delete icon is missing in the grid

Same issue in all tables (all modules) where items can be edited or deleted… “delete” icon is missing
Please note that “Delete” icon should be removed only for “primary” items

Fixed
Opening Case module – Error thrown (taskID requested is empty) When loading Task widget in Case module – taskID requested is empty – Error thown in console Fixed
Dashboard – Add Description to all Widgets Dashboard – Add Description to all Widgets

This “Description” Field will be editable and if populated, will be appended to the end of the widget title. This description will be user specific for there dashboard.

Fixed
Search field and search button are missing in all modules under tree view 1: Login as user that have permissions to Cases/Complaints/Documents/Organization/People
2: Click on some module from left side menu, for example cases
3: Try to search some old case,
Expected result: user can search the object
Actual result: Missing search field and search button in UI.
Please note that search field and button are missing in all modules cases, complaints, documents, organization, people
Fixed
Case module – Approval rooting issue (for cases created by complaint) Case module (only for cases created by complaint) – when opening “Approval rooting” node, there is an error thrown. Please see SS

1.Log into the application.
2. Navigate to Complaints
3. Click on “Close Complaint” for some selected complaint. Close complaint with choosing some action (ex. Open investigation)
4. Approve the task for closing complaint
5. Navigate to the automatically created Case
6. Click on approval routing.
Results: error in the console.

Note: Possible problem is that Automatically created Case (from closed complaint), has no automatically generated task (if you open “Task” node, it’s empty). There is also PDF file missing (Case File)…Another ticket opened for that (AFDP-3293)

Fixed
In Organization grid, primary contact is not displayed in grid 1: Login as user that have permissions to People module
2: Click on People from left side menu.
3: Click on Organization sublink
4: Add some organization with primary contact assigned.
Expected result: Organization is added and primary contact is displayed in grid.
Actual result: Organization is added, primary contact is not displayed in grid.
Fixed
User can’t relate new person to new organization with people, locations and communication accounts because can’t be expanded 1: Login as user that have permissions to People and Organizations modules
2: Click on New/Person
3: Insert all required fields and click on Organizations link, click on “Search Existing Organizations”
4: Click on “Add new organization” button.
5: Insert all required fields.
6: Click on People, Locations, Communication Accounts links.
Expected result: Appropriate modules are expanded and can be entered.
Actual result: Instead of modules on “Add Organization” form are expanded modules in behind on Person form.

Please note that same issue occur in Organization when user try to add new people.

Fixed
When adding person, inserted organization is not displayed on ribbon 1: Login as user that have permission to People module
2: Click on New/Person
3: Insert all required fields (first name and last name).
4: Click on Organizations link
5: Search existing or add new organization and select relation type.
6: Click on “Save Person” button.
Expected result: Person is created. New record is loaded. In ribbon is displayed value of added organization.
Actual result: Organization value is not displayed in ribbon, see attachment.
Fixed
Internationalization – User needs to log back in to see the language changes The internationalization is not working on core as expected in the following cases (for current user session):
1. Change the language -> Click on update -> Refresh
2. Change the language -> Click on update -> Open any left navigation menu in new tab
PFA the screenshots for your reference.

On logging back in, the behavior is as expected (Language updated in previous session is shown for all screens).

+Steps to recreate bug:+
1: Login as user that have permissions.
2: Click on Language(English) from the right top menu.
3: Choose any other language and click on update.
4: Refresh the web page.
Expected result: Updated language is successfully shown on the screen.
Actual result: Resets to English language. See attachment.
The same issue happens when any left nav menu links are opened in a new tab.

Fixed
LDAP Configuration in Admin page should provide syncEnabled checkbox (for LDAP sync) Extract syncEnabled attribute from spring-config-armedia-ldap.xml to spring-config-armedia-ldap.properties. And also add it to the LDAP Configuration form in the Admin page. Fixed
Concur/Non-Concur Task button – throws error 500 on “Concur” or “Non_Concur” button for Tasks, error 500 is thrown and error message shown in the application

It seams there is an issue with date format

Fixed
Locale settings not stored after clearing browser cache This happens on HDS (Bactes) after merging with latest ArkCase core changes. The screenshot should be self-explanatory:

!image-2017-10-10-16-23-18-544.png|thumbnail!

Fixed
Task module _Overview widgets_Documents In Task module, overview widgets for “Documents Under Review” and “Parent Documents” are not displaying correct information. Fixed
Approval Routing for automatically created Cases throws error 500 (no approvers) This is probably related to acm-task-plugin.xml file. It may be related to approval routing node. Fixed
Contacts Management – People – People Audit All changes to People object should be audited Fixed
AFDP-3944 Recreate Calendar Folders In case the account for the system user is closed or deactivated in Outlook, a fallback options should be provided.

* the system admin might recreate all calendar folders for the affected objects
* a user accessing an affected object will be notified that the calendar for the object is recreated due to deactivation of the system user used for creation of the calendar folder.

In both cases the current configured system user for that object type is used.
In both cases, all the events associated with the affected object instances will be lost.

Fixed
AFDP-3944 Calendar – Outlook folder issue – (UI) Admin configuration for setting system user credentials If/when authentication stops working due to invalid credentials, the system should highlight the affected system user in the admin panel, and inform the system admin to take appropriate action by updating the password or assigning a different system user. Fixed
AFDP-3944 Calendar – Outlook folder issue – (UI) Alert user for authentication problems When accessing Calendar from some object, user should be notified if the system user credentials, used for creating calendar Outlook folder, are no longer valid.
Notification should alert the user to contact system administrator for setting system user credentials
Fixed
AFDP-3202 Refactor date time format specified in language JSON file If possible, do not define our own date time format and let Angular does it automatically. We currently have many such format strings in language JSON files. Need to go case be case to refactor each date time display. Fixed
AFDP-3202 I18n for Admin page Update Internationalization frame work on Admin page. Fixed
AFDP-4542 New: Approval Routing Functionality – New Mockup of Add new to Approvers Table New: Approval Routing Functionality – New Mockup of Add new to Approvers Table

§ Metadata
• Assignee/Group Picker (Mandatory)
• Subject (Mandatory)
• Details (Mandatory)
• Due (Mandatory)
• Status (System Generated)
o Current – Current Approver
o Future – Future Approver
o Past – Past Approver
• Added By (System Generated)

Fixed
AFDP-4542 New: Approval Routing Functionality – New Mockup of Approvers Table on Approval Routing Node New: Approval Routing Functionality – New Mockup of Approvers Table on Approval Routing Node Fixed
AFDP-4118 Fix user and groups management implementation per AcmGroup model changes Fix user and groups management implementation per AcmGroup model changes.
Add/Remove user from a group should consider which type of membership is removing (1 [immediate & transitive] / 0 [transitive || immediate]) and decide to add or remove certain role.
Fixed
AFDP-4118 AcmGroup model to be changed to ManyToMany mapping instead of ManyToOne to AcmGroup to represent group membership in LDAP Change AcmGroup model to ManyToMany mapping instead of ManyToOne to AcmGroup to represent group membership in LDAP.
Fix all DAOs, service logic or tests where parent group is set, queried.
Check for any issues on UI.
Fixed
AFDP-4118 Fix LDAP sync once AcmGroup model is changed Fix LDAP sync logic per AcmGroup model changes.
Find user membership in a group by searching to all ancestors groups
Add AcmUserRole(s) by user to group membership.
Fixed
AFDP-4118 Ensure partial sync works per ldap sync changes Ensure partial sync works per ldap sync changes and add unit test to cover partial sync. Fixed
AFDP-4118 Fix API endpoints for Organizational Hierarchy per model changes – fix SaveMembersToGroupAPIController
– fix SaveSupervisorToGroupAPIController
– fix RemoveSupervisorAPIController
– fix RemoveMembersToGroupAPIController
– fix tests
Fixed