The newest point release of ArkCase, version 3.2, was released on January 11th, 2018. This point version is v3.2.2. For more information, please review the release notes below.
| Title | Summary | Resolution |
| User ann-acm has null distinguished name and uid | This issue is happening for the second time. Deeper analysis to be done for founding how this values are changed | Fixed |
| When user try to run audit reports site requests authorization (issue with adding @ARMEDIA to users) | 1: Login as user that have permissions to Audit module. 2: Click on Audit from left side menu. 3: Select some filter and click “Generate Audit Report” button. Expected result: Report is successfully generated. Actual result: web page requests authorization. If user authenticate with ann-acm (without adding @ARMEDIA) report will be generated. |
Fixed |
| Dashboard – New Cases widget – Label issue | There is an issue with one label in Dashboard – New Cases widget | Fixed |
| No ArkCase permissions when using SAML authentication | With the latest changes on user and group handling on ArkCase (appending the domain on users and groups), and using SAML authentication provider, after successful login with the IdP, user has no permission to see any of the ArkCase resources.
This is most likely a result of SAML assertion holding the username only (with no domain appended), that also becomes part of Spring Security authentication token, and which is unknown user to the system. The issue is manifested as empty page after redirecting from IdP (AFDP) to SP (ArkCase): |
Fixed |
| User/Group Picker should list only active users | ann-acm is no longer valid user (not member of any group). It shouldn’t be listed in the User Picker results list | Fixed |
| Reports Configuration issue | Reports Configuration – Report Types are not displayed This issue is causing another problem: Reports drop-down list in Report module is empty |
Fixed |
| History icon link is missing on tabbed footer in Cases | 1: Login as user that have permissions to Cases module. 2: Click on Cases from left side menu. 3: Click on History on tabbed footer menu. Expected result: History icon is clicked. Actual result: History icon is missing on tabbed footer menu. |
Fixed |
| Clean up some i18n related label issues | – Remove commented unused labels – Remove `userOrGroupFacetFilter`. Reason: setting param not label – Remove `cases.comp.merge.id’. Reason: internal data, not label – Move `createNew.createNewUrl` from label to config.json. Reason: URL, not label – Refactor page count message for `simple-pager` directive. Reason: Assumption of English order |
Fixed |
| Source Entity and Source Organization in document viewer page | Steps to reproduce:
1. Go to cases page. When user tries to add organization and person error occurs in console(“ypeError: Cannot read property ‘key’ of undefined”) and save button for adding person and organization are disabled |
Fixed |
| Audit – “save” button disabled if “All” is selected | In Audit module, if “ALL” is selected, “Save” button should be enabled. | Fixed |
| Document file types values are not displayed | Steps to reproduce :
1. Go to Cases page Actual Result: Expected Result: In the Type column should be displayed the lookup value (e.g eDelivery,Other..), depends of the document type selected |
Fixed |
| Error in cases page | 500 (Internal Server Error) occurs when user navigates to Cases page and approval routing section | Fixed |
| New case – Initiator save person button is disabled | Steps to reproduce:
1. Go to new case form Actual Result: Expected Result: |
Fixed |
| Task module – Parent documents – Labels issue | Bad presentation of the Labels in Task module – Parent documents node (Refreshing labels in Admin/Label configuration doesn’t help) | Fixed |
| Calendar Module Widget not populating any information | Calendar Module Widget not populating any information
1. Login Currently it won’t populate. |
Fixed |
| Participants are not able to be edit/deleted with parethesis | There is bug for editing, we are seaching in solr by id, but providing only name. | Fixed |
| Edit Related Person | Steps to reproduce:
1. Create new person Actual Result: Expected Result: |
Fixed |
| Title in related people/organization grid to be separate label | 1: Login as user that have permissions to Organizations. 2: Click on Organization from left side menu. 3: Click on “Rel Orgs” sublink. Expected result: title of grid is “Related Organizations”. Actual result: title of grid is same label as sublink and is “Rel Orgs”.Same should apply to People / Related People |
Fixed |
| Data is updated in templates grid even though user click cancel | 1: Login as user that have permissions to Admin module. 2: Click on Admin from left side menu. 3: Click on Security/Email Templates 4: Click on edit icon next to some template. 5: Select object type or action and click Cancel. Expected result: New selected object type or action should not be added in grid. Actual result: New selected object type and action are added in grid on cancel button click.Please note that data are not saved. |
Fixed |
| People module – Cannot upload picture – 500 error | People module – Picture node – Picture cannot be uploaded (add or edit). | Fixed |
| Creating new task from Case/Approval Routing – issue with selecting User/Group | Creating “New Task” on the “+” icon in Approval routing node for “Cases” has issues with selecting Assignee. This modal window should use new implementation for User/Group Picker. It will be nice to add one more field in the modal for “Owning group” (same as “New Task” modal window) for presenting Owning group. |
Fixed |
| Creating new Person with associated Organization – error | When creating new Person with organization associated in it, throws error. Association type is not presented too when adding new person as a “Source Entity” in Snowbound. | Fixed |
| Ad-hoc group containing forward slash in its name cannot be expanded in UI | Ad-hoc group names can contain forward slash character in their names, but any action that invokes REST endpoint on the backend side, and at the same time contains the group name in the URL, fails, because forward slash acts as a path separator in the URL.
Eg: trying to expand ad-hoc group named *A TEST GROUP / CONTAINING SLASH* throws an error and the spinner spins indefinitely: |
Fixed |
| Complaint disposition count report always display 0 results for all disposition counts | 1: Login with user that have permissions to Complaints and Reports. 2: Click on Complaints from left side menu. 3: Open some draft complaint and click on “Close Complaint” . 4: Submit all required data. 5: Click on Tasks sublink. 6: Click on task for approving closing complaint. 7: Click on “Approve Document” button. 8: Click on Reports from left side menu. 9: Select “Complaint Disposition Count” report. Expected result: Complaint disposition count is increased for 1 for chosen disposition count. Actual result: Count is always 0. |
Fixed |
| Key field should allow empty string as a value | When adding new lookup entries, “Key” field should allow empty string to be entered, meaning that “Key” field should not be mandatory and validation should allow empty string for “Key” | Fixed |
| Key field should not be editable in Lookups Configuration | When editing lookups in Admin -> Lookups Configuration, the key field should not be editable. | Fixed |
| When ad hoc task is created should be assigned to current user | 1: Login as user that have permissions to Tasks. 2: Click on new task 3: Insert all required fields and click “Save Task”. Expected result: new created task is assigned to current user. Actual result: new created task is not assigned.Also when user add ad hoc task under case or complaint, previously was assigned to current user – now is not assigned. |
Fixed |
| Fix missing langugage resources of Notifications/Tags/Subscriptions module | Fix missing langugage resources of Notifications/Tags/Subscriptions module | Fixed |
| Ad-hoc group names: using parenthesis messes up Solr search | On HDS, a couple of ad-hoc groups were created where the names contained parenthesis, eg. {noformat} Lakeview Multispecialty Clinic (Disability & FMLA Forms) {noformat} All users that are members of any of these groups are having issues working with ArkCase, because the access control evaluator fails to evaluate read access (see {{ArkPermissionEvaluator.checkAccessForSingleObject()}} line 112-119). When this code section is issuing a Solr query, Solr complains with something like “{{…unexpected character ‘)’…}}”. We should probably add parenthesis to the list of special characters (space, comma) |
Fixed |
| Add New Person or Organization from Form – Old UI screen | The New Person and Organization modal boxes are using the create UI modal box, but the add new Person or Organization from a complaint or case form or from a complaint or case person/organization table uses the old UI modal box.
When you open the New Person or New Organization modal box, on save button there are showing 2 icons. |
Fixed |
| When Search Filters are applied new search cannot be performed | When Search Filters are applied new search cannot be performed | Fixed |
| Fix backend code to use new lookups structure | Fix backend code to use new lookups structure | Fixed |
| Fix UI code to use new lookups structure | Fix UI code to use new lookups structure | Fixed |
| Refactoring lookups.json structure | Need to refactor the structure of the lookups.json file. Add “name”, “entries” and “readonly” property in every lookup. |
Fixed |
| Updated the Frevvo docker image | Frevvo containers needs to be updated, after some changes on the core frevvo forms | Fixed |
| Removing the user from ADHOC group triggers removing from LDAP group (and fails) | Going to Admin module, Security, LDAP User Management and selecting a user that is a member of an AHDOC group (1), then selecting the ADHOC group from the *Authorized* panel (2), and clicking on Remove button (3) results in an error.
!image-2017-11-29-16-26-12-575.png|thumbnail! The reason for that error is triggering the “remove a user from LDAP group” functionality on the backend, whereas the ADHOC group does not exist on the LDAP server |
Fixed |
| New Task Form – Date field validation | We need validation on the calendar dates in New Task form. Due date cannot be before Start date | Fixed |
| Backend changes – New lookups-ext.json file for all changes in lookups | All changes in the lookups should go in new lookups-ext.json file. | Fixed |
| UI changes – ‘readonly’ property and delete functionality for new created lookups | All lookups in lookups.json should have ‘readonly’ property set to true. Delete button for deleting new created lookups in Admin->Lookups Configuration |
Fixed |
| When user hover over calendar event, first 50 characters from inserted comments should be displayed | 1: Login as user that have permissions to Cases. 2: Click on Cases from left side menu. 3: Click on Calendar sublink. 4: Add new event and in comments add more than 50 characters. 5: Hover over inserted event. Expected result: 50 characters from comment are displayed when user hover over event. Actual result: Only Subject and from/to dates are displayed. |
Fixed |
| Introduce new data update service module | This service should allow for core and extensions to be able to define data update operations and ensure to be executed only once in the order specified. | Fixed |
| Rename “Future Approvers” into “Approvers” | 1: Login as user that have permissions to Cases/Complaints 2: Click on Complaints from left side menu. 3: Hover over “Future Approvers”. Expected result; text under last link is “Approvers’ and there is no design issue. Actual result: text is “Future Approvers and is covered by arrow. |
Fixed |
| When concur or non-concur, the task data and past approvers grid are not refreshed with new data | 1: Login as user that have permissions to cases/complaints 2: Click on New/Case 3: insert all required data and submit it. 4: click on Approvers 5: Click on Initiate button 6: Login with first initiator. 7: Click on same case and click “Concur” or “Non-Concur” Expected result: Current task, approvers grid and past approvers grid are updated. Actual result: Only Approvers grid is refreshed and updated. |
Fixed |
| Labels in Admin module -> Security/Calendar Configuration | Need to change the translation in security.calendarConfiguration.emailValid and security.calendarConfiguration.emailNotValid in other translation files in admin module. ( It is already changed in en.json and en-in.json files) | Fixed |
| I18n for docTree | Fix doctree issues | Fixed |
| Technical Debt – Improve efficiency of “/api/latest/service/calendar/configure” endpoint | PropertyFileCalendarAdminService should read from the property files on init and keep the configuration in memory.
Also move method ‘public CalendarConfigurationsByObjectType getConfiguration()’ from AcmCalendarManagementAPIController to AcmCalendarAPIController. |
Fixed |
| Ancestors for groups member of a deleted group are not updated | Ancestors for groups member of a deleted group are not updated.
Expected: When a group (LDAP/ADHOC) is deleted, any of the direct member groups (subgroups) this group has, should become top level groups. This would mean that it should be shown in the list of groups in Organizational Hierarchy. When deleting subgroup (group that has a parent), the group is removed from the parent and if this group ends up with no other parent, than it is deleted. Actual behavior now: If the deleted group has any subgroups in it, they are never shown in the organizational hierarchy list. Steps to reproduce: |
Fixed |
| Top Ribbon – Parent Organization – Organization picker allows choosing same organization | In Organization Top Ribbon, Organization picker should use same endpoint as for adding related organization, with filter that doesn’t allow choosing same organization as related | Fixed |
| Need to be able to add new lookup in Admin -> Lookups Configuration | Need the functionality for adding new lookup in Admin -> Lookups Configuration. | Fixed |
| Can’t expand groups in organizational hierarchy | 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 arrow for expanding next to some group. Expected result: group is expanded and can be viewed members of group. Actual result: dev console exception error occurs, see attachment.Please note that this is working on cloud environment. |
Fixed |
| Download as Zip files issue – if two or more files with same name | Steps to Reproduce:
1. Go to cases page Actual Result: Expected Result : |
Fixed |
| Document viewer page – picture can not be added in details | Steps to Reproduce:
1. Go to cases page Actual result: Expected Result: Picture should be added and successfully saved. |
Fixed |
| Missing possibility to add email template for Document Repository module | 1: Login as user that have permissions to Admin module. 2: Click on Admin from left side menu. 3: Click on Security/Email Templates. 4: Click on “+” . Expected result: There is check box for adding template for document repository module as for other modules. Actual result: There is no check box for adding template for document repository module.Please note that emails can’t be sent from this module also. I assume the reason is that we don’t have template configured. |
Fixed |
| Admin – Org Hier – Add duplicate Adhoc Group | 1: Add new Adhoc group that matches an existing group, The system should notify user that an adhoc group with that name already exist, The user can add a duplicate named Adhoc group | Fixed |
| People/Organization – UI needs to show if person or organization is active or not | People/Organization – UI needs to show if person or organization is active or not | Fixed |
| Task page – Declare as Record Document | Actual Result :
1. Go to Tasks page. Expected Result: 1. Go to Tasks page. |
Fixed |
| Audit Module – Can Run Audit Report with Invalid Data in the To and From Fields | 1: Enter “Test” into the To and/or From Field and Click Run Report, The report runs but doesn’t return results, The report shouldn’t run and should tell the user that the To and From field data is invalid | Fixed |
| Some widget names in dashboard Admin panel shown as raw resource keys | Widget names in dashboard config panel in Admin page do not display names, but display resource keys instead. This happens in Core app too. | Fixed |
| All modules – Search filter should respond when user click “Enter” | People Search filter should respond when user clicks enter
People module Result: Nothing happens. I expected the search filter to be applied. The “Go” to be selected. |
Fixed |
| Picture Link button in Email form | 1. Log into the application 2. Click on Cases in the sidebar 3. Select case and click on documents sublink 4. Expand the Documents tree and right click on some document 5. Click on email 6. In the details section of the email pop up from , click on picture link button (or Link button) (bug)The pop form for uploading picture is displayed under the email form not in the front. |
Fixed |
| For no version history, appropriate label text should be configured in admin label configuration | 1: Login as user that have permissions to Admin module 2: Click on Admin from left side menu 3: Click on Workflows/Workflow Configuration 4: Click on Version History link on workflow that doesn’t have history. Expected result: appropriate message is displayed informing that for that workflow there is no history. Actual result: Message is displayed: “admin.workflows.config.noHistory” |
Fixed |
| Change error message to “Only PNG format is allowed” in admin/upload logo | 1: Login as user that have permissions to Admin module 2: Click on Admin from the left side menu 3: Click on “Branding/Logo” 4: Upload logo – different format from png, for example jpg and click “Save” button. Expected Result; Validation message is displayed ‘Only PNG format is allowed”. Actual Result: Validation message is displayed “Error uploading custom logo files.” |
Fixed |
| Costsheet can’t be inserted without code, insert is not successful and no validation is displayed | 1: Login as user that have permissions to Cost Tracking module. 2: Click on New/Costsheet 3: Insert all required fields except code and click “Save” button. Expected result: Validation message is displayed informing that code must be inserted. Actual result: Cost is not successfully inserted, user is redirected to Cost Tracking page. |
Fixed |
| Cost/Time sheet can be sent for approval without inserted approver | 1: Login as user that have permissions to Cost/Time Tracking 2: Click on New/Costsheet(Timesheet) 3: Insert all required fields except approver and click “Send for Approval”. Expected result: Validation message is displayed informing that user have to insert approver Actual result: Cost (or Time) sheet is successfully sent for approval – saved. |
Fixed |
| Change the AcmGroup model to ManyToMany to represent the graph structure | Change the AcmGroup model to ManyToMany to represent the graph structure | Fixed |
| Alfresco sync service: handle events from all audit apps in order by ascending audit id | ArkCase’s Alfresco sync service supports any number of Alfresco audit applications. Currently it handles events for each application before detecting events from the next application. But some related events come from different applications, like so:
* folder created event (from the create-node audit app) If these three events all come in the same sync run ArkCase will miss an event. Either it processes the folder created event and the rendition created event first; so the folder and the file are created in ArkCase but not the rendition (since ArkCase doesn’t have the file yet); or it processes the file created event first, so only the folder is created (file is not created since the folder is not there yet; rendition is not created since the file was not created). So, ArkCase should gather all the events, then process all of them. |
Fixed |
| Add Reference ID to History table | Add Reference ID to History table.
If user adds a document or task or etc, to a Case or Complaint or Task we can store a link to the object in reference. History event: Add document xx |
Fixed |