|
|
||
Release 7.4.6a
5/10/11
Event record deletion is now supported, along with a new role permission to "Delete Events". (Case #'s 00025099,00025059, 00025172, 00026846, 00027581, 00027656, 00030829, 00031263)
Three new import options are now available to provide additional control over how records are updated during certain import routines. They are summarized as follows:
1.Academic Section Import
A new system setting setting was added that prevents the import process from overwriting room assignments on existing, matching sections if the room assignments were modified in Astra Schedule. This will prevent scheduling work from being overwritten if the room assignments have not yet been exported back to the SIS.
This new system setting (DoNotOverwriteAstraRoomAssignments) is included in the import configuration files as follows:
<SystemParameter name="DoNotOverwriteAstraRoomAssignments" settingKey="DoNotOverwriteAstraRoomAssignments" default="true"/>
Note that the default setting is "true". If the setting is not otherwise configured in system settings, the spoke will behave as if were set to "true", meaning that modified room assignments will be preserved during imports. To edit this value, an entry must be added to the System Settings in the Setup area of the application.
2.Excel Event Import
A new job parameter was added to the event import that allows users to define how they would like the import routine to handle matching event records during update.
If there are records in the import file that match existing records in the Astra Schedule database, the system can either skip these records or delete them and re-insert them using the data in the import file. The latter option allows an update to occur for these matching records.
This new option is visible on the event import job screen as a job parameter. The choices are either "Skip Event" or "Delete Event & Recreate".
3.Room Import
A new job parameter was added to the room import that allows users to define how they would like room updates to be handled when the rooms in question have effective dates defined in Astra Schedule.
If a room record has effective dates defined and is being updated by import, the import routine can now either update the version of the room that is effective "today", or it can update the version of the room that is active the furthest into the future.
This new option is visible on the room import job screen as a job parameter. The choices are either "Import to Current Room Versions" or "Import to Latest Room Versions".
Several new reports were added to the system, including:
•Customer and contact list report. (Case # 00027402)
•"Overbooked Event Meetings by Date and Time" report to identify overbooked events. (Case # 00027705)
•"Weekly Room Grid" report. (Case # 00031350)
•"Events with Selected Resource and Meeting Notes" report that includes events with resource assignments and notes. (Case # 00031602)
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.
•Term: Error received when attempting to delete a term. (Case #'s 00032597, 00032789)
•Calendar: Default calendar view not including events even though selected. (Case # 00031672)
•Calendar: Filters associated with different calendars are not defaulting correctly. (Case #'s 00031585, 00032427, 00032778)
•Calendar: Selected filter not always being displayed correctly. (Case # 00031704)
•Calendars: Error when accessing certain filters. (Case #'s 00031696, 00032820)
•Calendar: Manage Filters option still available when removed from calendar definition. (Case # 00032117)
•Calendar: Error encountered on Daily Room Grid due to partitioned room conflict. (Case # 00032727)
•Room Usage Controls: 12:00 AM start and end times causing error. (Case # 00024039)
•Room Usage Controls: Usage control settings to block academic section scheduling in rooms was not being honored correctly in the ad hoc scheduling tool. (Case #'s 00032726, 00033020)
•Room Usage Controls: Blocking event requesting and scheduling is also blocking section scheduling. (Case # 00032845)
•Events: Error encountered when filtering event list to "My Events". (Case # 00031927)
•Events: "Owner" drop‑down field was not displaying all users in the user list. (Case #'s 00030750, 00030937, 00030945, 00032219, 00032303, 00032623)
•Event Request Form: Custom fields are not available for event request forms. (Case #'s 00032323, 00032776)
•Event Notifications: "Request for Additional Information" message is not being sent to the requestor. (Case # 00032469)
•SIS Interface: Getting error during real time import from PeopleSoft DB2. (Case # 00030169)
•Event Import Utility: Event Types are not being created during import. (Case # 00032086)
•Event Import Utility: New job parameter included to delete and replace matches, or only insert new records during import. (Case # 00032891)
•SIS Interface: Web services interface is timing out. Web services timeout setting is now configurable. (Case # 00032771)
•Task Agent: Task agent is not being restarted automatically when the server is rebooted. (Case # 00032252)
•Event Summary Notification: Event summary report causes confusion due to cancelled items included in content. Report updated. (Case #'s 00025290, 00024118, 00025503, 00027387, 00028418, 00028969, 00029056, 00029225, 00029267, 00030509, 00030895, 00031071, 00031142, 00031123, 00031420, 00032116, 00032115, 00032245, 00032249, 00032586, 00033033)
•Reports: Report views included term "Name" instead of term "Label". Term label is preferred for reporting purposes. (Case #'s 00032204, 00032669, 00032685, 00032768, 00032836)
•Section Form: Enrollment field is not populating on the form for academic section records. (Case # 00032929)
•Security: Combined role permissions not being applied correctly to allow for greater access. (Case #'s 00032614, 00033035)
•Security: "Limit to My Events" permission not properly limiting edit permission on other events. Issue may also be related to an LDAP group/user role assignment problem. (Case #'s 00030690, 00031282, 00032905)
•Role Form: Save As feature not correctly copying permissions. (Case # 00032452)
•Security: "View Equipment" permission required in order to request items on an event request form. (Case # 00032766)
•Student Import: Error occurs during import. (Case # 00032098)
•System Settings: Default session timeout setting increased to 60 minutes. (Case #'s 00031417, 00031959, 00032470)
•System Settings: Updated application to properly handle locale changes to time format. (Case # 00031553)
•Timetabling: Additional information provided to indicate why a section was infeasible during timetabling if due to time constraints. (Case # 00031481)
•Meeting Patterns: Contact hours were being truncated if entered as fractional hours. (Case # 00031463)
•Meeting Patterns: Added "Is Standard" filter to meeting pattern list page for ease in identifying patterns flagged as "standard". (Case # 00031462)
•User Interface: Made a style change to improve navigation button placement on some screens in IE8. (Case # 00030864)
•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)
•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
•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.
•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)
•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
•Browser Support: 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.
•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
•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
•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
•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)
•“Guest” user account must be mapped to the “guest” role (in user setup) for proper application functionality.
•Holiday Section Conflicts: Section meeting instances are cancelled 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.