The post task action "Google Drive Upload" creates duplicate named files rather than creating a new version of the file. Google Drive allows multiple files to exist in the same folder with the same name (files in Google Drive are more ID based than file path based) and the api defaults must be to create a new file rather than look for a file with the same name and create a new version. Clarity's default behavior should be to create a new version, not new files with the same name.
It will surprise nobody here that sometime around August or September Autodesk decided to tell us the cumulative file size of the model(s) on BIM360. That is, that particular model and all the models that it currently has linked. Please alter the software to report meaningful individual file sizes again.
It would be great if we could control the schedule for the periodic cleanup on Task Servers. It would also be good to have a log for the cleanup results.
It would be nice to have an ignore option for the models listed in the Untracked Models section. This list keeps growing longer every day with temporary models that just add noise to the list.
Would it be possible to make the Cleanup more frequent and/or more aggressive? Hourly cleanup would be ideal if it were able to detect and skip the cache associated with any active Revit Sessions and delete all the others. BIM 360 Cache is chewing up space at an alarming rate.
Clarity should be able to uploade RVT files with Links to BIM 360 with the option to select the parent file. This way the model links will resolve and the 3d model and Sheets will show the links needed,
I would like to have the ability to see all the tasks scheduled for my task server for the next 7 days and completed tasks from the last 7 days. Then export the data to Excel. This would help me plan my tasks for all the projects I'm managing.
Please add information on how to use the "TaskUtility" in the help file especially related to how to select a task to kill as its not apparent on how to do this
It would be great to have an ability in the UI to mark models that are crashing (or corrupt) so that we can better analyze data related to a problem models
then this would allow us to filter model metrics by poor models (vs ok or good models) and find the patterns with the issues
Users often complain about how cryptic Clarity alert emails are, especially model alerts. It would be great to have an additional field for a custom message that we could define for each configured alert to explain why the user is receiving the alert and which action they should take next.