ASWB Central Release Notes
- Robert Adach
Owned by Robert Adach
Desktop Application
Version TBD
Release Date:
- To Test: TBD
- To Produciton: TBD
| Item Number | Summary | Description | Audience | |
|---|---|---|---|---|
| 1 | B-383 | PPD Searches are not being completed as expected | An issue was reported where the ASWBCentral desktop system was indicating that no PPD results were found, when the staff expected one to be returned. A workaround was introduced into Production to address the issue temporarily, and we have addressed the issue within the code for a permanent solution. | MSERV |
| 2 | B-386 | "Status Notes" entered for an application are not being stored | When you use the "Add New Status Audit Note" function, although the note entered appears in the grid initially, if you leave the application and return it is no longer there, and it is not saved to the database. A workaround was introducted into Production to alleviate this issue and a permanent solution was applied to the application in this release. | MSERV |
| 3 | B-387 | Workflow Audit Notes not being stored when performed by Staff | If an ASWB Staff member makes a change to a value, the value change is being saved to the database, but the data change log within the application is not reflecting the issue. | MSERV |
| 4 | B-409 | When sending an approval to Exam Services, the Last Name and Suffix should be concatenated | In ASWB Central we store the Last Name and Suffix as two fields, but in ALL legacy systems they are stored in one. When we send an approval over we are not including the suffix which results in the user not being able to register for their exam if the approval name is different than their ID. This has been addressed in Production with an emergency patch release. | MSERV |
| 5 | B-414 | Unable to delete applications with "Application Locks" | When attempting to delete an application which has one or more Application Lock records, the system threws an error message and the application was not deleted. This has been corrected to allow the application to be deleted. | MSERV |
| 6 | US-251 | As a system, I should use the defined contact information within email templates | The email template engine has been updated to allow us to dynamically insert Board and ASWB contact information. This will allow us to use a single version of an email template, but generate the appropriate contact information before sending it. | MSERV |
| 7 | US-265 | As a System, I should display the proper areas for a user based on their assigned roles | With the expansion of usage, the ASWBCentral desktop application will now need to display information based on the role(s) assigned to the user. This allows us to provide users with information relevant to their teams/departments, and segments access further. | MSERV |
| 8 | US-376 | As a system, I should only access information needed by the immediate process | We have reduced the amount of information we are initially accessing when a user opens an application on the web or desktop. This has resulted in a reduction in inital access time and memory utilization. | MSERV |
| 9 | US-417 | As a system, I should be able to migrate application data from another system | We are migrating all of the UT applications from LAP Manager into ASWB Central. This will allow the UT board to access one portal for all of the application details, and MSERV staff will only have to access the ASWBCentral system for any UT Application. | MSERV |
| 10 | US-441 | As I system I must be able to determine the accreditation validity of a school based on a users accreditation. | UTAH requires that individuals who indicate that they have graduated with a BSW or MSW must have done so from a school which held a CSWE or CASWE accreditation during the period of graduation. As the accuracy of the accredittation data is suspect, we do not want to alert the user to any possible issues with the data they are providing. This feature allows us to identify if a school was accreddited at the time the user attended it. | MSERV |
| 11 | B-340 | Incorrect reply-to used on GRPT emails | Emails sent fwhen GRPT orders are processed incorrectly contained IT staff email addresses when someone replied. This was addressed Production with a temporary workaround. | GRPT |
| 12 | US-374 | As a system, any code exceptions should be handled gracefully | We have overhauled the error handling within the system to provide a more user friendly experience and additional logging for investigative purposes. | ALL |
Version 1.2.0.1141
Release Date:
- To Test: 4/17/2018
- To Produciton: 4/17/2018
| Item Number | Summary | Description | Audience | |
|---|---|---|---|---|
| 1 | B-409 | Applicants Last Name appears incorrectly in CSC | When sending an approval to CSC, we were not including the "Suffix" of the record as part of the last name field. This has now been corrected. | MSERV |
| 2 | B-386 | The entry of "notes" into an application are not being saved | Although staff were able to enter notes into the Event tab, they were not saved to the record when the staff member left the record. This has now been corrected. | MSERV |
Version 1.2.0.1040
Release Date:
- To Test: 2/22/2018
- To Produciton: TBD
| Item Number | Summary | Description | Audience | |
|---|---|---|---|---|
| 1 | US-239 | As a system I should be able to update ASWBCentral with exam approval, registration and result details | Beginning in release 1.2 we will be expanding the data held within the database related to the approvals, registrations and examination results for Applications. | MSERV |
| 2 | US-230 | As a system, I should display email history to staff members | Corrected the following issues with viewing emails in the Desktop Application 1) If the data within a field is too long to fit within the current width, it should be wrapped to the next line (Currently the TO field is not properly wrapping) 2) The width of columns shown on the Email History grid should be adjustable by the end user. 3) When selecting an email message, the window that pops up should display the same information shown on the grid | MSERV |
| 3 | US-228 | As a system, I should report exam results to applicants | Added functionality for the system to gather and report email results to the applicant | MSERV |
| 4 | US-218 | When deleting an application, all associated data should be deleted from the database | Updated the existing delete functionality to ensure all data associated to a workflow is deleted when we delete an application. | MSERV |
| 5 | US-214 | As a system I should store the following items for a Jurisdiction | Expanded the demographics for Boards and associated them to ASWB teams to allow for tailored message content. The Demographics include the following: Jurisdiction Location Name - Full state/province name where the Jurisdiction operates Jurisdiction Location Abbreviation - Two letter state/province abbreviation where the Jurisdiction operates Board Name - The full name the Board should be referred to as (i.e. Colorado Department of Regulatory Agencies) Board Name Abbreviation - The abbreviated name the Board should be referred to as (ie. DORA) Board Contact Number - The phone number to provide to end users to contact the board Board Email address - The email address to provide to end users to contact the board Board Address - The address to provide to end users to contact the board Board URL - URL to provide to end users to contact the board ASWB Contact Number - The phone number to provide to end users to contact the ASWB team ASWB Email address - The email address to provide to end users to contact the ASWB team ASWB Address - The address to provide to provide to end users to contact the ASWB team ASWB From address - The from address to use when sending emails from the ASWB Team for the jurisdiction | MSERV |
| 6 | US-212 | As a system I should refer to the database for configuration values and attributes | Centralized the storage (and added necessary encryption) to certain application configuration values. | MSERV |
| 7 | US-205 | As a user, I should be able to delete an application which has not been imported | Added a utility for ASWB Staff to delete an application which has not been submitted on behalf of the applicant | MSERV |
| 8 | US-104 | As a user I should be able to run a report of Exam Status for applications | Updates to report showing applications that are Approved for Exam and have had test results reported | MSERV |
| 9 | T-229 | Standardize Configuration Settings | To increase the flexibility of the system all system configuration settings will be stored in the database rather than within the codebase. | MSERV |
| 10 | T-227 | Create base db contexts for the connections to the DARS, Registry and CSC Approval | Simplified the way in which the system is connecting to various ASWB databases to increase performance | MSERV |
| 11 | T-215 | Audit Logs should retain actual before and after values | When recording changes to data, the system now shows the actual values selected from dropdowns/checkboxes rather than their index values. | MSERV |
| 12 | T-206 | Improve file upload handling | 1) Added a visual indicator to confirm a file upload was successful when uploading files associated to questions 2) On the documentation screen, the File Upload and Notes action are now the same control making it easier to upload. 3) When saving a file via the desktop, we are now saving the date and time the file was uploaded into the system | MSERV |
| 13 | B-275 | Reports are not showing all information when exported | Corrected an issue where only a limited number of records were being sent to the Excel document when exporting. Also added summary information to onscreen reports for Management Status report. | MSERV |
| 14 | B-237 | The email template substitution variable {{FullName}} does not populate in Desktop based emails | Corrected an issue where the email templates were not populate the Applicants first name in certain emails. | MSERV |
| 15 | B-210 | Payment Audit Notes are incomplete | Adjusted the way in which we are saving the audit notes when capturing payments to include the association to the payment directly. This affects logging only. | MSERV |
Version 1.1.0.880
Release Date:
- To Test: 11/28/2017
- To Produciton: 12/18/2017
| Item Number | Summary | Description | |
|---|---|---|---|
| 1 | US-178 | New report to identify applications waiting for CSC to accept | A new report has been added "Waiting for CSC" which will show all applications which have been approved by Member Services, but not yet imported by CSC. |
| 2 | US-178 | Improved report exports | All reports now will now export to excel directly, and will format the results. Export will include report filter dates and the timestamp when the report was generated, |
| 3 | US-178 | Show candidate ID when CSC Approval is accepted | The Application Details section when selecting a record on the dashboard, and the Overview tab when inside an application will now indicate the Candidate ID. The following logic is used for the field:
|
| 4 | B-185 | Refresh button not refreshing when changes made from Web or other non-desktop sources | The refresh button will now circumvent the standard change tracking and will requery all necessary data to ensure the updated information is available. |
| 5 | US-191 | Increased MessageType field for auditing | For auditing purposes, the MessageType field was changed from 16 to 64 characters |
| 6 | US-193 | Introduce a "threaded" conversation datatype | To support the Board portal process, we have developed a new data type called "Threaded discussion" which will keep a log of the previous updates to the field and encapsulate them with a timestamp and the user who entered them. The historical "thread" is read-only. |
| 7 | B-194 | Corrected the saving of the date the application when from Awaiting Initial Documents to In Progress status | The timestamp of the event where the Application when from 'Awaiting Initial Documents' to 'In Progress' was being saved in an incorrect field and has been updated to ensure accurate reporting. |
| 8 | US-174 | Lock a record when accessed by the desktop application | When a record is opened via the desktop system, it is locked and other desktop users will not be able to access the application until the first user exits the application workflow. If a user is disconnected due to connection issues, system crash, etc. the system will unlock all records for that user the next time they log into the system. |
| 9 | Misc | Allow a Production and Test verison of the application to run at the same time | The ASWBCentral application will now allow users to have a Test and Production version of the application open at the same time. |
| 10 | US-113 | Allow applications to be assigned to a user | Introduced the ability for the system to assign an application to the current user when it is imported, and allow the staff to change/update assignments through the Event tab. |
| 11 | B-222 | Error when uploading file from the Transcript section | Resolved an issue that occurs when a Desktop user tries to upload a file in the Transcript section if certain conditions are met. |
| 12 | T-225 | Display a meaningful value when uploading files on the desktop | In situations where there is not a defined "note" value for a file being uploaded, the system will now show a note of "<Workflow Step Name> Documentation>" Where <Workflow Step Name> is the workflow step associated to the question where the upload occurred. This only affects the Qualifying Questionnaire file upload at this time. |
Version 1.0.0.745
Release Date: 11/8/2017
| Item Number | Summary | Description | |
|---|---|---|---|
| 1 | US-162 | Internal App Revenue Report should include summary data | When viewing or exporting the Internal App Revenue Report, we will now show summary data which includes:
|
| 2 | F-39 | Changes to application data through the desktop application is immediately saved | When updating data on the Desktop Application, certain data was not immediately saved and transferred to the database. In cases, when the application terminated unexpectedly, or exceptions were thrown, data was not saved, or the mapping to "base data" because out of sync. With this release, data changes are saved once the field focus is lost (user tabs to another field, clicks off the field, navigates to another tab). |
| 3 | F-39 | Update "mapped" data on value change | When data which resides at either the Applicant and/or Application level that is propagated from Workflow Data, the system will now ensure that the mapped data is immediately updated. This includes fields like, Exam Level, SSN, Date of Birth. |
| 4 | Gen | Performance Improvements | We continue to attack and address performance issues throughout the application. |
| 5 | US-133 | Delete Files from the Documents Tab | We have activated the ability to delete files from the "Documents" tab. |
| 6 | B-174 | Birthday sent to CSC Approval is incorrect | We corrected the issue where CSC Approvals were being sent with the incorrect date in the Approval field. |
| 7 | B-182 | Desktop users receive error when trying to upload a file | Application was referencing an incorrect file location when trying to upload from a local users system. |
Web Application
Version 1.3.1.1406
Release Date:
- To Test: 6/20/2018
- To Production: TBD
| Item Number | Summary | Description | Audience | |
|---|---|---|---|---|
| 1 | B-369 | Board Portal search fails when a record has no SSN | When conducting a search in the Board Portal if one or more of the records included in the result has no SSN the system would generate an error. In this release we addressed the issue and the records will return with no error | MSERV |
| 2 | B-414 | Unable to delete applications with "Application Locks" | When attempting to delete an application which has one or more Application Lock records, the system threws an error message and the application was not deleted. This has been corrected to allow the application to be deleted. | MSERV |
| 3 | US-197 | As an applicant, I should be able to edit an existing application I have submitted | Applicants are now able to edit applications which are in "Problem" status. The applicant will only be able to edit their responses to questions whose "Master Control" are set to "Not Yet Checked" or "Problem" statuses. | MSERV |
| 4 | US-240 | As a system, I should display display Jurisdiction/Context specific contact information and FAQ on the website. | We have updated the system so that it is contextually aware of where the user is located and will display relevant information within the application and help areas based on the users Role (when in the portal), or the Jurisdiction/License/Application type (when inside an application process) | MSERV |
| 5 | US-251 | As a system, I should use the defined contact information within email templates | The email template engine has been updated to allow us to dynamically insert Board and ASWB contact information. This will allow us to use a single version of an email template, but generate the appropriate contact information before sending it. | MSERV |
| 6 | US-376 | As a system, I should only access information needed by the immediate process | We have reduced the amount of information we are initially accessing when a user opens an application on the web or desktop. This has resulted in a reduction in inital access time and memory utilization. | MSERV |
| 7 | US-417 | As a system, I should be able to migrate application data from another system | We are migrating all of the UT applications from LAP Manager into ASWB Central. This will allow the UT board to access one portal for all of the application details, and MSERV staff will only have to access the ASWBCentral system for any UT Application. | MSERV |
| 8 | US-324 | As an authorized user, I should be able to create a new user account and associate to my Organization | For the GRPT process (and later the ACE Process) it is necessary to allow authorized users the ability to add new users to their Organization record. For example with GRPT, it is recommended that they provided a unique login for each Faculty member that will be accessing the system for reporting and security purposes. In this release we have added the ability to add a new user to the ASWBCentral system and grant them rights to an Organizations GRPT records. | GRPT |
| 9 | US-325 | As an authorized user, I should be able to add an existing ASWBCentral account to my Organization | We have added the ability to add an existing user (one who already has a ASWBCentral login) to an Organizations account so they may access the schools GRPTs | GRPT |
| 10 | US-326 | As an authorized user, I should be able to remove another users account from my Organization | Authorized users will now be able to remove user access from their account. | GRPT |
| 11 | US-327 | As an authorized user, I should be able to remove my account from an Organization account | Any user associated with a school, may remove their access to the school as long as 1) there is at least one other user on the account and 2) if the user is an Admin for the School, there must be one other active Admin on the school account. | GRPT |
| 12 | US-416 | As a school Admin, I should be able to change the roles associated to my faculty | We now have two different levels of permissions for GRPT users. 1) Admin - which allows a user to add/remove users from the school and access the purchased GRPT instances and 2) Staff - who only have access to the purchased GRPT instances. We allow anyone with Admin roles to change the role of other users associated with their school. The exception is that we will not allow a change to a record if it results in NO admins being associated with the school. | GRPT |
| 13 | US-287 | As a System I should not allow anyone to log in if JavaScript is NOT enabled | As several parts of the site require JavaScript functionality, we must ensure that anyone attempting to login has JS enabled, and if they do not, they should not be allowed to proceed. Users will be displayed a message indicating that they must enable JavaScript in order to continue | ALL |
| 14 | US-374 | As a system, any code exceptions should be handled gracefully | We have overhauled the error handling within the system to provide a more user friendly experience and additional logging for investigative purposes. | ALL |
Version 1.2.0.1065
Release Date:
- To Test: 2/15/2018
- To Production: 4/1/2018
| Item Number | Summary | Description | Audience | |
|---|---|---|---|---|
| 1 | US-253 | As a system I should ensure that we are able to capture all Authorization attempts | We have altered the way in which the system creates, tracks and updates CC payments when an application is submitted to ensure that we capture payment attempts properly when a user receives an authorization, but does not complete the application process correctly. | MSERV |
| 2 | US-250 | As a system I should store GRPT Item banks in the database | In order to support the new GRPT versions becoming available on April 2nd, we have expanded the system to allow for GRPT related Stems, Options and Rationales to be stored in the database | GRPT |
| 3 | US-248 | As a system, I should log specific data about a session and display the data via reports. | In order to provide the level of reporting identified by the GRPT stakeholders, the system will now track the order of pages viewed during a GRPT session, and the duration on each page. | GRPT |
| 4 | US-246 | As a system, I should display the items for a selected GPT instance | The system will allow an authorized user to see all of the items (Stems, Options and Rationales) for the the selected instance of a purchased category. | GRPT |
| 5 | US-244 | As a system, I should display a "Dashboard" for the GPT | The system will now allow a user to see a "Dashboard' when they log in of all GRPT instances they have access to. | GRPT |
| 6 | US-243 | As a system, I should allow a school to login | The system will now allow authorized users to login on behalf of their school to access GRPT categories purchased | GRPT |
| 7 | US-224 | As a user, I should be able to see all email communications I have received | Added the ability for web users to see all emails that they have received from ASWB in a single centralized location | MSERV |
| 8 | US-218 | When deleting an application, all associated data should be deleted from the database | Updated the existing delete functionality to ensure all data associated to a workflow is deleted when we delete an application. | MSERV |
| 9 | US-214 | As a system I should store specific information about a Jurisdiction for each ASWB team | Expanded the demographics for Boards and associated them to ASWB teams to allow for tailored message content. The Demographics include the following: Jurisdiction Location Name - Full state/province name where the Jurisdiction operates Jurisdiction Location Abbreviation - Two letter state/province abbreviation where the Jurisdiction operates Board Name - The full name the Board should be referred to as (i.e. Colorado Department of Regulatory Agencies) Board Name Abbreviation - The abbreviated name the Board should be referred to as (ie. DORA) Board Contact Number - The phone number to provide to end users to contact the board Board Email address - The email address to provide to end users to contact the board Board Address - The address to provide to end users to contact the board Board URL - URL to provide to end users to contact the board ASWB Contact Number - The phone number to provide to end users to contact the ASWB team ASWB Email address - The email address to provide to end users to contact the ASWB team ASWB Address - The address to provide to provide to end users to contact the ASWB team ASWB From address - The from address to use when sending emails from the ASWB Team for the jurisdiction | MSERV |
| 10 | US-213 | As a system I should be able to restrict users access to specific jurisdictions | Added the ability for the web site to limit access to information based on the Jurisdiction they are associated with (Board Members only) | MSERV |
| 11 | US-212 | As a system I should refer to the database for configuration values and attributes | Centralized the storage (and added necessary encryption) to certain application configuration values. | MSERV |
| 12 | US-211 | As a system I should be able to track contact information for a Person | Corrected an issue with how the Web site was associating login information to contact information | MSERV |
| 13 | T-229 | Standardize Configuration Settings | To increase the flexibility of the system all system configuration settings will be stored in the database rather than within the codebase. | MSERV |
| 14 | T-206 | Improve fileupload handling | 1) Fixed the issue where users would not receive an error message if they attempted to upload an unsupported file time 2) Added ability to limit file upload size | MSERV |
Version 1.1.0.892
Release Date:
- To Test: 11/28/2017
- To Production: 12/18/2017
| Item Number | Summary | Description | |
|---|---|---|---|
| 1 | US-156 | Restrict access to different areas of the website | To support the Board Portal, we have introduced a higher level of roles and permissions which allow the ASWB IT team to assign/revoke access to one or more of the following areas for each user in the system: Access to Social Worker Dashboard, Access to all Board Portal functionality, Access to SiteAdmin UI |
| 2 | US-158 | Allow a board member to review and response to "Board Hold" applications | Introduced the functionality for Board Members to access a website to see all applications currently awaiting their review so that ASWB can continue with their approval. |
| 3 | US-193 | Introduce a "threaded" conversation datatype | To support the Board portal process, we have developed a new data type called "Threaded discussion" which will keep a log of the previous updates to the field and encapsulate them with a timestamp and the user who entered them. The historical "thread" is read-only. |
| 4 | US-159 | Allow a board member to review all applications that have been submitted to ASWB for their Jurisdiction. | Introduced the functionality for Board Members to search via a dashboard OR via search criteria for any application submitted to ASWB. |
| 5 | US-190 | Provide common landing area for users with multiple roles to access web areas | In anticipation of users holding multiple roles with the relationship to ASWB (Board Member, Social Worker, Reference), we have expanded the current social worker "dashboard" area to also accommodate other users. |
| 6 | US-200 | Board members can get summaries of Application progress | Under the Board Portal - Reporting area, users can now see the progress of applications within pre-defined time spans. |