Just posting here as a quick reminder that we are always looking for feedback to continuously improve our software, our Developers are working hard to incorporate IVIVC and AutoPilot with the Phoenix for the next release (6.2). We are also addressing some issues that have come up from our users. These “known” issues which are discovered after Release are recorded in our Product Notifications and may be useful reading for those of you planning validation etc. ftp://support_ftp:pt9JTmD9GdXQLtCgPkvL@ftp.certara.com/support/desktop/Phoenix/PHX001_Product_Notification.pdf ftp://support_ftp:pt9JTmD9GdXQLtCgPkvL@ftp.certara.com/support/desktop/Phoenix/PHX002_Product_Notification.pdf ftp://support_ftp:pt9JTmD9GdXQLtCgPkvL@ftp.certara.com/support/desktop/Phoenix/PHX003_Product_Notification.pdf Have a good weekend all, Simon.
Since 6.2’s release we have regrettably found a few issues which are detailed in the ; Phoenix Product Notification 004 available on the Support site; ftp://ftp.certara.com/support/desktop/Phoenix/PHX004_Product_Notification.pdf the most critical of which is probably; Import: Importing Excel files when using the option “start importing data at row#” with sheets that contain empty rows at the top might not import the last row (QC 10909): When importing into Phoenix and using the option “Start Importing data at row #”, Excel sheets that have empty rows at the top may cause row(s) at the bottom of the sheet to not be imported. The workaround is to remove the empty rows at the top of the sheet in Excel prior to importing into Phoenix. The user should verify that all desired rows have been imported until this issue is corrected. This problem occurs in all Phoenix versions and will be corrected in Phoenix 1.2.1 point release (the next Val Suite release will be compatible with both 6.2 and 6.2.1) Simon. PS - we’ve made some fixes to the forum so that the Search function will now work properly, please email me if you encounter some future problem with the forum.