Web Application
Phoenix Plugin
Client Application
August 2022: Added INTG-3288, 3293, 3294, and 3295.
April 2022: Added INTG-891, 1307, 1449, 1499, 1502, 1506, 1513, 1526, 1530, 1541, 1550, 1551, 1557, 1572, 1577, 3111, 3117. Removed INTG-597, 636, 656, 679, 800, 863, 920, 935, 949, 951, 959, 971, 1380 (fixed in 22.4.1) and INTG-647, 782, 907 (obsolete with 22.4.1).
January 2022: Added INTG-1380, 1242, 1264, 1288.
Adding an updated copy of a copy to the same folder causes an issue with the Revision Number (INTG-3288): The copied file is updated but the Revision number for the copy does not increment by one. This keeps the file from being used properly as a dependency for savepoints.
Notify option does not work as expected for Copy function (INTG-3293): When copying a file with the Notify option deselected, a notification is still received. Copying a file a third time into a folder where a copy with the same name already exists causes duplication of the file instead of overwriting the existing copy (INTG-3294). Overwrite message does not always appear when copying a file into a folder where a copy with the same name already exists (INTG-3295). Administrators are able to delete a property that is in use, which removes that information from the folder or file to which it is applied (INTG-1499): To avoid removing a property that is in use:
An exception may occur during “Custom Filter” creation (INTG-1577): The workaround is to export the file as an Excel file, then filter using Excel or use the text filter option. Not able to unblind a file if permissions are set as Set/Unset Blind=True and View Blind=False (INTG-1557): The workaround is to have another user with the correct permissions unblind the file or grant the user both view and set/unset blind permissions. When a table file is locked, “Edit” actions are still available, but file content will not be updated (INTG-1526): From the Contents tab for a locked table file it is possible to edit values displayed. It is also possible to click Update and see the electronic signature request. However, after submitting the signature, the contents of the file stored in Integral will not be updated. Thus, even though it appears that locked files can be edited, the content of the locked file stored in Integral remains protected. An administrator cannot create file types with the same names in different repositories (INTG-1506). Administrators are able to delete a property that is in use, which removes that information from the folder or file to which it is applied (INTG-1499): To avoid removing a property that is in use: For a folder property: In the Admin module, identify the folder type to which the property applies. Click the Under Properties, find the property in question and either use a wild card symbol (*) or, if available, select a value. Press the Apply button to retrieve any folders that have used the property. For a file property: Click the Review the Refine Results list to see if the property is being used by any of the retrieved files. The user interface appears to allow editing of XPT files, but the changes are not applied (editing of XPT files is not currently supported) (INTG-1449). 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. 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). 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. When a property-based rule is applied to an access group, changing the property value in the study metadata does not automatically update the access permissions via the rules (INTG-977): The workaround for this issue is to create a new root folder, which will force a reset of the group permissions. 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. Deleting a folder also deletes all child files which are locked or blinded (INTG-891): Before deleting a folder, check that it does not contain locked or blinded child files to avoid inadvertently deleting such files. Contents tab does not display the icons for locked, blinded, or linked items (QC 265/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. Blinding, then locking the same file at file level will not allow the file to unlock later (QC 254/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. 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. Filename length is limited to 128 characters, including the file extension (INTG-470): Filenames that are longer than 128 characters are truncated to 128 characters, which could result in the file not being loaded. To avoid this issue, keep filenames less than 128 characters. 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. Dependency file can become editable when updated with revised version (INTG-3194): A dependency file should only be editable when it becomes detached from Integral. “Add Selected Item” dialog displays incorrect folder content for the selected repository (INTG-1572): The workaround is to switch to another repository and then reselect the desired repository to obtain the correct display of folders. Adding a selected item is not successful if the user switches to a different repository (INTG-1551): Switching to a different repository after selecting an item in the Add Selected Item dialog generates and error upon completing actions and signing. The workaround is to export the file from Phoenix to the local directory and use the Upload option in Integral’s browser. Legacy folders are not displayed in the “Add Selected Item” dialog, when user has the correct permissions (INTG-1550): The workaround is to export the file from Phoenix to a local directory and then use the Upload option in Integral’s browser. Project symbol in Object Browser does not change after detaching the project from Integral (INTG-1530): After using the Detach Integral Item option on the ellipsis menu, the icon does not change from If the Integral plugin for Phoenix 8.3.5 is uninstalled, ggquickeda will no longer work (INTG-1513): ggquickeda will generate an exception when executed after the Integral plugin for Phoenix 8.3.5 is uninstalled. To prevent this issue, do not uninstall the Integral plugin. 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, it has been reported that the system will occasionally fail with timeout errors for large projects (INTG-975): The workaround is to save on the local drive first and then reconnect with Integral to save again. 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. Saving binary files that are part of a Phoenix project from Phoenix to Integral through the Save Options tab in the Integral plugin does not work (INTG-862): The Binary Object selection in the Save Options tab of the Save to Integral dialog is not functioning and items selected to be exported as binary objects are not saved to Integral. There is no known workaround for this issue. In the “Default Save Options” panel, the Load From File button is not retaining and applying loaded options (INTG-676, 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. Drag and drop for file uploads does not work in the Integral plugin (INTG-600): The newer version of DotNetBrowser used with Integral 1.1.1 does not support drag and drop from a user's desktop to the Integral Browser as the previous version did. The workaround is to use the file browser to select the files to upload. Savepoint folder appears as red in Local Directory, even though it is up-to-date with Integral (INTG-3117): After syncing a savepoint with updated content and updated dependency, the savepoint folder remains red (out-of-date) in the Local Directory. To work around this issue, sync the updated dependency file first to Integral, then sync the savepoint to Integral, as described in the following workflow. Update the dependency for the savepoint locally. Update the savepoint locally, based on this data. Refresh the Local Directory. Sync updated dependency file to Integral. Sync updated savepoint to Integral. Incorrect message 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 selection 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.
icon in the Home page, select the identified Folder Type from the menu.
icon in the Home Page, clear any entry for the search and press the Enter key.
This displays results for all files to which the user has access.
to 
.
The savepoint folder and any updated files now appear in red in the Local Directory.