acciardi
Computer
- Jun 6, 2006
- 143
Hello all -
My design team has been on NX4/TCe for about a year now and one of the things we pine for the most is a local "workspace" into which you can check out parts.
I-Deas/TCe still supports this metaphor, and I was wondering if TCe can be configured to let NX users do the same.
The benefits of a local workspace are many... you can have a little sandbox to play with parts in and be able to save your work without having to save everything back to the main vault.
It also avoids the habit of putting unfinished work back into the vault. We often pull up parts that are half-finished because the user wanted to save his work. Everytime you hit Save in NX the data goes into the vault, but in I-Deas (and in Pro/Intralink) the Save is to the local drive and the CheckIn pushes it into the vault.
I know that there are Workflows that can set status bits that, combined with load options, can filter the parts that are retrieved by release state. But it seems like a lot of extra work when you can just put things in the master vault that are usable and keep the WIP in the local drive.
Any help or advice on this is greatly appreciated.
Ed
My design team has been on NX4/TCe for about a year now and one of the things we pine for the most is a local "workspace" into which you can check out parts.
I-Deas/TCe still supports this metaphor, and I was wondering if TCe can be configured to let NX users do the same.
The benefits of a local workspace are many... you can have a little sandbox to play with parts in and be able to save your work without having to save everything back to the main vault.
It also avoids the habit of putting unfinished work back into the vault. We often pull up parts that are half-finished because the user wanted to save his work. Everytime you hit Save in NX the data goes into the vault, but in I-Deas (and in Pro/Intralink) the Save is to the local drive and the CheckIn pushes it into the vault.
I know that there are Workflows that can set status bits that, combined with load options, can filter the parts that are retrieved by release state. But it seems like a lot of extra work when you can just put things in the master vault that are usable and keep the WIP in the local drive.
Any help or advice on this is greatly appreciated.
Ed
