The newest point release of ArkCase, version 3.2, was released on February 6th, 2018. This point version is v3.2.4. For more information, please review the release notes below.
| Title | Summary | Resolution |
| Fix the defects in JS files that prevent them from being auto-formatted | See comments in AFDP-4496 for a list of JS files that can’t be auto-formatted. Apparently it’s because these files have functions or other design elements named for JS reserved words. Fix all these issues so all the JS files can be formatted property (and so we aren’t using reserved words or other language elements in a wrong way). | Fixed |
| User Picker for Approver in Change Case Status form, shows invalid users (without domain) | Choosing the approver in “Change Case status” frevvo form, opens a User Picker, that lists invalid users on search. User Picker forms should be unified all over the sapplication |
Fixed |
| Organization can’t be created with person associated | 1: Login as user that have permissions to Organization. 2: Click on New/Organization 3: Insert all required fields and add person 4: Submit data. Expected result: New organization is created with people. Actual result: Organization is not successfully created, exception occurs. |
Fixed |
| History grid is empty in tasks | 1: Login as user that have permissions to Tasks. 2: Click on New/Task 3: Insert all required data and save it. 4: Click on History link on tabbed footer menu. Expected result: Appropriate record for task created is displayed. Actual result: History grid is empty. |
Fixed |
| Ad hoc task added to case/complaint can’t be deleted | 1: Login as user that have permissions to Cases/Complaints 2: Click on Cases/Complaints from left side menu. 3: Click on Tasks sublink under some case/complaint 4: Click on “+” 5: Insert all required data and save the task 6: Click on case/complaint title 7: Click on Tasks sublink, Expected result: icon for deleting task is visible in grid and can be clicked Actual result: icon for deleting task is not visible in grid. |
Fixed |
| Lookup management – Deleting lookup entry | When deleting entry from the lookup, it will be nice to have confirmation box, as notification for the user (“Are you sure” dialog box) | Fixed |
| Approval Routing grid – bad presentation of Owning group and Assignee name | When adding new Approver in Approval Routing table, new task is created, added in the table, but in the column for “Owning group”, User name is displayed, and in the column for Assignee, User ID is displayed instead of User name. Moreover…when this task is activated, Owning group for that task is again populated with Assignee name |
Fixed |
| Ad-hoc group names are converted to uppercase | With the latest migration of LDAP data, ad-hoc group names are converted to uppercase, where on HDS we need the exact capitalization, because we are trying to match the group name to a dynamically created string (consisting of HDS Client’s identifier and its name), and that comparison fails. | Fixed |
| Case status not refreshed | After initiating approval process, Case status should be changed from “Draft” to “In Approval”. After concurring all tasks, Case status should be “Approved” Even after hard refresh, case status is not changed |
Fixed |
| Add existing group to the Ad-hoc group functionality | Add existing group to the Ad-hoc group functionality | Fixed |
| Admin/Email Templates – validation on template configuration data in order to restrict multiple mails to be send for same action | Service code should be changed, so the templates don’t need to be unique. In current implementation, the service ignores templates where more than one of the checkboxes is selected. We could change the service so it uses any matching template, regardless of whether the template matches other situations too. That may be friendlier, because then we would need only one template. But we should restrict the possibility to set multiple templates for same action/object in order to restrict sending multiple emails For example: if user set template for action or object for which there is already set template, notification should be displayed (“There is already set template for selected object/action”) and “Save” button should be disabled |
Fixed |
| Edit Participants issue | When trying to edit participant in Cases or Complaints – Error message …”Invalid Participant…” | Fixed |
| Insert picture/link form is displayed under the new task form | Steps to reproduce:
1. Go to new Task form Actual Result: Expected Result” Insert picture form is displayed in the front of the New task form. |
Fixed |
| Update UI to be able to add existing group as a subgroup. | Add UI elements and REST end point to use functionality defined in `GroupServiceImpl` | Fixed |
| Map display for the address | It is nice to have a “Map” button for every address item, that will open google Maps | Fixed |
| Change entries order in Lookup Table in Admin | Add Sequence Value to the Lookup Table in Admin | Fixed |
| Participant type drop down list is empty in document viewer page | 1: Login as user that have permissions to complaints. 2: Click on Complaints from left side menu. 3: Click on Documents sublink under some complaint. 4: Right click on some document and click Open. 5: Click on Participants tab. 6: Click on “+” . Expected result: Participant type is not empty and user can select option. Actual result: Participant Type drop down list is empty. |
Fixed |
| When calendar is disabled, 403 error occurs when user try to open closed case | 1: Login as user that have permissions to Admin/Cases module. 2: Click on Admin from left side menu. 3: Click on Security/Calendar Configuration 4: Activate Calendar for Cases if is not activated. 5: Click on Cases from left side menu. 6: Filter closed Cases. Actual result: 403 error occurs (user have no granted permissions). Expected result: No error should occur, user should have permissions to closed cases also, because is member of owning group . |
Fixed |
| Changes in history are duplicated | 1: Login as user that have permissions to Organization 2: Click on Organization from left side menu. 3: Click on Phone Numbers sublink 4: Add new phone number 5: Edit phone number data 6: Click on History sublink 7: Click on button to view changes Expected result: The changes are displayed in columns “Old Value” and “New Value” and Action is displaying the value changed. Actual result: The changes are displayed double, also columns are not correct. |
Fixed |
| Even though user initiate workflow with not selected “Non-concur ends the approval cycle” it will be selected when workflow is finished | 1: Login as user that have permissions to cases/complaints 2: Click on New/Case 3: Insert all required fields ans sumbit 4: Click on “Approval Routing” 5: Deselect “Non-concur ends the approval cycle” and click Initiate. 6: Login with next approver and concur the task. 7: Concur all tasks until last approver. Expected result: “Non-concur ends the approval cycle” should be deselected after workflow is finished – because under this conditions workflow was run. Actual result: “Non-concur ends the approval cycle” is selected |
Fixed |
| Uploading correspondence or adding documents even though is finished in backend, is uploading on UI | 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 root folder and select some correspondence. Expected result: Correspondence is successfully uploaded. Actual result: Uploading is never finished in UI, even though document is uploaded on backend. Please see attached video.If user click F5 can be seen that correspondence document is successfully uploaded. Same issue occurs with uploading documents. |
Fixed |
| Implement asynchronous inheritance of participants to subfolders and files | Having checked the validity of the participant for the parent folder, there shouldn’t be an issue to set the participant to the child folders and files. So we can synchronously set the participants to the parent folder and execute the inheritance asynchronously. There could be issues if something goes wrong in the async execution. We cannot implement some batch updater because we don’t know if inheritance was desired, i.e. the parent folder can have different participants with the child folders/files. In a case like this we can expect the user to manually press the “Inherit participants to children” button from the UI, similar to functionality that exists in Windows on folder security. |
Fixed |
| ArkPermissionEvaluator.hasPermission now supports multiple permissions | Document ACL Changes: ArkPermissionEvaluator.hasPermission now supports multiple permissions | Fixed |
| Use file participants feature in the UI for Case File, Complaint, Task, Costsheet, User, Timesheet | Document ACL Changes: Use file participants feature in the UI for Case File, Complaint, Task, Costsheet, User, Timesheet | Fixed |
| Create new Java service that will handle files/folders participants and inheritance | Document ACL Changes: Create new Java service that will handle files/folders participants and inheritance | Fixed |
| Update database – Inherit participants from entities to files and folders | Document ACL Changes: Update database – Inherit participants from entities to files and folders | Fixed |
| Use core-participants directive in document-details | Document ACL Changes: Use core-participants directive in document-details | Fixed |
| “Inherit participants” on files and folders on entity save | Document ACL Changes: “Inherit participants” on files and folders on entity save | Fixed |
| Add hasPermission on files/folders web APIs | Document ACL Changes: Add hasPermission on files/folders web APIs | Fixed |
| Create Participants Doc Tree extension | Document ACL Changes: Create Participants Doc Tree extension | Fixed |
| Implement “Inherit participants” on UI | Document ACL Changes: Implement “Inherit participants” on UI | Fixed |
| Add participantsBusinessRule to DataAccessPrivilegeListener. Remove all participantsBusinessRule handlers from pipeline. | Document ACL Changes: Add participantsBusinessRule to DataAccessPrivilegeListener. Remove all participantsBusinessRule handlers from pipeline. | Fixed |
| Add data access rules for files and folders in drools-access-control-rules.xlsx | Document ACL Changes: Add data access rules for files and folders in drools-access-control-rules.xlsx | Fixed |
| Refresh FileParticipants (on UI) after a change to EntityParticipants | Document ACL Changes: Refresh FileParticipants (on UI) after a change to EntityParticipants | Fixed |
| Set participants to attachments folders (as for Container folder) | Document ACL Changes: Set participants to attachments folders (as for Container folder) | Fixed |
| Add restricted flag to EcmFile and AcmFolder | Document ACL Changes: Add restricted flag to EcmFile and AcmFolder | Fixed |
| Reduce memory usage during file upload by avoiding byte arrays | Today when a file is uploaded, we load the entire file into a byte array. This uses the maximum amount of memory possible, causes memory thrashing, and may result in out of memory errors if people start uploading videos… a 5-second video from my phone is already 10MB. | Fixed |
| Fix missing label resources | Fix missing label resources throughout the application | Fixed |
| Admin – Configure Automatic Approval Routing Approvers and Tasks | Admin – Configure Automatic Approval Routing Approvers and Tasks
Give the super user the ability to configure a static list and order of approvers with static tasks for each parent object/object type/doctype. |
Fixed |
| Large PDF files (> 100MB) can’t be added to ArkCase | Files above a certain size always fail to be added to ArkCase. | Fixed |
| Search Subscription with invalid data | 1: Log into the application., User lands on the Dashboard. 2: Click on Subscriptions in the sidebar., User lands on the Subscriptions page. 3: Click on the search box and enter invalid data (e.g “@#(^%$”) and click the search button, Verify that the Subscriptions result table is not displayed, Subscription table data is displayed when i searched with invalid data |
Fixed |