Ares Known Issues
-
When cloning an item in the web, routing rules are not applied when the new item's final status is set
For example, changing an item's status from CurrentStatus to PendingActivation will not apply any rules which also prevents any custom routing rules from being applied to items cloned from this item.
Bug# 4559
0 votesReleased in 5.0.1
-
Cloning course items in the web does not provide a username entry for the new item's first history entry
In the web, clone a course and select at least one item. When viewing the item history for the newly cloned item, the first entry 'Status changed to Item Submitted via Cloned Course' will have an empty string for the username.
Bug# 4558
0 votesReleased in 5.0.1
-
0 votes
Released in 5.0.1
-
0 votes
Released in 5.0.1
-
The non-breaking space value is rendered on the webpage instead of the space
Workaround: See https://support.atlas-sys.com/hc/en-us/articles/360011824714 for instructions on fixing the non-breaking space in the include_defaultcourseinfo.html, UCourseInfo.html, and UCourseTags.html pages.
v4.7
Bug#35840 votesReleased in 5.0.1
-
The OrderBy #TABLE attribute does not work for many item-related tables.
Most of the table builder functions we have in the web DLL support an 'OrderBy' to specify the default sorting parameters. However, four item-related tables, Item, ItemNotes, ItemTracking, and ItemHistory, do not apply OrderBy attributes specified in table tags.
0 votes -
1 votereleased ·
AdminDustin Stokes (Chief Technology Officer @ Atlas Systems, Inc., Atlas Systems, Inc.) responded
Released in Ares 4.6.6