The default pages do not currently support special date formats such as ISO8601 for the ActivityStatusDate. When adding the ISO8601 to the code, the pages are preventing the UTC time from being converted to the user's local timezone.
Bug# 86110 votes
When submitting a new request through the web and manually typing in the date, the date will be accepted regardless of if it is a blackout date. The blackout date will be unavailable if you attempt to select it from the calendar.
Workaround: Disable the manual entry to the date field by adding the below code to the scheduled_date.js:
// Disable manual entry for date
Bug# 83640 votes
A second class attribute was added for action items in the data row template. The contextual classes (e.g, menuClone) should be included in the earlier class definitions.
<a class="dropdown-item btn btn-light <#DATAROW field="RequestActionAllowed" name="Clone" disabledValue="d-none">" href="aeon.dll?Action=11&Form=32&Value=<#DATAROW field="TransactionNumber">" class="menuClone"><span aria-hidden="true" class="fas fa-copy text-primary"></span> Clone Request</a>
Bug# 78690 votes
Not all Date/Time fields are coded with the ISO8601 date.
Bug# 77100 votes
Security scans may ping the following old commented out jQuery in the web pages that needs to be removed:
<!-- jQuery first, then Popper.js, then Bootstrap JS -->
<!--<script src="https://code.jquery.com/jquery-3.4.1.slim.min.js" integrity="sha384-J6qa4849blE2+poT4WnyKhv5vZF5SrPo0iEjwBvKU7imGFAV0wwj1yYfoRSJoZ+n"
Bug# 75730 votes
The DLL is using the same code for both the MainMenu.html and ViewRequestHistory.html tables and just uses an attribute to determine which table is show.
Bug# 12310 votes
Requesting a copy from the Item Checked Out or Available for Use status produces the correct status line, but doesn't redirect user to the edit photo duplication form, and also gives a status line about editing a request that has already been processed.
Bug# 73930 votes
Bug# 73370 votes
Bug# 73360 votes
When adding carriage returns, it breaks the JSON parse.
Workaround: Use a <br> tag before starting a new line to ensure the alert will display properly.
Bug# 72460 votes
For pages with the required attribute and a cancel button, the nonvalidate attribute needs to be added to the cancel button in order to allow users to stop the request form and return to the main menu. The attribute also needs to be added to the Save Request button in the includerequestbuttons.html.
Bug# 69090 votes
Typo of the spelling "Request" in the templates folder:
Bug# 69010 votes
Underneath the "2019 Atlas Systems, Inc. All Rights Reserved" div, enter the following code to add the site map form on the logon page:
<a href="aeon.dll?Action=10&Form=3>">Site Map</a>
Bug# 66810 votes
The includeheaderrequest.html page is a web file that pre-dates Aeon 5.0. It is no longer used in any default Aeon 5.0 pages. The file should be removed.
Bug# 60260 votes
The check for UserControlsTransaction is loading the transaction query each time to determine ownership.
Bug# 44930 votes
Aeon is deleting the Session ID on pages that are able to be accessed when not authenticated.
Bug# 44150 votes
Some web users have been able to re-submit requests after they are placed in statuses that should not allow re-submission.0 votes
When an individual user has a request limit of “0” set in the client (so that the user can have unlimited requests), that “0” then shows up in web status lines as the user’s request limit if the <#requestlimit> tag is used in any status lines."
Status line message: "Thank you for your request(s). If you have more than 0 active requests, your requests will be placed in review and you will need to submit individual requests from the Saved Requests page."
Should clarify message if request limits are used overall, but individual user has unlimited limit.0 votes