Known_Issues

May 2023: Added INTG-4237. Removed INTG-600, 975, 3177, and 3619 (fixed in 23.4.1).

January 2023: Added INTG-3874.

When performing Copy/Link, dragging a file across other folders in the right panel before dropping the item onto the target folder can cause an exception (INTG-4282): To work around this issue, drag the file directly to the target folder, without moving the cursor over other folders in the right panel.

Error while saving a savepoint when save options have identical names (INTG-3520): When selecting results with a similar Path in the Save Options window, unique results names should be provided or an error message will be generated.

Jpeg content fails to load when switching between files (INTG-3368): When viewing the Content tab containing a preview of a jpeg file, switching to another file may not update the Content tab. In such cases, the workaround is to select the file a second time to update the content.

System Audit Report Filter/Custom Filter incorrect for “Details” column (INTG-3465): When filtering on the Details column of the System Audit Report, entering values for Search and Text Filters > Custom Filter will show a “No matches found” message, even when there matches exist. Ignore this message and continue by pressing OK. The filter will be applied and the matches returned successfully.

Custom filtering of System Audit Report can display incorrect “No matches found” message (INTG-3427): When using the Custom Filter dialog to filter on any Details column in Pivoted View of the System Audit Report, entering values and then specifying Starts With will show a “No matches found” message, even when there are matches that exist. Ignore this message and continue by pressing OK. The filter will be applied and the matches returned successfully.

When editing a custom folder type, all four Security Context types are incorrectly available (INTG-1307): When the custom folder type is marked as a Root folder, only the Root Folder Security Context is applicable, even though all four contexts are listed in the interface. Similarly, if the custom folder type is not a Root folder, the Root Folder Security Context is included in the list when it should not be available for selection. This issue is only encountered when editing a custom folder type, not during creation of the folder type.

Unable to delete copied files (INTG-1264): If a file that is copied from one folder to another does not have the delete permission, it cannot be deleted and will generate an error in the console. If the permissions are changed for the file to include delete permission, the file can then be deleted.

If new revisions for the same file are uploaded by different users, the “Conflict” dialog does not function correctly (INTG-921): In the rare situation where two users upload new revisions for a file at the same time, a dialog is displayed to one of the users explaining that there is a conflict. If the Cancel button is pressed in the Conflict dialog and then Upload is selected again in the Upload dialog, the Conflict dialog should redisplay, but it does not. At this point, the Upload dialog is still displayed, the revision has not been uploaded, and it is unclear how to proceed. The workaround is to press the Cancel button in the Upload dialog and try again.

History tab's “Revert to Revision” option does not work after renaming the file using the Properties tab (INTG-919): In the situation where there are at least two revisions of a file and the filename is then changed through the Properties tab, if you use the Revert to Revision option to go back to a previous revision, the History tab does not list a new revision and the content of the file remains as it was in the last revision. The workaround for this issue is to download the revision you want to return to and then re-upload that revision with a new name.

Blinding, then locking the same file at file level will not allow the file to unlock later (INTG-871): If a file is blinded and locked, it cannot be unlocked at the file level. If you use the lock icon, you can go through the steps to unlock, but the file will not be unlocked. This issue is seen when operating at the file level. The workaround is to unlock the file from the folder level. Unfortunately, this action will unlock all files in that folder and you will need to lock the other files again.

There is no warning message when uploading a file with the same name as an existing file (INTG-432): When uploading a file with the same name as an existing file, the uploaded file is accepted as a new revision of the existing file with no confirmation message being presented to the user. To avoid this issue, verify that the name of the file to be uploaded is unique to any existing files.

Contents tab does not display the icons for locked, blinded, or linked items (INTG-888): Although the icons are properly displayed in the tree on the left, the do not appear in the Contents tab. There is no known workaround for this issue.

Contents tab incorrectly displays the Delete icon and Delete All icon for items in a folder with only Read access (INTG-832): There is no known workaround for this issue.

Sorting data in the Content tab is a lexical sort (e.g., 1, 10, 2, 22, 3, etc.), regardless if the data are numerical or character or a mix of both in a column (INTG-1288).

Phoenix Plugin

