HOTFIX-72 Restarting the IQE signature workflow cancels the in-progress workflow | 5/9/2023 | The text on the link for starting/restarting/repeating a signature workflow in IQE has been updated to accurately reflect the status of the workflow.
When restarting a signature workflow in IQE, any outgoing signature requests on signature elements currently in the workflow will now automatically be canceled. |
HOTFIX-70 New "Backup uploaded to FTP" email notification | 3/9/2023 | Added a new email notification that will be sent to users responsible for downloading backups, when their backups are fully uploaded to the FTP server.
Going forward, the users responsible for downloading backups at organizations with FTP integration with MediaLab, will not be sent the "backup ready to download" email notifications anymore, when their backups are fully processed, if those backups are being uploaded to FTP. Instead, they will get the new "backup uploaded to FTP" email notification once the backup file was either uploaded to the customer's FTP server or copied to the customer's dedicated folder on our FTP server.
If the users want to download their backups from MediaLab, they will need to navigate to each product's "backups" page in MediaLab, and download them from there, since backups uploaded to FTP do not show up on their to-do list under "Backups Ready to Download" anymore. |
HOTFIX-68 Made the behavior of "Backups Ready to Download" to-do list consistent across all products | 3/8/2023 | For some of the products, the backups ready to download were being removed from your to-do list when other user(s) downloaded them, or if they were being uploaded to FTP (for accounts with FTP integration with MediaLab), while for other products (eg. Document Control, Compass), the backups stayed on your to-do list even if other user(s) responsible for downloading them had already downloaded the same backups, or if they had been uploaded to FTP.
Going forward, the backups ready to download for all products, will be automatically removed from your to-do list if other users download them, or if those backups are being uploaded to FTP.
|
HOTFIX-62 Unlocking Data Table Rows: New Requirement for Providing a Reason | 7/28/2022 | Once all required fields for an IQE data table row have been provided, the row is locked. If corrections or updates are needed, the row can be unlocked by clicking on the “lock” icon for the specific row. After this hotfix, the user unlocking the data table row must provide a reason for unlocking, which will be included in the history for the IQE event / data log. This provides additional context around corrections or updates that may be necessary to IQE data table entries.
As before, IQE captures all response history for all form elements. When corrections and updates are made to any IQE response, the original response (including timestamp and name of the respondent) are still preserved in the response history, as well as the new response + timestamp + name.
When building a form, you can control who is allowed to unlock a data table row and for how long. You can restrict corrections and updates to 24 hours of initial entry, 1 hour of initial entry, or prevent any corrections / updates. Please select the setting appropriate for your IQE form’s purpose and the kind of data being captured. |
HOTFIX-61 MediaLab Website Access Restored, June 8th 2022 | 6/8/2022 | At approximately 2pm Eastern Time, many MediaLab customers began to report problems with accessing the website. MediaLab determined that this outage was caused by a problem at our hosting provider and outside of our direct control. Other major websites were affected by the same error, including social media platforms and banking websites.
MediaLab reported to our hosting provider that we were among affected customers, and we received assurance that the issue was their top priority.
As of 3pm Eastern Time, the hosting provider corrected the errors, and MediaLab.com and other affected websites are again accessible.
We sincerely apologize for the downtime. If you have further questions, please contact support@medialab.com. |
HOTFIX-60 MediaLab Website Access Restored, June 8th 2022 | 6/8/2022 | At approximately 2pm Eastern Time, many MediaLab customers began to report problems with accessing the website. MediaLab determined that this outage was caused by a problem at our hosting provider and outside of our direct control. Other major websites were affected by the same error, including social media platforms and banking websites.
MediaLab reported to our hosting provider that we were among affected customers, and we received assurance that the issue was their top priority.
As of 3pm Eastern Time, the hosting provider corrected the errors, and MediaLab.com and other affected websites are again accessible.
We sincerely apologize for the downtime. If you have further questions, please contact sales@medialab.com. |
HOTFIX-59 Users with problems using the MediaLab website on Tuesday May 5 2022 | 5/10/2022 | We apologize if you are experiencing problems with the MediaLab website today. We are aware of technical issues within Microsoft Azure that have been impacting us and in turn, some (but not all) users. This is causing the 403 and "request blocked" errors that users may be seeing. We're working to resolve these with Microsoft ASAP. We'll send an update as soon as we can. In the meantime, you can try clearing your browser's cache, trying a different browser, or using incognito mode in your browser. |
