| Title | Summary | Resolution |
| CaseFile frevvo form previous/next tab not working | CaseFile frevvo form previous/next tab not working | Fixed |
| ArkCase user guide no longer under Help. | ArkCase user guide no longer under Help. 404 error page comes up. | Fixed |
| Organization is not filled in grid for related person inserted | 1: Login as user that have permissions to People module. 2: Click on Related People sublink under some person. 3: Click on “+” icon to add new person. 4: Click on “Select Existing person”. 5: Search some person with organization and add it. 6: Select “Person Association Type” and save it Expected result: Related person is successfully added. Organization of related person is displayed in grid. Actual result: Organization of related person is not displayed in grid. | Fixed |
| When adding multiple documents within a Complaint,… | When adding multiple documents within a Complaint, the Author is only applied to the first document | Fixed |
| Ensure that all native SQL queries on ArkCase project are working with MySQL | First check whether all SQL in ArkCase platform works. If it does not work, rewrite the queries in the appropriate dialect. For example, in ArkCase we have native queries on multiple locations. We need to ensure all queries in the DAO layer of ArkCase are working with the new MySQL containers. | Fixed |
| When username is empty, wrong validation message is displayed next to password “Password cannot contain username.” | 1: Login as user that have permissions to Admin module. 2: Click on Admin from left side menu. 3: Click on Security/Organizational Hierarchy. 4: Click on “Add New Member” under some LDAP group. 5: Insert something into password. Expected result: Appropriate validation should be displayed according to entered password. Actual result: Validation message is displayed “Password cannot contain username.” | Fixed |
| History Event versus Audit Report Events | Need to investigate and fix the different between the audit events that show on the history table for each object and the events that show in the Audit report. All events that show on the history table need to show on the audit report. | Fixed |
| Contacts Management – Organization – Organization Audit | All changes to Organization object should be audited. | Fixed |
| Calendar – Internal server error notification | When trying to open calendar in cases or complaint module, notification in the left corner “Internal server error” and “Cannot find property ‘length'” in the console. Same error thrown in the console when leaving calendar. | Fixed |
| Admin – Workflow – Missing Actions on the Workflow Configuration Table | Admin – Workflow – Missing Actions on the Workflow Configuration Table. | Fixed |
| Preferences Section – Need to be able to change labels | Preferences Section – Need to be able to change labels for the Preferences module labels. | Fixed |
| Uploading a ‘.doc’ File Triggers Transaction Rollback |
*Description*: When a user uploads a ‘.doc’ file to a doc-tree, the upload triggers a rollback.
*Environment:* https://core.arkcase.dev.armedia.com/arkcase/ *Steps to Reproduce*: # Login as ‘ann-acm’ *Actual Result*: System fails to upload ‘.doc’ file *Expected Result*: System shows ‘.doc’ that I selected to upload. * Integration Test output {code:java} [main] org.springframework.test.context.support.DefaultTestContextBootstrapper –Loaded default TestExecutionListener class names from location [META-INF/spring.factories]: [org.springframework.test.context.web.ServletTestExecutionListener, org.springframework.test.context.support.DirtiesContextBeforeModesTestExecutionListener, org.springframework.test.context.support.DependencyInjectionTestExecutionListener, org.springframework.test.context.support.DirtiesContextTestExecutionListener, org.springframework.test.context.transaction.TransactionalTestExecutionListener, org.springframework.test.context.jdbc.SqlScriptsTestExecutionListener] Using TestExecutionListeners: [org.springframework.test.context.web.ServletTestExecutionListener@2b662a77, org.springframework.test.context.support.DirtiesContextBeforeModesTestExecutionListener@7f0eb4b4, org.springframework.test.context.support.DependencyInjectionTestExecutionListener@5c33f1a9, org.springframework.test.context.support.DirtiesContextTestExecutionListener@1623b78d, org.springframework.test.context.transaction.TransactionalTestExecutionListener@c8c12ac, org.springframework.test.context.jdbc.SqlScriptsTestExecutionListener@6adbc9d]2017-10-16 13:44:01,824 [INFO ] [main] org.springframework.beans.factory.xml.XmlBeanDefinitionReader – Loading XML bean definitions from class path resource [spring/spring-library-ecm-tika.xml] AutowiredAnnotationBeanPostProcessor – JSR-330 ‘javax.inject.Inject’ annotation found and supported for autowiring java.lang.NoSuchMethodError: org.apache.poi.util.LittleEndian.getUnsignedByte([BI)I at org.apache.poi.hwpf.model.FormattedDiskPage.(FormattedDiskPage.java:61) (RunBeforeTestMethodCallbacks.java:75) (RunBeforeTestClassCallbacks.java:61) (RunAfterTestClassCallbacks.java:70) 2017-10-16 13:44:03,328 [INFO ] [Thread-1] org.springframework.context.support.GenericApplicationContext – Closing org.springframework.context.support.GenericApplicationContext@408d971b: startup date [Mon Oct 16 13:44:01 EDT 2017]; root of context hierarchy Process finished with exit code -1 {code} *Reproduction IT MR*: https://gitlab.armedia.com/arkcase/ACM3/merge_requests/1823 |
Fixed |
| Create labels pickup component and use it in Admin->Lookups | The label pickup should allow searching by label key and by label value. It should work in the user selected language (no need for language selection). Use the new label pickup component fro choosing values in _application-lookups-standard-modal.client.view.html_ and _application-lookups-inverse-values-modal.client.view.html_. | Fixed |
| Organizational Hierarchy displaying invalid group members | ArkCase Admin panel, Security/Organizational Hierarchy. Expanding an ad-hoc group shows a list of its members which also include members that are marked {{INVALID}} (which often means they are deleted from LDAP directory or moved to other {{OU}}). In my opinion this is misleading and I think we should filter inactive members from the group. Even more, if you check the group membership in the database, inactive members are not there. I analyzed the cause for this and realized that for listing the group members we are using Solr query: {{object_type_s:USER AND groups_id_ss:”GROUP NAME”}} which returns the list of all users members of that group, even they are marked {{INVALID}}. So, if we agree that {{INVALID}} group members should be hidden, then we can: 1. extend existing query with adding additional filter ({{status_lcs:VALID}}): {{object_type_s:USER AND status_lcs:VALID AND groups_id_ss:”GROUP NAME”}} 2. use some other Solr query, such as: {{object_type_s:GROUP AND name:”GROUP NAME”}} 3. or just make sure we remove all the group memberships when invalidating a user | Fixed |
| Participant type in Case, Complaint or Documents module | Document, Complaint or Case Participants The Participant Type should us camel notation (capitalize first word) assignee -> Assignee owner -> Owner | Fixed |
| Creating Folder/file in parent Documents repository for Tasks should be forbidden | In Task module, Parent documents node, there is a problem when creating a New Folder. All functionalities related to documents (adding new documents, folders…) are not working | Fixed |
| Techincal Debt – LDAP User picker lists invalid (inactive) users | When you want to add users to a particular ad-hoc group, the user picker modal lists both valid (active) and invalid (inactive) users. Latest version of the modal does not offer to choose facets, so you are unable to tell between valid and invalid users: !image-2017-03-10-18-51-15-623.png|thumbnail! I talked to [~dmiller] and he also sees no point in showing invalid users. The search filter should be updated to filter out invalid users | Fixed |
| Organization module – Remove/Hide buttons “Merge”, “Import” and “Export” | Merge, Import and Export functionalities for Organizations are not implemented yet. Until we have these functionalities, these buttons should be removed/hide from UI, for better user experience. | Fixed |
| Update Branding – Few New Pages that Need to be updated | Please let me know if you have any questions. | Fixed |
| History Functionality for People and Organizations | It happens multiple logs to be shown for same event (same event, same time stamp…) History functionality to be checked after finishing the relations between Organizations, People, Cases and Complaints. | Fixed |
| Cost/Time Tracking – Create New – Duplicate Costsheets and Timesheets are Created in the Tree Temporarily | 1: Create Costsheet or Timesheet and hit save., Only one costsheet/timesheet is created, but the issue is two costsheets/timesheets with same information are created and showing in the treeview. Must refresh the tree over and over until the duplicate goes away. | Fixed |
| AFDP-3944 Clarify ‘restricted’ object. | Clarify what `restricted` object in this context means. | Fixed |
| Can’t add new person in complaints/cases with organization assigned | 1: Login as user that have permissions to Complaints/cases module 2: Click on Cases/Complaints from left side menu. 3: Click on People sublink under some case/complaint 4: Click on “+” 5: Click on “Add new Person” button. 6: Insert first name, last name, click on Organization and add new or existing one, select Relation Type and click “Save Person” button. 7: Then select “Person Relation Type” and click “Save Person”. Expected result: New added person is successfully added in grid. Actual result: Person is not added in grid. In console : Failed to load resource: the server responded with a status of 500 (Internal Server Error) | Fixed |
| Cost Module – Send Costsheet for approval without selecting approver | 1: Open Costsheet and enter all mandatory fields except approver and then click send for approval, The user can send for approval without specifying an approver. The costsheet is created, but not sent for approval. | Fixed |
| People Id’s table | Actual Scenario : 1. Go to People ID’s section 2. Add new ID 3. The value text of the ID type is displayed in the table Expected Scenario : 1. Go to People ID’s section 2. Add new ID 3. The label text of the ID type is displayed in the table | Fixed |
| Login with Credentials of Fake User Displays Stacktrace | *Description*: When a user enters credentials for non-existent user on login screen, stacktrace is displayed instead of regular error message. *Environment:* https://core.arkcase.dev.armedia.com/arkcase/ *Steps to Reproduce*: # Navigate to login page # Enter ‘doesnt.exist’ as username # Enter ‘fakepass’ as password *Actual Result*: System shows internal server stacktrace. *Expected Result*: System shows error message about bad credentials or other appropriate message. | Fixed |
| Id, primary contact, phone and location are not displayed in related organization grid | 1: Login as user that have permissions to Organization module. 2: Click on Organization from left side menu. 3: Click on Related Organization sublink. 4: Click on “+” 5: Click on Search existing organization field and search existing organization with location, phone, primary contact. 6: Select Organization Association and click “Save Organization”. Expected result: In grid are displayed all data respectively: relationship, organization name, organization id, organization type, primary contact, phone and location. Actual result: Fields ID, primary contact, phone and location are empty. | Fixed |
| When user logs out and try to login with another user, user logins with first user again | 1: Login with valid credentials. 2: Logout 3: Login with another user with valid credentials. Expected result: Second user is successfully logged in. Actual result: Even though second user credentials are inserted, first user is logged in again. | Fixed |
| Server error occurs when user navigate to Calendar | 1: Login as user that have permissions to Case/Complaints, admin modules. 2: Click on Admin from the left side menu. 3: Click on Security/Calendar Configuration 4: Enable calendar functionality for some module – cases for example and Save it. (Configure calendar with valid configuration). 5: Click on Cases from left side menu 6: Click on Calendar sublink. Expected result: User is navigated to Calendar no errors occur. Actual result: Server error occurs, see attachment. | Fixed |
| Calendar Issue – Creating Outlook folder when creating new Case or Complaint object | When creating a Case, probably not all required folders are created properly, or maybe there is issue to access them, so when trying to open calendar for that Case, error is thrown and Calendar event cannot be created. Detailed investigation is needed to locate the problem first. | Fixed |
| Person not created on new Compliant when new Organization is also created | Create a new Complaint Add an Initiator Click to Create the new Initiator Complete the first and last name Add in Identifier Add picture Create new Organization Save the Organization Save the Person Person is not persisted to Complaint form or within the Person module | Fixed |
| Organizational Hierarchy LDAP Group – cannot be expanded | Actual Result: 1. Go to Admin – Organizational Hierarchy page 2. Double click on ACM_ADMINISTRATOR_DEV users group 3. The ACM_ADMINISTRATOR_DEV folder is not expanded and it’s empty Expected Result: 1. Go to Admin – Organizational Hierarchy page 2. Double click on ACM_ADMINISTRATOR_DEV users group 3. The ACM_ADMINISTRATOR_DEV folder is expanded and users that belongs to that group are listed | Fixed |
| Edit LDAP Member – Date/Time format issue | Actual Result: 1. Go to Admin – Organizational Hierarchy page. 2. Select Ldap member from LDAP user group . 3. Edit the selected member 4. Changes are displayed for the edited user 5. Edit same user for second time 6 Error notification message is displayed and error in console “Internal Server Error]Could not read document: Failed to parse Date value ‘2017-06-23T04:00:00.000+0000′” Expected Result : 1. Go to Admin – Organizational Hierarchy page. 2. Select Ldap member from LDAP user group . 3. Edit the selected member 4. Changes are displayed for the edited user 5. Edit same user for second time 6. Selected user is successfuly updated. | Fixed |
| Task – Edit Start date issue | Actual Result: 1. Go to Tasks page 2. Select Task and edit the start date 3. Start date is not updated Expected Result : 1. Go to Tasks page 2. Select Task and edit the start date 3. Start date is updated | Fixed |
| Disable Calendar Integration | Actual Result : 1. Go to Admin-Calendar Integration page 2. Disable calendar Integration 3. Create new case 4. Calendar is visible for the created case Expected Result: 1. Go to Admin-Calendar Integration page 2. Disable calendar Integration 3.Create new case 4. Calendar is not visible for the created case | Fixed |
| Modified date in Notifications grid have some code data instead of dates | 1: Login as user that have permissions to Notifications module. 2: Click on Notifications from left side menu. Expected result: In grid are displayed correct Modified Dates , Actual result: Instead of dates are displayed some codes. See attachment.Please note that Modified Date is correctly displayed in Subscriptions and Search grids. | Fixed |
| LDAP User Managment – User is deleted before confirming | Step to Reproduce: 1. Go to Admin – LDAP user management page 2. Select user and delete it . Actual Result: User is deleted before confirmation pop up is displayed if the user want to delete it. Expected Result: User can be deleted only if the OK button is clicked when the popup is displayed with message ” Are you sure you want to delete this user?” | Fixed |
| Dashboard Widget assignee | Steps to reproduce: 1. Go to dashboard page. 2. Add widget (e.g My Cases, My Complaints) 3. Save the widget Actual result: In the widget table for assignee is displayed User Identifier Expected Result: In the widget table for assignee should be displayed full username | Fixed |
| People/Organization Participants – more than one owner allowed | Actual Scenario: 1. Navigate to participants section in People Module 2. Add another Owner in the Participants Table 3. More than one owner is allowed and displayed in the table Expected Scenario: 1. Navigate to participants section in People Module 2. Add another Owner in the Participants Table 3. Notification message is displayed that more than one owner is not allowed | Fixed |
| files named core.”en”.json prevent arkcase from starting | [~manoj.dhungana] has seen this at PRC, and I have seen it locally and on core dev server. Somehow, probably when saving labels or lookups, the system generates a file named core.”en”.json in the labels folder. This causes ArkCase to fail to start, since the config file watcher can not handle files with quotes in the file name. It’s not really a proper file name anyway…. the file name should not include quotes. | Fixed |
| Instead of Module name “Tasks” in preferences is displayed “Complants” | 1: Login as user that have permissions to Tasks module. 2: Click on down arrow next to username. 3: Click on Preferences. Expected result: All modules are displayed for configuration. Actual result: Instead of Tasks is displayed Complaints twise. See attachment. Only label is not correct because the configuration works as expected. | Fixed |
| Add/Delete items in the Grid component in all modules | When Adding or deleting item in the grid components in all modules, you have to do “hard refresh” to update changes in the grid. Solr is not automatically refreshing the UI. | Fixed |
| User can add same person as related more than once | 1: Login as user that have permissions to People 2: Click on People form left side menu. 3: Click on “Related People” sublink. 4: Click on “+” and select one person from existing people, select relation type and save it. 5: Click on “+” and select same person from step4, select relation type and save it. Expected result: same person should not be available in search after it is added once. Actual result: same person can be added more than once as related. See attachment. | Fixed |
| Edit Owner participants In People/Organization module | Actual Scenario: 1. Navigate to participants section in People Module 2. Edit Owner with user that does not belong to the Owning group in the participants table 3. Searched user is displayed in the search bar 3. Owner is updated. Expected Scenario: 1. Navigate to participants section in People Module 2. Edit Owner with user that does not belong to the Owning group in the participants table 3. User that does not belongs to the owning group is not displayed in the search bar as participant name | Fixed |
| Add Subgroup form for ad hoc group does not have title | 1: Login as user that have permissions to Admin module 2: Click on Admin from left side menu 3: Click on Security/Organization Hierarchy 4: Click on button for adding subgroup under some ad hoc group Expected result: Form opened have title. Actual result: Form opened is without title, see attachment. | Fixed |
| User can’t add more that one location | 1: Login as user that have permissions to complaints 2: Click on Complaints from left side manu 3: Click on “Locations” sublink. 4: Click on “+” icon 5: Insert all data and click Save button. 6: Click on “+” icon in order to insert one more location record. Expected result: “+” is visible and can be inserted more than one location. Actual result: only one location record can be inserted, because “+” icon is not visible after one insert. | Fixed |
| People table in Complaints is not displaying data | Steps to reproduce: 1. Create new complaint 2. Go to created complaint page 3. Go to people table Actual Result: Initiator is not displayed in the people table and new persons added are not displayed in the table Expected Result: Initiator is displayed in the people table . | Fixed |
| Standardize date serialization/deserialization across Arkcase application | The dates serialization in Arkcase is different in a lot of places. The issue are mainly the nanoseconds in the dates. Since Solr doesn’t accept nanoseconds in the date format and nanoseconds aren’t really useful for Arkcase, we should standardize on this date format *yyyy-MM-dd’T’HH:mm:ss’Z’*. One place to change is the _servlet-context.xml_ file. We should change *WRITE_DATES_AS_TIMESTAMPS* to *WRITE_DATE_TIMESTAMPS_AS_NANOSECONDS*. This is for serialization/deserialization of dates in our REST calls. Additionally we should remove the date format settings from all over the application and use the format defined in one place. Probably in the *acm-core-api* project. Same should be done in the UI. | Fixed |
| AFDP-3944 Technical Debt – Existing Outlook folder will become unaccessible when migrated to new version of Arkcase | The new version of Arkcase will look for username/password stored in the database to access the Outlook calendar folder associated with an object. After upgrading to the version of Arkcase that stores username/password per object entry, the existing Outlook folders associated with objects will not be accessible since there would be no entries for those objects in the database. We should have a solution in place, that if there is no entry in the database for given object, the system will try to access the Outlook folder with the configured credentials, and if successful, create an entry for that object in the database. If not, we can assume that either the credentials are no longer valid, or the folder should be recreated. In case of invalid credentials, action by administrator should be taken. In case that a folder should be recreated, then the folder can not be recreated in batch, since there is no entry for the given object, and it would not be recreated by the administrator action `recreate folders`. The folder for such objects should be recreated individually. The possible sequence should be: 1. Search for entry in the database to access the Outlook folder associated with the object 2. In case there is no entry, try to access the folder with the stored credentials 3. If the folder can be accessed, add entry in the database. 4. If the folder can not be accessed, try to recreate it and add entry in the database for that object 5. If the folder can not be recreated, assume that the credentials are invalid, and inform the administrator. | Fixed |
| Team Workload Widget | 1. Log into the application 2. Click the enable edit mode icon (pen and paper icon) in the top right hand corner of the Dashboard 3. Click the add new widget icon (circle plus sign icon) in the top right corner of the Dashboard 4. Click the ‘Team Workload’ Widget (bug)Team workload widget is displayed in the dashboard but error occurs in the console:ypeError: Cannot read property ‘due’ of undefined at application.js:20079 at vendors.min.js:323 at n.$eval (vendors.min.js:338) at n.$digest (vendors.min.js:335) at n.$apply (vendors.min.js:338) at HTMLButtonElement. (vendors.min.js:600) at HTMLButtonElement.dispatch (vendors.min.js:3) at HTMLButtonElement.r.handle (vendors.min.js:3) | Fixed |
| Adding a Second Initiator in People node for cases and complaints should not be permitted (only one initiator allowed) | Actual Result: 1. Go to New case page 2. Create case. 3. Go to People section of the created case. 4. Add existing person with association type Initiator (same person initiator as one of the created case) 5. Second Added initiator is displayed in the table. Expected Result: 1. Go to New case page 2. Create case. 3. Go to People section of the created case. 4. Add existing person with association type Initiator (same person initiator as one of the created case) 5. Initiator with same credentials as the of the created case can not be added Note: In new case frevvo from only one initiator can be added, but in people table of the created case multiple initiators can be added (even same person multiple times as initiator ) | Fixed |
| AFDP-4520 Create “Forgot Username” functionality on Login Page | Create “Forgot Username” functionality on Login Page Use Case: 1. Got to ArkCase login page 2. Click on “Forgot Username” (See Attached SS – ForgotUsername.png) 3. User must enter email address on account in ArkCase and hit save 4. User will get a confirmation module box on save (See Attached SS – ForgotUsernameConf.png) 5. Then the system checks to make sure that is valid email address and that there is a username in ArkCase. 6. If there is a valid username, an email will be sent to that email account with the username and a link to the ArkCase login page | Fixed |
| Instead of value is displayed id from label configuration for profile.modal.differentPasswords | 1: Login with valid user. 2: Click on down arrow under user name and click Profile 3: Click on “Change Password” button in top right corner. 4: Insert correct old password and different passwords in fields for confirming new password and click “Save Changes” button. Expected result: value of label configured in label configuration is displayed. Actual result: Id of label configured in label configuration is displayed. | Fixed |
| When case is created duplicate object is displayed in treeview | 1: Login as user that have permissions to cases module 2: Click on New/Case 3: Insert all required data and submit it. Expected result: In tree view is displayed at the top only one new created object, Actual result: Duplicate object is displayed in treeview.Please note that this is working correctly for complaints and other objects. | Fixed |
| Even though all widget are enabled for group, user can add only some of them on dashboard | 1: Login as user that have permissions to Admin module 2: Click on Admin module from left side menu. 3: Click on Dashboard/Dashboard Configuration 4: Select all widgets one by one and add group in which current user is member (in my case I added ACM_ADMINISTRATOR_DEV) to Authorized for all widgets. 5: Click on Dashboard from left side menu. 6: Click on “Enable edit mode” button in right top corner. 7: Click on “+” icon. Expected result: All widgets enabled in step 4 are displayed in list and can be added. Actual result: not all widgets are available for adding. See attachmentsIf some of the widgets are not applicable, they should be removed from list in Admin module. *Widgets available in dashboard configuration: * Aliases; Approval Routing; Calendar; Cases; Cases By Queue; Cases By Status; Complaints; Cost; Dbas; Details; Doc Review; Documents; Emails; Expenses; Faxes; History; Hours Summary; Ids; Locations; My Cases Widget; My Complaints Widget; My Tasks Widget; New Cases; New Complaints; News Widget; Notes; Organizations; Parent Docs; Participants; People; Person; Phones; Pictures; References; Rel Organizations; Related; Rework Details; Signature; Tags; Tasks; Team Workload; Time; Urls; Weather Widget; Workflow; Workflow Report*Widgets that can be added, even though user is authorized for all: * Active Case Files by Queue Cases By Status My Cases My Complaints My Tasks New Complaints Team Workload Weather News New Cases Workflow Report | Fixed |
| Admin – Org Hier – Delete LDAP Group Error | {html}Delete LDAP Group Error – Just as an FYI, I can delete Adhoc groups with no problem.
vendors.min.js:297 DELETE https://cloud.arkcase2021.arkcase.com/arkcase/api/latest/ldap/armedia/groups/MATT_TEST 400 (Bad Request) (anonymous) @ vendors.min.js:297 n @ vendors.min.js:293 g @ vendors.min.js:290 (anonymous) @ vendors.min.js:323 $eval @ vendors.min.js:338 $digest @ vendors.min.js:335 $apply @ vendors.min.js:338 (anonymous) @ vendors.min.js:600 dispatch @ vendors.min.js:3 r.handle @ vendors.min.js:3 vendors.min.js:311 service call error:[400, Bad Request]Could not Delete LDAP group with ID = -1. Server encountered exception: Removing LDAP group failed! Exception type was: ‘com.armedia.acm.core.exceptions.AcmUserActionFailedException’. {html} |
Fixed |
| AFDP-4520 Create “Forgot Password” functionality on Login Page | Create “Forgot Password” functionality on Login Page Use Case: 1. Got to ArkCase login page 2. Click on “Forgot Password” 3. User must enter email address and username on account in ArkCase and hit save 4. User will get a confirmation module box on save (See Attached SS – ForgotPasswordConf.png) 5. Then the system checks to make sure that the email address and username is valid 6. If the email and username are valid, an email will be sent to that email account with the username, temp password, and a link to the ArkCase login page | Fixed |
| Complaint reference not saving inverse relation – different behavior than case reference | When saving a reference from complaint module, inverse relation is not saved. Bi-directional link is not maintained in the target object as a side-effect. The code in complaint reference controller is different than case and it needs to be similar to the case reference. Steps to reproduce : – Complaint > References – Add new reference – Add a case file – Reference saved, click on the case file – Inverse relation missing in the case file, hence no reference displayed – Do the same for case module i.e add a complaint reference to a case file, inverse relation is saved, and links work both ways | Fixed |
| Participant table is empty in document repository module | 1: Login as user that have permissions to Document Repository module. 2: Click on Documents from left side menu. 3: Click on Participants sublink. Expected result: 2 rows are displayed with values for assignee and owning group. Actual result: table is empty. Same issue in “My Documents” | Fixed |
| Admin – Org Hier – Validation Errors | 1: Add LDAP group without populating any fields, Validation will not let you save with empty fields, The window closes like it saves. | Fixed |
| Consolidate Reference Tables and functionality in all modules | In order to have consolidated UI experience, we should have same columns in the “Reference” Table for all modules (Case, complaint, task) and in the “Add Reference” pop-up window, where user can chose from the list of referenced objects, based on previous search. Please see the comments bellow and SS attached | Fixed |
| In participant table id is displayed, instead of value of title label | 1: Login as user that have permissions to Cases/Complaints 2: Click on Cases/Complaints from left side menu 3: Click on Documents sublink. 4: Right click on some document and click Open 5: Click on Participant tab, Expected result: Participant grid value (configured in Admin/Label Configuration) is displayed. Actual result: instead of value is displayed id of label. | Fixed |
| Document Audit records not created – Notes adde… | Document Audit records not created – Notes added – Tag added | Fixed |
| Person > Email type is not persisting Created a… | Person > Email type is not persisting Created a Person with an email and the email type did not persist Afterwards, updated the email type and it still did not persist. | Fixed |
| Add Signature to User Profile that can be used as an annotation on Snowbound | Add Signature to User Profile that can be used as an annotation on Snowbound. Signature can be edited from Users Profile. This signature can be added to an image level. The signature will be user specific and will be governed by ACL. | Fixed |
| New Case/Complaint (Frevvo) – Adding Participants – Owning group membership issue | In Frevvo forms for creating new Case or Complaint, there is an option for adding participant. Following the rule that Owner has to be part of owning group, there is a restriction not to list participants that are not members of the previously selected “Owning group” (in the User picker pop-up window). This is working fine, BUT there is an issue in the reverse scenario: – leave “Owning group” field empty – choose “Owner” in “participant type” field – Chose Ann Administrator (member of ACM_ADMINISTRATOR group) from the User picker pop-up – then, go to “Owning group” drop down list and chose some other group, ex. ACM_INVESTIGATOR Result: Case will be created with Owner: Ann Administartor and “Owning group”: ACM_INVESTIGATOR. – Error Expected Result: If owning group that is selected from the drop down list, is not the group where previously selected owner is member, then “participant name” field should be set to null. User has to choose new participant from the user picker, that will now list only users related to the selected owning group. One more issue here: Participant type list in drop-down is not filled with all types. But, This should be fixed with managing dropdowns through Admin part | Fixed |
| Log-out Keeps Previous User’s Information | *Description*: When a user logs out and then logs in with a different user, the original user’s information is show in the UI. *Environment:* https://core.arkcase.dev.armedia.com/arkcase/ *Steps to Reproduce*: # Login as ‘ann-acm’ # Log out # Login as ‘samuel-acm’ *Actual Result*: System shows ‘ann-acm’s username and modules. *Expected Result*: System shows ‘samuel-acm’s username and modules. | Fixed |
| People module – Remove/Hide buttons “Merge”, “Import” and “Export” | Merge, Import and Export functionalities for People module are not implemented yet. Until we have these functionalities, these buttons should be removed/hide from UI, for better user experience. | Fixed |
| Creating new Organization – adding new Peron in it, and adding existing Organization for that person | When creating new Organization, user can add “NEW Person” within “People” node. In that “New Person” modal window, user can add existing Organization – that person cannot be saved. | Fixed |
| “Incident Category” drop down list in complaints does not takes values configured in Admin/lookups configuration | 1: Login as user that have permissions to Complaints. 2: Click on New/Complaint 3: Click on “Step 2: Incident” tab 4: Click on Incident Category drop down list. Expected result: values configured in Admin/Lookups configuration, Actual result: Option1, Option2 and Option 3 values are displayed. | Fixed |
| There is no rule for complexity for password change – it can be changed to 1 character password | 1: Login as valid user 2: Click on down arrow next to username under profile picture. 3: Click on Profile 4: Click on “Change Password” button. 5: Insert current password and 1 character password in fields for new password. Expected result: There should be policy for changing password and system should not allow submitting simple passwords. Actual result: Password with 1 char is accepted.Same issue on “Store Outlook Password”. | Fixed |
| Missing “People” and “Locations” links in tabbed footer in complaints | 1: Login as user that have permissions to Complaints module. 2: Click on Complaints from left side menu. , 3: Expand top item in tree view. Expected result: links from tree view match links in tabbed footer. Actual result: missing “Locations” and “People” links in tabbed footer menu. | Fixed |
| AFDP-4542 New: Approval Routing Functionality – Change the routing process to add the initiate and withdraw actions which would be triggered on a signal vs user task | New: Approval Routing Functionality – Change the routing process to add the initiate and withdraw actions which would be triggered on a signal vs user task – Initiate: This would trigger the first approval routing task in the list and would continue to try and pull the next approval task in the task order. Every time a new task is added to the approval task table, there should be a check to see if that is the current active task and if so, it should be automatically initiated, if the approval tasks have already been initiated. – Withdraw: All tasks in the Approval Task Table will be will be deleted and new Approval tasks will need to be added? | Fixed |
| AFDP-4542 New: Approval Routing Functionality – Update the approver service to add the subject, details, due date | New: Approval Routing Functionality – Update the approver service to add the subject, details, due date | Fixed |
| AFDP-4542 New: Approval Routing Functionality – Enhance the current services | New: Approval Routing Functionality – Enhance the current services | Fixed |
| New folder/New document can’t be created in Attachments under tasks | 1: Login as user that have permissions to tasks module. 2: Click on Attachments link. 3: Right click on parent folder. 4: Click on New Folder Expected result: folder is successfully created Actual result: folder is not created service call error – forbidden, see attachmentsSame happens with adding documents. The documents are not successfully added. | Fixed |
| AFDP-4358 Update parent company | When a parent company relationship is added, the UI part showing the parent company should be updated to reflect the change on the back-end. Currently, it still shows the old parent company until the UI is hard-refreshed. | Fixed |
| AFDP-4358 Use new endpoint for searching organizations. | When searching for organizations for creating a new association, the new endpoint should be used, that excludes the organization itself and it’s ancestors, to avoid creating cyclic dependencies. | Fixed |
| “User has no granted permission for this action” – 403 forbidden error occurs when user navigate to Cases/Complaints – only for some users | 1: Login as user that have permissions to Cases/Complaints. 2: Click on Cases/Complaints from left side menu. Expected result: No error message on top left corner is displayed. Actual result: “User has no granted permission for this action.” message is displayed in left top corner.Please note that user have permissions to create cases/complaints and edit them. | Fixed |
| Organization > Parent Organization top header W… | Organization > Parent Organization top header When adding a Parent Organization via the top ribbon, it does not add the Related Organization to either the table within the two Organizations. Expected outcome: Parent Organization listed in top ribbon Organization > Related Organizations – entry added for both the parent and child organization History Event added for both Organizations *Reporter*: James Bailey *E-mail*: [mailto:james.bailey@armedia.com] | Fixed |
| Organization – Parent organization issue | “Parent Organization” in the Organization “top ribbon” should be same as “Parent company” we have in “Organization Relation Associations”. As it is now, these 2 attributes are no connected. Example scenario: 1. User adds organization “X” as Sub-Company to organization “Y” 2. Relations works fine and if we go to organization “Y”, in the “Related Organization” node, there is organization “X” as “Parent Company”. But on the top ribbon, “parent Organization” is still “Unknown” !08_24_Parent company.png|thumbnail! Another problem is that there is no have restrictions on how many parent companies can be added. !08_24_Parent company 2.png|thumbnail! One company (Organization) can have only one “Parent” company and many “Sub-companies”. | Fixed |
| AFDP-4358 Notify parent organization assignement | When a new organization association is created, in case a “SubCompany” type is selected, the user should be notified that the organization at the “SubComopany” end of association will have a parent company set. If it had a parent company set before, it will be removed, as well as the association to the previous parent. | Fixed |
| Admin – Calendar Configuration – Calendar Still Accessible | 1: Unselect Enable calendar configuration for Case Module, The Calendar sublink in the case module should be removed , It is still accessible. | Fixed |
| Allow full Solr reindex per object type | Currently if you want to do full Solr reindex for a particular object type, the only way is deleting {{solrLastBatchUpdate.properties}} file, which will in turn trigger reindexing of all object types, which is usually not what we want. That also puts a huge load on Solr, which is not able to cope with that many update requests and fails with OOM errors. | Fixed |
| Approval Routing notification to Assignee on approval or rejection | Whenever a user approves or disapproves from the Approval list, we should send a notification to the Assignee and the Initiator if they are different users. | Fixed |
| Calendar: Edit Event Attachments | Actual Situation: 1. Documents are attached on creating New event 2. Event is created 3. On edit event, previously attached documents are not displayed Expected : Scenario 1. Documents are attached on creating New event 2.Event is created. 3. On edit event, documents can are displayed and changes cane be made | 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 |
| Notification message should be displayed if user try to add already existing ldap/ad-hoc group | 1: Login as user that have permissions to Admin module 2: Click on Admin from left side menu 3: Click on Security/Organizational Hierarchy 4: Click on “Add add-hoc group” link 5: Insert already existing name in group name and click “Add Group” button. Expected result: Validation message is displayed informing user that group already exists. Actual result: exception occurs in dev tools console. | Fixed |
| Details component is missing in “New Person” and “New Organization” forms when user try to add them to some object (Case, complaint, people, …) | 1: Login as user that have permissions to People module 2: Click on New/Person 3: Click on Organizations link 4: Click on “Search Existing Organization” field. 5: Click on “Add new Organization” button Expected result: opened form have all for entering. Actual result: Form is missing Details section.Please note that same issue occurs if user want to insert new organization and then from people section to add new person. | Fixed |
| AFDP-3202 Provide localization for data from backend | Some data from back-end needs to be translated to display in UI. For example drop down list, task outcome button text, and some server side messages. Provide solution for localize data from back-end. | Fixed |
| AFDP-3202 Localize lookups in Complaint, Case, and Task pages | -Translate back-end data for Complaint, Case, Task modules- As development progress, the original plan of this ticket has changed. As a result, this ticket solved following i18n issues: * caseTypes/ComplaintTypes pull donw * Priority pull down * Dates format fix in info panels * Task outcome buttons | Fixed |
| AFDP-3202 i18n for user profile page | Internationalization for user profile page | Fixed |
| AFDP-3202 i18n for preference page | Internationalization for preference page | Fixed |
| AFDP-3202 Fix missing lables for Core module | Fix missing labels for other languages for Core module and provide translation as needed. Lookup entries among them are needed to help identify where localization is not done, to help testing, and to make UI look better. | Fixed |
| AFDP-3202 I18n for task outcome buttons in Task page | Internationalization for task outcome buttons in Task page | Fixed |
| AFDP-3202 i18n for Report page | Date pickers and State dropdown | Fixed |
| Primary Url mark label [Primary] is under the URL name (not readable) | 1: Login as user that have permissions to People module. 2: Click on People module from left side menu. 3: Click on some record with added urls (or add new by yourself) 4: Click on URLs sublink. Expected result: Primary record is marked with [Primary] label as other records. Actual result: [Primary] record is not marked. See attachment Other issue here is that setting URL as primary is not working. Edit URL/Set as Primary, should change the [Primary] label to the newly set primary URL and remove “delete” icon from that URLOther Issue: URL type not displayed in the grid | Fixed |
| AFDP-4679 Fix Admin page label resource | Fix Admin page label resource | Fixed |
| File types Lookups | Actual Result: 1. Go to Admin – Lookups configuration page. 2. Add Lookup for file types 3. Go to (e.g) Cases documents section 4. Select the Root folder and click on add file icon (in the Documents table header) 5. Add lookup is not displayed as dropdown option Expected Result: 1. Go to Admin – Lookups configuration page. 2. Add Lookup for file types 3. Go to (e.g) Cases documents section 4. Select the Root folder and click on add file icon (in the Documents table header) 5. Add lookup is displayed as dropdown option | Fixed |