|
|
||
Release 7.4.6b
5/17/11
A new "Same Time Link" option is now available on the section form. This new option works in the same way as Cross-Listing but links only the time/day pattern and not the room assignment to ensure that the sections' times remain the same. This link option is primarily for schools using the Timetabling feature that offer cross-campus sections at the same time via ITV technology. Sections linked via the Same Time Link feature will remain at the same time during manual scheduling and during timetabling.
Various bug fixes are included in this release. The following is a list of key fixes by application area.
Please contact customer support for the status of any specific Astra Schedule case number.
•Calendar: Error encountered on Daily Room Grid due to partitioned room conflict. (Case # 00032727)
•Events: Cancelling a single event meeting causes all meetings for the event to become "Incomplete". (Case # 00032775)
•Room Usage: Exam room assignments not properly blocking room availability. (Case # 00032943)
•Security: "No Event Requesting" room control prevents scheduling. (Case # 00032817)
•Room Optimizer: Exam setting for 2x capacity not being honored. (Case # 00031680)
•Exams: Exam actual enrollment reverting after initial scheduling with 2x enrollment option. (Case # 00032864)
•Exams: Error when attempting to manually schedule an exam meeting inside of the room optimizer sandbox. (Case # 00032866)
•Holidays: Holidays not properly cancelling section meeting instances. (Case # 00032328)
•Security: User with permission to view sections gets error when viewing section details from the calendar. (Case #'s 00032870, 00032913)
•Portal: Event list web part is not displaying all events when filtered to "My Events". (Case # 00032795)
•Security: Guest user with View Events and Request Events is allowed access to Notification List option. (Case # 00032869)
•Reports: Event resources not showing on reports after upgrade from 7.3 to 7.4. (Case # 00032852)
•System Configuration: Machine ID not properly maintained after backup and restore, causing report files to generate errors. (Case # 00032977)
•Editing the properties of custom fields requires user to choose a new name for the custom field when saving any changes
•Start and End Time fields may not display correctly when user chooses “Export to Excel” or “View Raw Table” option on certain pages with these fields
•Search filters on the Section List page are not intelligent (ie, when choosing a specific building filter and then subsequently adding a room filter, the room filter will display all rooms on the campus(es), not just those in that building)
•Accounting: The accounting application currently has a field length limitation that can prevent Astra Schedule from being able to uniquely identify rooms if there are buildings and room named the same across multiple campuses, or if there are otherwise unusually long building and room names. In this case an error will be encountered when exporting the room information from Astra Schedule to the accounting application.
•Cannot show alternate meeting patterns when assigning rooms in optimizer or production sections
•Rooms returned as “available” by the Ad-hoc scheduler may not be correct when filtering for multiple features as part of user’s search criteria
•Users with Calendars set to the “Month” view will only see one event per day when multiple events are scheduled within the same day
•Exam meetings colors may be inconsistent when changing the calendar view
•Calendar hover info panes for double-booked events will only display information for one of the two events
•Some user roles may be able to see the meeting details of events marked “Private” by the event creator
•Calendar functions are not currently compatible with the Safari browser, and some display resolutions in IE 7 & 8 may render the time control and text boxes incorrectly
•IE 7 users may experience issues with opening the Simple Event form when attempting to launch it from within a filtered calendar view
•When filtering down to a single room view on an effective-dated room, scheduled events may not be visible
•Setting an event recurrence of “every 30th day” when setting up an event in the Event Wizard will skip February
•Rooms with a default room usage policy that forbids event scheduling will still show up as available for “guest” users trying to request them for an event (ie, users w/o a login & password)
•The notification schedule is not accessible by a user that does not have Event scheduling permissions
•Attempting to delete an Event Meeting Type that is currently in use will result in application error
•Some user roles may not be able to schedule events on Holidays that have been configured to allow event scheduling
•Rooms designated as “tentative” or “requested” (as part of an event creation workflow) may still appear as “available” to other users with the event request permission
•Resource quantity overbook checking logic has been ported from 7.3 codebase. Rewrite for 7.5 currently underway; however, this functionality in 7.4.5 does not differ from its 7.3 implementation and users may experience issues when scheduling events with associated resources of quantity > 1
•System will not prompt two or more users with the “event approval” permission who are accessing the same event concurrently
•E-mail notification capability regarding changes to assigned rooms and resources is not currently functional
•Events which have not been edited in v7.4.6 (and thus updated with workflow status) may not be retrieved when attempting to filter by event status ONLY in the Event List page
•Users may experience application issues when attempting to cancel events which contain more than one event meeting and have been assigned resource(s) in “Tentative” status
•After importing events via the Excel import utility, customer data must be re‑exported to ObjAcct before users can effectively access Events and Customer related functionality.
•Importing Room resources using Excel for any records in which the RoomSISKey contains a trailing space will result in a loss of the room’s saved features
•Job status for On Demand section import jobs will not display on the Section Form when job does not complete (ie, ends in “Error” status)
•User can delete a Customer that has been associated to a scheduled event
•Selecting “Merge” when adding a new person record will result in an application error
•People records cannot currently be searched via email address
•Users viewing the Rule Walker in Internet Explorer 8 on 1024 X 768 resolution may not be able to view all the rules (IE 8 only)
•Reporting: Reports that include sub‑reports cannot be used in report subscriptions due to issues with how the sub‑report parameter is handled. This currently includes the following reports:
•Events by Date and Time with Notes
•Events Detail by Date Range
•Events Detail by Reservation Number
•Events for Selected Resource with Meeting Notes
•Rooms by Building
•Rooms by Region
•Rooms by Room Type
•Rooms for Selected Building
•Rooms with Selected Feature by Building
•Percent of Rooms in Use by Day and Time for Selected Room Type
•Percent of Rooms in Use Selected Room Type by Size
•MSSQL users experimenting with creating advanced reports will need to grant full access to their Astra Reports user (does not impact Oracle clients)
•Clicking “view impact” of Holidays (on select Activities) results in an application error
•Sandbox will not intelligently update the meeting patterns of sections which are part of a completed Room Optimization Sandbox and then subsequently have their meeting patterns changed via Realtime import from the SIS when user publishes results to production
•Due to the implementation of the new Sandbox for optimizer processes, pre-existing optimizer runs will not convert to version 7.4.5
•Some longer meeting type names may be cut off in the Sandbox criteria settings filter
•Assigning rooms to specific section meeting dates (section meeting instances) has no effect when editing a section from a sandbox. Only the room assigned to the first instance will be used as the Section Meeting room
•Users may experience performance issues when executing Room Optimization runs on terms with large number ( > 5000) of sections. (Note: adding additional preference rules has been found to improve performance after encountering this issue)
•Timetabling is not currently functional for clients with Oracle backend
•Statistics in Timetabling are not updated after changes have been made to any Sections or Students
•Updating a room or time assignment for sections in a Timetabling Sandbox results table may require user to manually refresh the page when switching tabs in order to display the update(s)
•“Show Patterns with Student Conflicts” checkbox not currently working as designed within the Ad-Hoc Scheduling tool
•Linked sections may not be able to be scheduled in a Timetabling run
•In the Sections tab of the Sandbox results, the “Time Status” field is not reflecting dynamic updates when user makes changes to the corresponding section
•Timetabling users may notice an issue in which students appearing on the “Students in Conflict” tab are still visible following the resolution of the conflict
•Section status may not change to “Unscheduled” in the Section modal window of a completed Timetabling Sandbox run after dropping its room assignment
•Associating a required Time Preference to sections can cause them to appear as “infeasible” in the Sandbox results viewer
•Students are not currently being removed from the “Students in Conflict” tab after all conflicts have been resolved
•The “Possible Times” column is not being populated correctly in Timetabling Results
•“Guest” user account must be mapped to the “guest” role (in user setup) for proper application functionality
•Holiday Section Conflicts: Section meeting instances are canceled and flagged as exceptions upon section creation. However, at this time, holiday configuration actions that should impact existing section records will not perform this work. Holidays that block section meetings must be created before sections are created.
•Any event that was saved in 7.3 will, when edited in 7.4, move back to the beginning of the workflow process
•Event & resource requests in pending status (ie, waiting for approval) will be lost in conversion
•Configuring the 7.4 workflow engine for Events requires a SQL script (NOTE: UPGRADES ONLY; New installs will not require this step)
•Portal configuration data does not upgrade from 7.3.x to 7.4
•PeopleSoft clients who utilize the audit table as part of ATE configuration may need to regenerate this table post-upgrade
•The application user help is not currently context-sensitive
•People records cannot currently be searched via email address.