Similar to the find and replace functionality in MS Word and MS Excel this would be a good tool for finding files in not only the vault, but also in factory files as well.
This suggestions is to further the idea link posted below
and based on this thread.
with reference to :
in light of this recommendation, and with reference to my current situation looking after vault collaboration 2012, i wonder if there is some configuration improvements we may be able to think about that would allow admins to use a valid default lifecycle state for inventor (design files) but still allow dwf files that are generated for these to not belong to the default state or category that would be used for day to day engineering drawings.
that way admins could setup the vault to suit the best option for the engineering files (inventor files) and also configure the dwf file generation to ensure that they will behave as desired (or rather needed if you read the article linked herein).
it would to me be an improvement and also potentially allow admins to see that there is a need to consider the dwf file issues sooner rather than later, on this topic, even some notes in the help file for this configuration setting that mentions some of the things mentioned in the article could be of help.
this could be considered perhaps along with some other ideas relating to the job processor, perhaps an option in the job processor to allow admins to dictate whether dwf creation is to follow the default category (and its associated lifecycle state) or to go into an alternative category or state).
error - some items in the original selection are no longer available. please refresh and try performing the operation again.
this is an error message we see in the following circumstance:
setup a search, find all target files (in this case all dwf files that belong to a lifecycle state), delete large batches of these found files... immediately after successful delete, we see the error message that says we need to refresh and perform the operation again.
that is fine, we click ok and finish, however when you have just deleted 1000 dwf files, the error is displayed for each one. even hitting escape key 1000 times can take a while.
i wonder if we need to have this error message displayed in such a fashion?
one or two clicks should be enough. even the opportunity to refresh or restart the search again as another button option on this error message should be enough to kill it ?
many thanks for you consideration.
the goal is to have dwf files generated for released state, when files are released from within vault explorer.
we have the present option to enable the "Action" to update properties and create visualisation file (as can be defined in the lifecycle management configurations). with this enabled, the property update and dwf creation then occurrs via the job processor running on one or more users machine overnight.
this presents a problem, in that there are numerous hurdles to overcome if wishing to update properties on released files, especially across a replicated bunch of servers.
i would very much like the option to enable the dwf creation (automatically via the state change) all by itself, without having the property update happen.
Why isn't there a coonection to the "Saved Searches" in Vault through Inventors Task Scheduler?
I would love to see in the future
NTI CADcenter A/S
for consideration ;
in our operation we have seen some file / folder ownership management problems (inability to take ownership) seen between relicated servers. ie a remote server is down = no way to transfer ownership to other servers / sites.
i think there is the need to have some improved functionality on this topic and other general topics relating to the replicated environment.
is it sufficient to accept that if a remote server is down that there is no way ever to get ownership back of files back? despite very short or zero lease times etc etc.
i would have thought that the provider server would be able to force ownership back to itself or other server if the files were not checked out. i have searched to no avail & also have been advised by our VAR group that we cannot do this.
if that is the case then i feel that with some consideration of improved functional development that this would be possible or at the least have something along the lines of automatical ownership transfer configure to send ownership from remote sites after hours, back to the server who owns the files again before business resumes the next day. that way if a site does not boot up at the start of business, the other remote servers have the choice to take ownership if it is urgent.
this may not be the answer but with sensible discussion and development there may be solutions to the situations that could arise.
Vault copy design desperately needs a copy and replace function built in. I'm working with a very large assembly (1,000 or so different parts) and I have to rename each component manually. There is a feature to add Prefix and Suffix but there is no feature to remove the previous prefix or suffix. Furthermore, I spent 4+ hours renaming every part only to have the copy design fail. There should be some way to save the copy design before executing. A simple find and replace feature would save me hours and hours.
Why don't we make Check in/Check out optional?
Example with document locks and without Check in/Check out:
I'm working on a fast network and data loading is not an issue.
Why do I need to Check out then?
I just want to (automatically) lock the documents I'm working on and I do not want the hassle of Check in/Check out.
So, when I hit the Save button everything is saved into Vault.
Example with Check in/Check out:
- When I'm going to work on site, I can just check out all documents I need and when I'm back I can check in all these documents.
- when I'm working at home trough a "slow" internet connection, I do not want all the traffic every time I save something, then I need to use check out at the beginning of my work and check in when I'm done.
This can be a user setting but also needs to be a admin setting to overrule users.