-
Under Review
Can we split the emails between emails from projects/scheduled tasks and emails from user run tasks?
We are constantly running automated model checks and publications, which fail due to simple things that the admin can take care of, but all users assigned to that project are getting notified. So we turn off their email notifications, which then causes them to not receive emails when they run tasks themselves.
-
Constrain task to specific task server
As a coordinator or platform admin, it would be great to be able to pick a task server when sending off a task. We regularly need to test new tasks on multiple projects and it doesn't always make sense to constrian the entire project to a specific task server.
-
Under Review
GTP Stratus - Auto Publish
GTP Stratus is a fabrication tool used to track the fabrication process through a project's life. Currently, you have to manually publish Revit models up to GTP Stratus to get the latest content. Could it be possible to automate this?
-
Load Families into models.
It would be great if clarity could pick up families in a model or file location and load them into selected models and sync. It would need to know if you wanted to overwrite or overwrite with parameter values and keep a log of any errors it dismisses as it loads in the families.
-
tag tasks when they are part of a sequence
When there are many tasks and sequences, and a task is being modified it is not obvious that it will affect a sequence or that it is part of one. Perhaps if tags were added to a task when it was added to a sequence.
-
Planned
creator and modifier
Could you add parameters to show who created a task and who modified it last?
-
Under Review
Clarity Task Management UI
When working on editing tasks would it be possible to manage the "Time", "Enabled" and "Launchable" toggles at the Setup task Page level instead of having to open and edit each task individually?
A minor inconvenience that could save a couple of minutes when editing tasks for larger projects.
-
Under Review
New Metric/ Alert - "User" links
I've started to find a lot more "User" machine links than we'd prefer to see. I'd love a metric to keep track of this or other "unapproved" link locations, like old project folders or non-library locations.
Example screenshot attached. These links should be saved in our library or in the ACC Desktop location. Not in C:\Users or via OneDrive at all.
Some metric/ alert to be able to search for a string in the "link location" you're already saving to the sql would be great.
-
Add Current Model Size to project home page
Add Current Model Size to project home page
-
On the Project page add a column for the task server assigned to that project
On the Clarity Project page add a column for the task server assigned to that project. It would make it easy to see and balance the tasks running on various task servers.
-
Improve how Clarity deals with missing Dynamo scripts
Current situation if a script is not available on the task servers anymore:
- Can't create new tasks for this script (good)
- Existing tasks can be copied (not so good imo)
- In edit mode, the Dynamo inputs section is missing (of course)
- In edit mode, there is no indication as to what is going on with that task (definitely not good)
- If scheduled, the task is never claimed (not good either)
Suggestions for improvement:
- Show a warning in edit mode (e.g. "Dynamo script could not be found on any task server")
- If scheduled, have such tasks fail immediately
- Do not allow
-
Under Review
Model Metrics Alerts should have more options to filter projects to Office or Tag
When creating a Model Metrics Alert, it is currently only possible to select All or individual projects. If this could reference Tags as well, it would allow alerts to be created that were forwarded to the correct people based on the project Tag, such as office or practice area.
-
Twice a day task schedule
I would need to be able to schedule a task to run twice a day. Right now I need to duplicate the task to run it a second time on the same day. It make it difficult to maintain and cause mistake and error.
-
Parameterized file and path names
Hi,
I have a suggestion that would make a major quality of life improvement.
Clarity should include sheet parameters in file naming and/or in Artifact Sub-folder.
By doing so parameters such as discipline of sheet set could be used to create a folder, phasing would be put in specified catalog - all from one task.
In summary by adding dynamic parameters from sheet to file path naming in Clarity we could achieve clearer documentation sorting with less tasks to manage and run.
-
Add Family File Size to Index Model Families Reports
I ran my first Index Model Families task and was surprised that the family file size was not in the report. If File Size was in the report, I could quickly pinpoint families that are too big. Could the file size metric be added to the family indexing?
Thanks,
-
relative path
A folder structure is constant (more or less) from project to project. It would be very helpful to specify a path for actions relative to the Revit project folder. It would save time on copying tasks from project to project - no need to adjust the UNC path for every project.
Thank you.
-
Display thresholds in model metrics graphs
The model metrics graphs are a great tool to see how a certain metric has developed over time. It would be really useful, though, if those graphs would also display the firm metric guidance guidance thresholds defined for caution/concern and issue (while taking into account model size, small model factor and large model factor). See attached mockup.
-
rte
There is a RVT and RFA upgrader, these are great. A RTE would be nice. We don't have a lot of those but still have a few.
-
Add office to the available Keywords
I think it might be helpful for those users with multi office organized servers to allow the use of the office as a keyword in the post task action.
In our offices the file path looks like this: //servername/office/project name/
If we could leverage the assigned office parameter set during the project startup it would dramatically simplify our project startup process.
This would allow us to set post task action paths in the task templates as \\servername\[office]\[Project]\ and eliminate the need for template tasks that are specific to each office.