| Title | Summary | Resolution |
| Fix order of Preference Page List | Order of modules should match the module navigation list: Complaints, Case Files, Tasks, People, Organizations, Documents, My Documents, Cost Tracking, Time Tracking. | Fixed |
| Tag is not associated correctly to costsheet and timesheet | 1: Login as user that have permissions to cost tracking/time tracking 2: Open some cost sheet/time sheet 3: Click on tags sublink 4: Insert new tag 5: Navigate to another page (for example click on Case Files link) 6: Go back to cost sheet you inserted tag previously. Expected result: tag is displayed in grid. Actual result: tag is not displayed in grid. |
Fixed |
| Module widget, multiple modules should be removed from Module configuration menu | 1: Login as user that have permissions to Admin module 2: Click on Application/Module Configuration 3: Check the list of modules 4: Remove Core, Common settings, Document details, Frevvo, Goodbye, Welcome widgets.Expected result: Displayed all widgets that the user can enable/disable. Actual Result: All modules in ArkCase are displayed. |
Fixed |
| There is no notification that user can’t insert timesheet in future | 1: Login as user that have permissions to time tracking page 2: Click on New/Timesheet button 3: Click on “Next week” button. Expected result: Next week button is invisible or notification is displayed that user can’t insert time into future. Actual result: button is visible and no notification message is displayed that user can’t insert time in future. |
Fixed |
| Timesheet can be inserted and updated without charge code | 1: Login as user that have permissions to open time sheets 2: Click on New/Timesheet 3: Insert all required data, except the charge code and click Save button, Expected result: Validation message is displayed “You can’t leave this empty: Charge Code”, Actual result: Timesheet is successfully saved without charge code. |
Fixed |
| In document repository, assigned user identifier is displayed, instead of full username | 1: Login as user that have permissions to view Admin module 2: Click on Admin/Username Display Configuration and set it to “Use full Username” 3: Click on Documents from menu 4: Open some Document repository 5: Click on Participants, Expected result: In assignee is displayed full name (for example Samuel Supervisor). Actual result: For assignee is displayed “samuel-acm” – user identifierPlease note that this works ok for other modules for example cases, complaints If user open some case and then go back to document repository, the correct full username will be displayed. |
Fixed |
| New Organization form – People node – data not saved | When new organization is created, there is an option to associate an existing person to that organization. But that data is not saved and not presnted when you open “people” node for that organization | Fixed |
| Complaint > Organization First column in table missing label | Complaint > Organization
First column in table is missing label |
Fixed |
| Add Organization within a Case – Missing Label | Add Organization within a Case and the dialogue box to create the new Organization is missing a label
common.comp.newOrganization.parentOrganization |
Fixed |
| Document Tags table does not track who added the tag | Document Tags table does not track who added the tag and the date it was added. The Tags table on the document viewer page needs a 2 columns added. One column for “Date Created” and “Created By”. |
Fixed |
| Complaint > Organization first column – Missing label | Complaint > Organization first column in the label needs a label | Fixed |
| Creating Related Organization does not result in a new Organization in the list | Creating Related Organization does not result in a new Organization or a link between an existing Organization.
Organization > Related Organizations |
Fixed |
| Organization module – History functionality Issue | History event is not working for the Organization module. Any action done within the modules is not logged and presented in the History node. | Fixed |
| People module – History node functionality issues | For the History node in People Module, there are few issues/defects that has to be fixed: – History Events issue (History events aren’t firing) – Event descriptions are messed up (ex. “common.objectTypes.PERSON Updated – Document Downloaded”) |
Fixed |
| Improve the results table in Tag module | The results table on the Tag module should include a hyperlink to the tagged object (similar to the Search page results). The Name column should display the clean tag name without the number string. The Type column should be removed, because it will always display ASSOCIATED_TAG.
A space needs to be added to the Title after the Tag name (Matt1) and Parent (COMPLAINT). Currently it reads: “Matt1on object of type COMPLAINTand ID:529” |
Fixed |
| AFDP-3202 Localize Dashboard | Dashboard needs to be localized | Fixed |
| Complaint Incident Date | 1.Log into the application. 2. Click on new button. 3. Click on new complaint. 4. Fill in necessary fields , select incident date and click submit. 5. Close the complaint with option Open Investigation. 6. Approve the automated task. 7. Navigate to the created case and change case status. 8. Navigate to the created automated task.Bug: The incident date in automated task is not the same as the selected date on creating complaint. It’s the current date. |
Fixed |
| Attempt to change an Owning Group even if the user is not a member of the current Owning Group | In the Case and Complaint modules a user from a different Group is allowed to attempt to change an Owning Group even if the user is not a member of the current Owning Group attempted to be changed (the user’s actions are not successful – he gets an error message, but the link itself should be disabled). The link to reassign the Case or Complaint to another Owing Group should be disabled for a user that is not currently part of the Owning Group that the Case or Complaint is currently assigned to. | Fixed |
| History event when claiming case/complaint | When claiming case or complaint which was on group, history event description is not proper. | Fixed |
| Tags Module – Search Results Issues | Tags Module – Search Results Issues
1. The Parent column should be a hyperlink to the actual parent record |
Fixed |
| Costsheet code | 1.Log into the application. 2. Click on New button. 3. Click on the new costsheet link button. 4. Select type case. 5. Select code from the code drop down menu (improvement )In the code drop down menu are displayed only some of the codes. |
Fixed |
| Timesheet charge code | 1. Log into the application. 2. Click on new button. 3. Click on new timesheet link button. 4.Select case from the type drop down. 5. Click on thew charge code drop down.In the charge drop down are displayed only some of the cases. |
Fixed |
| No fields for subject/message when emailing from package | {html}<p>Open action, go to documents. Right click and choose email. There is no choice to enter a subject or content.</p><p> </p><p> </p>{html} | Fixed |
| Complaint History tab shows log-in id | Complaint History tab shows log-in id
Complaint > History Consider having a display_name within the user object which could be the userId or the First_Name Last_Name combination. That way we can make this configurable. |
Fixed |
| Adding Organization to Person under Case/Complaint | Adding Organization to Person under Case/Complaint should allow user to pick from existing Organizations.
If entering a new Organization, we should collect the address and website of the Organization. It would be nice to have a button to launch Google Maps with the location especially if someone is on a mobile device. From there they can get directions. |
Fixed |