The approver of a Submittal can now add a status code on the fly when approving so in a way this is good so they can have ones like "Reviewed as noted" but on the flip side after a while this list will become very messy since it is not tied to Vista Status codes and their is no oversight. Is it too much for the Architect to ask the GC for a new approval "status code" so they can be managed and tie them back to Vista?
Guest
| Company | Viewpoint |
| Job Title / Role | SE |
| I need it... | 3 months |
Dear Viewpoint Suggestion Box contributor;
We at Viewpoint sincerely thank you for your contribution to Suggestion Box on how we can improve Viewpoint products. While we can’t do everything at once, we rely upon your feedback to help guide the prioritization of our product improvements, and Suggestion Box is a critical tool for us to understand and prioritize our customers’ needs.
Viewpoint reviews Suggestion Box regularly for all of our products and updates statuses, adds comments, and performs various house-keeping (including deleting) as needed to ensure that Suggestion Box is maintained as a productive environment for product enhancements requests.
© 2023 Trimble Inc. All Rights Reserved. Viewpoint®, Vista™, Spectrum®, ProContractor™, Jobpac Connect™, Viewpoint Team™, Viewpoint Analytics™, Viewpoint Field View™, Viewpoint Estimating™, Viewpoint For Projects™, Viewpoint HR Management™, Viewpoint Field Management™, Viewpoint Financial Controls™, Vista Field Service™, Spectrum Service Tech™, ViewpointOne™, ProjectSight® and Trimble Construction One™ are trademarks or registered trademarks of Trimble Inc. or its affiliates in the United States and other countries. Other names and brands may be claimed as the property of others.
We're working on the ability to filter which status codes are available on a given project and lock the list down to just those status codes so there is no more unexpected statuses added on-the-fly
This is a big problem for our company as well even with the adding on fly being restricted to project editors and admins. Since the security groups are still so basic we are finding most of our internal users need editor access so that means they are all able to create status codes on the fly and this directly impacts custom reports and processes in Vista we have spent a lot of money to create. - Big big problem!
I just realized this was possible - by finding 3 random status codes in the list. . . now for how to unwind them and get rid of them. . . .
Aaron
Please also see Related Suggestion "Status Codes-Reviewer Cannot See"
We'll be addressing soon -- first limiting who can add - then management
Tom:
We did not realize the mess this was creating in our company, see suggestion I just posted in Related Suggestion "Status Codes-reviewer cannot see"