Current Release

The following issues have been resolved in the v2.9.0.4 General Release.

The full details of each internal development release is included here for reference, but all the following are included in the v2.9.0.5 release.

Please Note—While v2.9.0.4 is the Current release, a new version v2.9.0.5 is currently being prepared. All v2.9.0.5 fixes are listed here so the user can be informed regarding what has already been reported and addressed—as well as to inform the v2.9.0.5 testers of what has been completed. Once v2.9.0.5 has been fully tested and is ready, it will be released and will replace v2.9.0.4.

Also, all issues that have been resolved in v2.9.0.5 are likewise resolved in the most recent release of v2.10.

[The following issues have been resolved in the v2.9.0.5 release:

BBL-539 -- Jobs: When selecting a project from the Projects display list, one project was disappearing from the Source tab. This has now been corrected.
BBL-504 -- Jobs: When executing a an Export for a project located on an EU Hub, a message appeared stating, "Central File is missing…Could not open document. This has been resolved.]

The following issues have been resolved in the v2.9.0.4 release:

BBL-504 -- Jobs: Export was not functioning properly for projects located on an EU Hub.
BBL-529 -- Jobs: Jobs were unable to Export to PDF, DWG or NWC when logged onto an EU Hub, displaying a message that stated, “Issue with project path: The central model is missing… cannot open document.” This has been resolved.

The following issues have been resolved in the v2.9.0.3 release:

Jobs: Fixed issue on Export Jobs, where non-Revit® files were being selected and processed for Export. This was causing Revit® to remain open and the Export Job to not process. BIMrx® Cloud Manager now prevents non-Revit® files from being processed for export.

The following issues have been resolved in the v2.9.0.2 release:

BBL-481 -- Browse: Single files were not downloading from the project Browser. This issue has been resolved.
BBL-483 -- Jobs: The Autodesk Connection Connection Type would sometimes become disabled in Add mode as a result of pressing several different key combinations.
BBL-490 -- Jobs: There was a failure to Export NWC jobs. Updated scheduled job processor to deal with old job files that do not have the NWC Export Options specified.
BBL-493 -- Members: Active/Inactive buttons have been enlarged and moved to the Hub Members tab. Project Admin Status has been reformatted to improve readability.
BBL-494 -- Members: When loading a very large number of Members for a Hub (more than 5,000-10,000) the application was sometimes experiencing problems. This has been resolved for both the menu-driven access of the Members module, and when while in Members a new Hub is selected from the Hub list at the top of the screen.
BBL-495 -- Files: Folders and files were sometimes not being created in BIM360®. This issue has been addressed.

The following issues have been resolved in the v2.8.2.4 release:

BBL-473 -- Browse: When implementing the Dynamic display of BIM360® project folders, files, and versions, the ability to download folders only was inadvertently removed. This has now been restored.
BBL-474 -- Browse: When publishing a Revit® Cloud Workshared model from the project tree using Publish Latest, and the publish was failing due to a lack of sufficient permissions to perform the operation, there was no communication to the user regarding what happened. Now, when this occurs, the application properly detects the situation, and the user is presented with a message describing what occurred.
BBL-477 -- Projects: The import of a project admin user after creating the project failed, causing the project to appear as though it wasn’t created. This has been resolved.
BBL-478 -- Jobs: The Job Type selection is now only available in Add mode. This helps the user to ensure consistency and integrity when copying jobs. Also, when copying a job to create a new one, the system was not enabling the Edit button after selecting the newly created job, which has now been addressed.

The following issues have been resolved in the v2.8.2.3 release:

BBL-468 -- Browse: When Multi-Select was set to On, and no projects were selected, after pressing Ok to the Download dialog box the application crashed. The system now correctly detects this situation and notifies the user they must select a project and try again.
BBL-470 -- Jobs: Folder and file selection for Dynamic Publishing jobs was not fully respecting the filter settings and has been addressed. Also improved the logging statements to provide clearer and more accurate information.

The following issues have been resolved in the v2.8.2.2 release:

BBL-465 -- Jobs: When a job was defined as Static Download, and Upload/Download entire existing projects was unchecked, the application was erroneously downloading all files for all projects that matched the current project and file filter settings—and all projects and files if the filters were left blank. It now correctly downloads only those project/files that were selected and displayed in the Selected Files tab.
BBL-466-- Browse: When using a Custom Connection, publish of Revit® Cloud Shared models was failing. These models now publish as expected if the user has permission to access the models. If they don’t have permission, then the system displays a message stating they need to have permission granted and to try again.

The following issues have been resolved in the v2.8.2.1 release:

BBL-457 -- Jobs: Tree view was double-populating due to BBL-358 on-demand tree view population, introduced in v2.8.1. This also affected the following two items, BBL-458, BBL-459, shown below. [On-demand tree view population has been removed from the Jobs module but remains in Files and Browse.]
BBL-458-- Jobs: Static Downloads: Verification that a job contains selected files was stopping projects with folders selected from saving and deploying.
BBL-459-- Jobs: Static Downloads: When editing a static job (download or upload), the previous settings were not being restored and were getting lost once the job was saved.

The following issues have been resolved in the v2.8.2 release:

BBL-408 – Jobs: Export NWC: Was not exporting Autodesk® Connector models having linked views.
BBL-421 – Jobs: Export PDF: Coordination Review was preventing opening of a model due to display of a coordination review popup message. BIMrx® Cloud Manager now suppresses Coordination Review popups and Manage Links pop ups--logging both messages clearly and the action selected. For Coordination Review it logs the coordination issue and action taken. For Manage Links it clearly states the models not loaded, unresolved paths and the action taken.
BBL-423 – BlueBeam settings were not being correctly set to the user’s saved folder path. This has been addressed.
BBL-426 – Download of files over 2Gb in size was causing errors and not downloading from both Browser and Jobs.
BBL-429 – [As of Version 2.8.1.0] The new feature used to assign Member Access rights has been slightly altered, renaming the “Ignore” option to “Keep Current”. This is strictly a cosmetic change, and all functionality remains the same.
BBL-430 – When updating a Project Member, the application popped up a mouse-over tool tip window over the Members tab, which blocked access to the dialog box selection necessary to complete the update.
BBL-432 – When pressing the Log File button from a module, it was bringing up the log contents from the most recent operation that was run—regardless of the module for which the update was run. For example, if a Files Upload was run then the user went to Members and pressed Log File—before running a Members operation—it showed the Files Upload log.
BIMrx® Cloud Manager now keeps track of the most recent log file on a per-module basis, and when the pop-up Log File viewer is invoked, it displays the correct log file name and contents for the current module only. Also, the Log File button no longer appears on the Jobs module.
BBL-433, 443 – Browse: When the Project List was refreshed, either from the refresh button or by changing the current Hub or Connection, the current Project Tree View as not being cleared. This has been addressed and now clears on Hub/Connection change or Project List refresh.
BBL-436 – [As of Version 2.8.1.0] Access to the Role Id panel was disabled when on the Hub Members tab. This access has now been re-enabled.
BBL-437 – [As of Version 2.8.1.0] An error occurred when a user logged on with a Custom Connection was retrieving project user info for a Project Admin and the logged-on user wasn’t a member of the project. It now correctly handles this situation and checks to see if they are an Account Admin. If so, it performs the import/update as requested. If not, it cleanly ignores the request.
BBL-438 – [As of Version 2.8.1.0] Members—Resolved issue preventing Hub Members display from properly refreshing after making one or more members Active or Inactive.
BBL-451 – Performed internal changes to further improve reliability of file download process. This also includes support for restricted intermediate-level folder permission downloads when using a Custom Connection, and improvements to the clarity of the logging information.
BBL-450 – BIMrx® Cloud Manager now determines when a downloaded Revit® cloud-shared model contains an archive of multiple .rvt files or is a single .rvt file, and correctly changes the extension to .zip when it is an archive.
BBL-455 – When the user logged onto BIMrx® Cloud Manager using a Custom Connection, Revit® cloud-shared models were not correctly displaying their Published or Not Published status. This has been resolved.

The following issues were resolved in the v2.8.1 release:

BBL-385 — Application was skipping large Revit files without indication in the log file. It now correctly downloads these files.
BBL-372 — Autodesk® Forge® has certain rate limits and quotas that apply to each different type of API access. When one of these limits are hit (due to the total load on the Autodesk® server at a given time) the call fails with an error 429: Too many requests. BIMrx® Cloud Manager now anticipates the possibility of this problem and, when it occurs, repeats the access up to three additional times. If it still fails after the fourth attempt, the process is skipped, and an appropriate indication is recorded in the log and in the log statistics.
BBL-366 — The application was not correctly handling certain error conditions generated by Autodesk® Forge® API calls (such as file already being accessed, invalid permission, etc.), causing the job execution agent to fail. The system now correctly handles these conditions, logs the error to communicate with the user why the call was unsuccessful, and continues.
BBL-n/a — When getting folder contents for files, the application was throwing a harmless background exception that did not affect the results or display to the user—but did slightly slow down processing. This error was only discernable via specialized debugging tools and has been corrected.
BBL- 349 — When certain jobs were deployed to a remote server, instead of displaying, “The task has not yet run”, it displayed, “Error -532462766” or “Error –2147024894”. This was due to a known API issue and the system now correctly displays the deployed and next run date/times and “N/A” for the Result.
BBL-279 — In Jobs, when attempting to add a project that does not exist locally, a system-level error message was displayed. Now BIMrx® Cloud Manager clearly states the following:
A Local Repository for the selected project does not exist. Please select a valid local repository location for the selected project and try again.
BBL-383 — BIMrx® Cloud Manager now supports changing the default BIM360® Project Files folder to a different name. This fix applies throughout the application and affects both interactive processes—such as file uploads and downloads in the Files and Browse modules—as well as scheduled job operations.
BBL-418 — When establishing a Custom Connection and connecting to an unauthorized Hub, an exception is raised that tells nothing of why the connection was refused--and actually appeared as though the user was connected to it when in fact they were not. A clear message is now presented describing why there was an error and why it occurred. Note—one cause of the error is not having a valid BIM360® Custom Integration defined that matches a valid BIM360® Forge App.
BBL-420 — When the user was signed in with a Custom Connection, the Hub name for Autodesk® Connection jobs was not displaying. This occurs when the user first logs on with a Custom Connection. Once they logged on with an Autodesk® Connection, then it displayed correctly once they went back to a Custom Connection. It now displays correctly regardless of the logon sequence.
BBL-405 — When an Autodesk® Connection job is deployed that triggers scheduling of a Refresh Token job, the system now prompts the user for the day of the week on which to schedule Refresh Token Job execution.
BBL-390 — In Connect, when logging out of an Autodesk® Connection, the application was preventing login as a different user.
BBL-393 — In Jobs, when processing the deployment of an Export job, the job didn’t see the project files selected and would not deploy the job.
BBL-358 — In Jobs, when doing a Dynamic Download, using the folder filter and checking include sub folders, the sub folders of other sub folders (sub-sub-folders) and files were not included as the user would expect.
BBL-407 — In Jobs, when accessing an unexpanded project folder tree view and the Select All checkbox was checked, the application crashed.
BBL-343, 357, 363, 364 —When executing either dynamic or static download or upload Jobs, unnecessary folders and/or files were being either uploaded or downloaded.
BBL-410 — In Jobs, when deploying a Job after being connected to an Autodesk® Connection for more than one hour, the user was receiving an Autodesk® token error message. The application now detects this situation and prompts the user to login using the normal login screen.
BBL-414 — In Browse and Files, application was not reporting file version higher than 9. Also, the dates reported were not the correct dates for the actual current version. BIMrx® Cloud Manager now reports the correct version and date. Additionally, date is now being reported according to the user’s local time, the same as BIM360 does.
BBL-424 — When filtering jobs by job type, Export wasn’t appearing as an option on the dropdown list. This has been resolved.
BBL-415 —Removed confusing log message stating it was publishing a project when in fact it was examining it to see if it was selected for publish; greatly speeded up static publishing job execution. Added additional breaks in the log and removed the work ‘successful’.

The following issues were resolved in the v2.8.0 release:

BBL-351, BBL-367 — When "Project Files" folder on BIM 360 is renamed files do not Upload. Applies to both manual uploads and scheduled jobs.
BBL-375 — When "Project Files" folder on BIM 360 is renamed files do not Download. Error occurred on scheduled job uploads only.
BBL-365 — When "Project Files" folder on BIM 360 is renamed files do not Publish. Error occurred on scheduled job uploads only.
BBL-352 — When an Upload job ran for more than 60 minutes the access token would sometimes expire.
BBL-284 — Jobs: Upload, Download, Export, not properly displaying Static selections after editing the job, saving it, then returning to perform more edits.
BBL-345 — License management does not allow deactivation if expire date is passed. License Manager, which is invoked from the About box, now supports deactivating an expired license then activating the new one.
BBL-366 — Scheduled Download jobs occasionally raising errors instead of logging and continuing when typical non-successful file or folder access read was encountered.
BBL-372 — The Autodesk Forge error: 429 Too Many Requests -- sometimes occurs on Download job – and causes the job execution program to fail. This is due to too frequent requests of the Forge API.
BBL-384 — When verifying email address password was being sent as the from name. This applied to email verification only but not to the actual Jobs email.
BBL-353 — In the Jobs module, after adding a new Job or deploying a Job, the current selection was not being preserved after refreshing the list.
BBL-359 — When exporting a PDF from the Jobs module, the PDF was exporting multiple models.
BBL-311 — In the Connect module, the network server configuration was crashing when the copy button was pressed and a blank VNC password was encountered.
BBL-283 — When assigning dynamic filters in the Jobs module, in come circumstances the subfolders were not being assigned/unassigned as expected.
BBL-N/A — Fixed export Job token refresh issue.

The following issues were resolved in the v2.7.3 release:

BBL-313 — Implement enhanced security measures to protect against potential hackers.

The following issues were resolved in the v2.7.0 release:

BBL-265 – Static checkboxes were not functioning correctly in in certain situations for Publish jobs set to static.
BBL-275 –The application now creates only the folders required to support the files uploaded or downloaded. Previously, when uploading or downloading, all the folders were created.
BBL-277 – The program now allows adding multiple projects to Upload/Download/Publish jobs in static mode without duplications.
BBL-278 – When saving a download static job, an unnecessary warning dialog popped up.