From the Vault Web Client all you can see on an item is if its in a change order. I would like to be able to click on the change order icon and see the change order title, description, and current state.
I agree. Many times we have employees that don't need to alter or interact with a change order, they just need to review it or look it up for reference purposes (Sales e.g. to support an existing sales order or Purchasing to notifiy a supplier of a change to an item with an active PO). It would also be nice if the web client could be configured which ECO properties to show.
We paid for 8 extra licenses of Vault to get this functionality.
Status changes in Vault Webclient would be a nice thing.
Our reviewer's for welding quality management for example don't have CAD workstation but only citrix clients.
It would be great if they could simply review drawings and reject or accept them (possibly with a comment).
The web/thin client is intended for non-engineering based Vault access. Obviously this could vary based on organisational requirements, but I find that a high majority of these people are needing to view what is changing within the design process. However, you cannot view ECOs in the web/thin client. Thus rendering the web/thin client an obsolete entity in a lot of companies using ECOs within Vault.
Granting access to ECOs for staff who don't require a full client license would be a huge help for a lot of customers, it's pretty straight forward and clear that this would be beneficial and I can't think of any valid reason why ECOs should be ommitted from the web/thin client.
Compared to the thick client, what tabs in the Change Order are important to have in the Thin Client?
Obviously I can't speak for everyone, but I think the 'General' tab would be enough to cover most bases. Most non-engineering staff would likely only need to know the change details, description, who raised it, when, current state, all of that is covered on the General tab. The records tab would also be useful but I suspect most would sacrifice that if it meant we could get ECOs visible in the client ASAP. I say that as typically the product under change should usually be in the description, so non-engineering staff may have little to no interest in seeing which raw files/items are hooked to the ECO.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Share and shape product ideas.
Log into access your profile, ask and answer questions, share ideas and more. Haven't signed up yet? Register
Upgrading to a 2015 product? Make sure to check these out 1st!