ShareAspace 1.8 - Known issues
1.8.2
Instance order for import files
Currently the SoftType importer is sensitive to instance order in the import payload. If import data contains any already existing instances, appearing before new instances, imported instances with circular references between them will result in corrupted references. When creating import data, a workaround is arrange the import dependencies so that instances without references are handled first. A tool for applying the workaround to an import file is available.
Deep structures on imports
Large imports with very deep structures cannot be imported. This is a rare case but there are no exact numbers on the limit due to the limit being tied to depth and number of items on each level. In a future release a proper error message will be given when the limit is hit. Splitting up the input data into multiple imports solves the issue.
Approval request
The number of reviewers on an Approval request is limited to 10. There should now be an upper limit on the number of reviewers.
1.8.1
ShareAspace web performance
Running ShareAspace web with multiple module tabs open at the same time can impact the performance of the web application as a whole. While the issue is being worked on a recommended workaround is to close tabs that are not in use. Using the the "close all / close all but" functionality can be of help.
Approval Request reviewer Rejection/Reassignment
When an approval request reviewer rejects a review request, the rejection and any text that the user provides about the rejection is stored in the approval request history log.
If the same user is subsequently reassigned to that approval request as reviewer, first they have to be removed from the list of reviewers i.e. ShareAspace records them as a reviewer that rejected the review and then reassigned. The fact that the user previously rejected the request for review is removed from the approval request history log.
Instance order for import files
Currently the SoftType importer is sensitive to instance order in the import payload. If import data contains any already existing instances, appearing before new instances, imported instances with circular references between them will result in corrupted references. When creating import data, a workaround is arrange the import dependencies so that instances without references are handled first. A tool for applying the workaround to an import file is available.