1 Application Enhancements
The following new features were added to the latest eCASE Audit release.
1.1 Project Status Report Changes
Weāve made minor enhancements to the Project Status Report including:
Removed the āGroup Byā option
Moved SIC data to the first column
Removed āReviewed Dateā and āReviewerā fields
Pulling only prepared items into the report
Moved this report from the Application level to the Folder level
1.2 Display Risk Rank on Risk Mapping Search
Risk Mapping searches now include the Risk Rank (Low, Medium, High, etc).
1.3 Relate Budgeted Hours Between Tabs
Budgeted hours entered on the Annual Plan Summary tab are now automatically added to the Project Cost tab on linked folders. Youāll no longer need to enter the hours on each tab separately.
1.4 Assignment Number Column Folder Link
The āAssignment Numberā Column on the Annual Plan Summary tab now directly links to the folderās Project tab.
2 Terminology
Weāve made updates to terminology configuration in this release:
2.1 Edit Terminology on Risk Profile Header
Weāve added terminology options for the Risk profile column header. You can now edit this header and the new terminology will be reflected in all locations: the Fiscal Year Plan risk profile, the Project tab, and the Terminology tab.
2.2 Edit Terminology on Project Fiscal Year and Existing Fiscal Year Work Topics
Weāve added the option to configure the terminology for the Project Fiscal Year and Existing Fiscal Year Work Topics fields that appear on the New Project form.
2.3 Alert Terminology Reflects Terminology Configurations
When you attempt to create a new Fiscal Year Plan for a year with an existing plan, an alert pops up. This alert text now matches terminology configurations. For example, if your FYP terminology is āCalendar Year Planā the alert will read āThe Calendar Year Plan already exists. To open this Calendar Year Plan, click hereā.
2.4 Risk Factor Template Terminology
To maintain consistency throughout the application, all columns on the Risk Factor Template Profile now match the terminology set for the FYP/Project Risk Profile in Configuration.
3 Field Changes
Here are some updates to eCASE Audit form fields for this latest release:
3.1 New āOrganizationā Field for Employee/Agency Employee
Weāve introduced a new āOrganizationā data element for Agency Employee and Employee Contact types. You can create a new Organization with multiple contacts, allowing you to maintain contact details for additional contacts within the organization. When viewing the contact in the contact type view, the application lists the first name, last name, and title of each additional organization contact.
3.2 Decimal Values in Finding/Recommendation Cost
You can now enter decimal values for the Finding/Recommendation cost CFDA Amount.
3.3 Recommendation Costs Character Limit Increased
The character limit has been increased for the Recommendation Costs field on the Findings tab. The maximum cost input is now $9,999,999,999,999,999.99.
3.4 Action History Enabled for All Fields in the Audit Configuration Folder
All Audit Configuration Folder fields have been added to the Action History Logs. This way, administrators can see if a user has made a change to any fields.
3.5 Configure Project Cost Tab Fields
In the Configuration folder, you can now enable/disable or mark required the fields on the Project Cost tab.
4 Bug Fixes
The following bug fixes were applied in the latest version of eCASE Audit:
ID | Description |
|---|---|
55386 | Fixed a bug occurring when users would submit forms with required fields. Even when valid data was entered in the required fields, an error message would appear, prompting users to enter valid data. |
57708 | Corrected a bug in which clicking Save from the top toolbar on the Milestone resulted in an error. |
57735 | Milestone dependencies configured in the Project Template were not carrying over once the milestones were imported to the Milestone Dates tab in the Project. This issue has been resolved. |
57744 | Fixed a bug in which users were unable to import milestones by selecting an existing Project Template in the Search Criteria. |
57789 | After creating a new Project within a work topic for a Fiscal Year Plan, users were unable to access the Fiscal Year Plan from the Launch Pad. This has been corrected. |
58007 | Addressed an error resulting when attempting to access Profile, Risk, or Objective sections within a Fiscal Year Plan. |
58262 | Resolved an issue in the Time By Dates Report that prevented records from displaying when running a search by Folder or Project. |
58768 | Resolved a bug where āLead Auditorā and āAudit Managerā fields marked as disabled in Configuration would still display until a value was selected. |
59063 | Tooltips on the FYP Launch Page/Project Creation Page were not reflecting terminology updates made on the Terminology Configuration page. This issue has been fixed. |
59092 | Resolved a bug in which users were unable to access Projects in the Fiscal Year Plan. |
59194 | Corrected an issue where document updates would fail when Procedure attachments reached the maximum size. |
59463 | Fixed a bug where the Action History for a Procedure would not reflect all tasks performed for that Procedure. |
59486 | Addressed an error occurring when a user attempted to create a new Procedure. |
59596 | Fixed an issue where data would not populate in the Project Cost tab after being saved in TimeXpress. |
59704 | Agency Employee contacts were displaying as duplicate entries in the Contacts list. This has been resolved. |
59835 | Corrected a bug preventing the Custom Audit Template field from loading values in Folder Search/Reports. |
59991 | Corrected a bug in which Work Paper changes would cause unwanted auto-renumbering. |
61851 | Corrected a bug causing the Project Management Report āPrepared byā and āReviewerā columns to be duplicated. |
61996 | Addressed an issue in which the Recommendation Tracking Action Log would not reflect changes made on the Terminology Configuration page. |
62314 | Corrected a bug in which Procedure Steps that were deleted then re-added would auto-renumber. |
63461 | The time zone assigned in the User Profile was not reflecting in the Action Log within Project folders. This has been corrected. |