Modify with warnings or Read only

[SrGilberto]

Ever since we went to Wildfire we experience 2 problems. Before an assembly can be checked in all family table instances have to be verified (It was not like that in 2001). 1> parts get unintentionally changed. 2> Things have to be updated and verified before we can check in.

Would it solve the problem if all our library parts are changed to "read-only" status as opposed to "Modify with warnings" (which is the way it's set now).

We also have to have all our instances in workspace and verified before we can check into commonspace.

I've suggested that all library parts should be set to "Read-only" by default to see if that resolves the problem. Our library parts are being un-intentionally changed, and we are constantly having to update them.
Will the "Read-only" status help us?

Regards,
SrG.

 

[mechbull]

I think your prob is a glitch in intralink and pro

we used wf 2.0 with i-link 3.4
same checkin procedure

the issue we had was parts created in 2001 or earlier seem to always need verified for no apparent reason.
checked out parts to change a note in drawing and go to check in and get the error that parts needed verified

VERY annoying

I am not allowed to mess with the read only option your asking about but please let us know if you solve this

the alternative is to unset that part of intralink where it needs the verification to check in parts

good luck

 

[Tofflemire]

Hi SrGilberto,

I am using Intralink 3.2, so I can not comment on the version you are using. What I have found is this.

I do not recommend setting them to READ ONLY, you can not add to family tables if this is set.

Play with you Intralink settings so if an assembly is saved it does not say piece to up the version.

You can see who is changing this parts by who checked them in last. Then Train person or people at what is happening and this should reduce and help fix the problem.

As far as verifying goes, this becomes a habit, I do not even think about it, I just do it so all my assemblies work...

Tofflemire

 

[SrGilberto]

I sent your response to my Pro/IT_guy and he sent this response and asked the question:

I found a reference to a command, but I cannot find the command itself. I found a "verify_on_save_by_default" which would verify all parts as they are saved, but my concern is what if one of the instances fails verification. Did anyone on your fourm indicate what the command is?


Here's my question:
Would it help if we set the variable "verify_on_save_by_default" to "yes", but have all our library parts (screws and bolts) set to a status of "Read-only". That way all our custom family instances would get verified, but none of the library parts would get incidentally modified, and therefore would not need verification. On paper this sounds like it would work, but does anyone here know if this would solve the problem?

Regards,

 

[looslib]

You can set permissions in Intralink so that engineers get Library files checked-out as Read-Only, while admins/Librarians can have modify rights to the library files. It is a setting with Pro/I on how the system handles files at check-out time. the files in the Library are at an In-Work status at all times.


"Wildfires are dangerous, hard to control, and economically catastrophic."

Ben Loosli
Sr IS Technologist
L-3 Communications