Is it just me or is this just the way it is? After I do some
drawing changes and perform the next check-in, the "notes" will
show up in the revision table's "Description" cell AFTER it is
checked in. Only then, will it let me to go back and place the
revision symbols (with the latest rev. scheme). This cause me to
save and check-in AGAIN which I have to force a REV (read from
file) and then I have to retype my previous notes! What the heck?
Am I missing something?!?
Also, I'm having trouble getting any type of information driven into the "Approved" cell of the revision table. When I highlight the header column, I can see the 6 Column Properties. I've added "Approved" in the drawing's properties with text/evaluation and I get nothing in the table. I even tried the properties tab in PDM but still nothing. Grrr!
Any help or advice will be appreciated!
Also, I'm having trouble getting any type of information driven into the "Approved" cell of the revision table. When I highlight the header column, I can see the 6 Column Properties. I've added "Approved" in the drawing's properties with text/evaluation and I get nothing in the table. I even tried the properties tab in PDM but still nothing. Grrr!
Any help or advice will be appreciated!
sorry Jay the company I work for does not use Lifecycles and I did not know you could not do that.
Thanks
Can you please explain what exactly is broken with the Revision Table? As far as I can tell, it's accurate with the latest revision scheme. (And it matches the titleblock's REV parameter $PRP:"Revision"). I just can't drive any "APPROVED" info.
Is everyone saying it's broken because...if you do a right-click on the table and select Revisions>Add Revision or Add Symbol, that it will not correspond with PDM's Revision Scheme? If so, I don't think SW intended it to function this way. I think that method was intended for non-PDMW users. Otherwise, PDMW should be driving the functionality of the table. In other words, PDMW users should stay away from the table's right-click Revisions>...method. Do you agree?
Opinions?
For me the following are broken,
Description, type in a description, checkin, and voila the description is erased!
Number of visible rows, flat out dosen't work.
Approved, you have already pointed this out.
I would have to strongly disagree with the description being erased and number of visible rows. This works just fine for me. The only thing I find broken is the Approved parameter and the order of operation for the revision symbol.
I hope you are not manually trying to insert a new row into the revision table and imputing your text there. In that case, you probably will see it go blank after checking in. This is because you need to "save and check in" first. During the check in process you will need to input your revision text "description" under the "notes" column. Let PDMW do the work and it will add the number of visible rows you set in the VaultAdmin. Your description should be intact if you follow this advise. I hope you get it to work. Let me know.
I find it very odd that SW would use "Description" under Column Properties in the revision table and expect you to use "Notes" in PDMW to populate this field. But that's the way I was instructed from my VAR during class.
Yes, if you let the system add the rows during checkin then it works.
The normal practice is to fill out a rev table prior to checking in.
This follows the same logic as custom properties/title block, they are filled out (except revision) before checking in.
As for the notes in pdmw aligning with revision description, that was a cop out on SolidWorks behalf. That "note field" was not intended for rev desc.
e.g. What if, as an admin, I needed to allow a revision overwrite. For documentation purposes I will add a note in PDMW describing why the revision overwrite occurred. The "note field" is perfect for this situation. That is what the "note field" was intended for and always has been.
But in SolidWorks infinite wisdom my note documenting the revision overwrite is blasted into the revision block.
IMHO, it's broken and always has been since day one.
Have fun checking in twice.
In my twenty plus years at doing this, I've seen how large and small companies handle their revisions. The majority of the companies use drawing revision tables to explain "WHAT" was changed, not "WHY" something was changed. If you want to know WHY something was changed, then I bet you could find it in the ECO, along with "what", "who", etc.
Since how most part/assembly files have different revisions than their counterpart drawings, the check-in "notes" functions differently. It is what it is! I suppose you could have a custom property in your drawing template for "Comments" to track WHY revisions were overwritten. SW plainly should have had an additional option for this...just like when you can RBC an assembly or part in the vault and "Add Note..."
I believe you are taking my comments in the wrong manner.
I just happened to be the only person who has chimed in stating that this option in PDMW Admin is broken. If you search through the archives you will find discussions about this topic. It has been discussed quite a bit.
In reference to "WHY", the why I referred to does not exist in a paper world and is not covered under any process (ECO/ECN).
If someone looks at the history of a document in a PDM system and sees a document which has been checked in at the same rev more than once, it's nice to see a reason out there.
You are somehow reading something into my reply that dos not exist.
Relax.
Good Luck!
I know that it's a bit late, but for anyone else having this problem the easier workaround is manually add a revision by right clicking on the revision table > revision > add revision. This will then bring up the revision symbol tool. Place the symbols as required and then when you check in fill in the revision info.
The symbols will stay, and you won't need to check in twice.
Enjoy