Validation Suite installation check for Phoenix 8.2.2, 8.3.4, and 8.3.5 fails after Integral Plugin 23.4.1 is installed (INTG-4276): An update to Phoenix by the “Integral 23.4.1 for Phoenix 8.x” installer causes one Validation Suite test (“PHX Installation”) to fail in the WinNonlin and NLME test sets. The update by the installer enables Phoenix to open Word files uploaded from Integral. The failure is observed if the Validation Suite is run after installing Integral Plugin 23.4.1 and occurs because the updated file has a different checksum than the Validation Suite expects. There is no issue if the user upgrades to Phoenix 8.4.

Lock and Blind Options when saving a savepoint (Save or Save As) disappear if you make a change in the Save window (INTG-4260): If you need to make changes to the Save window of a savepoint (e.g., modify the name or edit the save options), select the right arrow first, then the left arrow. After changes are made, select the right arrow again and the Lock and Blind options will appear.

When Integral Browser is opened from Phoenix, using the “Reload” option removes Plugin-related options from the right-click menu (INTG-4237): To avoid this issue, do not use the Reload option on the right-click menu. If the problem should occur, close and reopen the Integral Browser or use Refresh button.

Use of the F1 key from an Integral Plugin dialog or the Integral page of the Preferences dialog generates an unexpected error (PHX-4075): This issue does not affect any Phoenix operations and the warning message can be ignored. To access the Integral Plugin documentation, use this link:

https://onlinehelp.certara.com/integral/index.html#t=Integral_Guide%2Fintegral_plugin%2Fintegral_plugin.htm

It can also be accessed through the Help > Contents menu item in Phoenix:

In the Phoenix Assistance page, select Integral Plugin under “Import/Export.”

Click the Certara Integral Assistance website link.

Use the links in the “Integral Plugin” section.

“Analyses” and root folders are red after savepoint update (INTG-3892): If the savepoint has dependencies that are out-of-date, the folders remain red after saving. To bring the savepoint up-to-date, load the savepoint into Phoenix, refresh the dependency, rerun the analysis, and save back to Integral.

Formatting issues occur when importing a csv file from Integral to Phoenix (INTG-3874): The preview of the file in the Phoenix Load Data dialog shows HTML instead of the rows and columns of data. To work around this issue, import the file from the local machine into Phoenix without using Integral.

Reverting an individual file within a savepoint should be avoided (INTG-3563): Users should not attempt to revert an individual file within a savepoint. Instead, either revert the entire savepoint or download the needed file version, if further work is to be done using a particular version of the file.

“Refresh from source” at the project level for older revisions of a savepoint will not load the latest revision of the savepoint (INTG-3478).

Savepoint folder is not colored red when reverted to a version with a Dependency that is out-of-date (INTG-1242).

When saving projects from Phoenix to Integral, the plugin does not check the validity of dependencies before adding them and this can result in a 500 error if an invalid dependency is encountered (INTG-974): If the 500 error is encountered, the workaround is to return to Phoenix, right-click the project and select Detach from Integral, then save the project. The problematic dependency is no longer present and the project saves successfully.

Integral Browser does not work properly on Windows 8.1 Kanji System Environment (INTG-879): Issues such as the Object Browser splitting when scrolling, only a subset of the content being displayed on the Content menu, and unable to select items in the Content menu have been observed when using Windows 8.1 Kanji System Environment. There is no known workaround for these issues.

In the “Default Save Options” panel, the Load From File button is not retaining and applying loaded options (INTG-1392/CS00206457): If the default save options are loaded from a file, but not applied when saving a project to Integral, the loaded save options are not retained. Moving to a different preferences panel and going back to the Default Save Options panel shows that the save options are not there. This issue is not seen in Phoenix 8.3. The current workaround is to make any manual edit to the loaded save options using Edit, Add, or Remove, and click OK. When Phoenix is reopened and a project is saved to Integral, the save options will be properly retained and applied.

Client Application

Incorrect message displayed when overwriting during a sync to Local (INTG-3111): When syncing to Local involves overwriting an existing file, selecting OK to confirm the overwrite can result in an erroneous “Sync not required” message. Ignore the message and continue selecting OK to overwrite the root folder.

When synchronizing a new local folder, the entered description does not carry over to Integral (INTG-898): The new folder is successfully synchronized to Integral, with the folder type matching what was set in the Client application. Any text entered as a description in the Client application is not saved to Integral. There is no known workaround for this issue.