AnsweredAssumed Answered

I hate Mondays...need help

Question asked by Corey Hinman on Mar 17, 2008
Latest reply on Aug 14, 2017 by John Stoltzfus

Like • Show 1 Like1
Comment • 18

Ok, here is my issue. I have a group called view only. They have permissions to "read file contents" on Released files....nothing on Pending...oh, here's the lifecycle

Initital=>Pending>Release>Pending (for any revisions)

I DO NOT have "always work with latest version" checked. I have a part that is at Rev A released, but there is also a Rev B Pending in the system. If I search for that file I see zero results.

How do I set the group to see the latest release version, even if it's not the latest actual version?

Corey

Corey Hinman Mar 18, 2008 7:11 PM

Correct Answer

BINGO....In the workflow the "Ignore Permissions from Previous States" was checked on the States in question. I guess I misunderstood the real use for that little bitty checkbox that caused me so much frustration.

See the reply in context

No one else had this question

Outcomes

18 Replies

Joy Garon Mar 17, 2008 12:11 PM
Mark Correct
Correct Answer
Hi Corey -

Well, if it helps, this Monday is special - St. Patricks Day! Not that I condone drinking to solve the Monday blues :-)

Anyway, a thought on the viewer permissions.

I'm assuming that the permissions per folder and atate permissions for this group has 'Read file contents' checked. You may also have to check 'Show working versions of files' on permissions per folder.
---- exerpt from Administration Guide -----
Show working versions of files
User may see both working versions and revisions of files. Note that this
permission must be set together with Read file contents in order to see a file
that has no revision set (or if not using revisions).

Regards,
Joy
Like • Show 1 Like1
Actions
- Corey Hinman @ Joy Garon on Mar 17, 2008 12:13 PM
  Mark Correct
  Correct Answer
  That is checked unfortunately. When we make a revision the first thing we do is bump the rev level so we are actually approving the new revision.
  Like • Show 0 Likes0
  Actions
  - Joy Garon @ Corey Hinman on Mar 17, 2008 12:25 PM
    Mark Correct
    Correct Answer
    Hmmm...
    
    Do you have multiple workflows? Are you sure that you have checked the state settings for each workflow?
    Like • Show 0 Likes0
    Actions
    - Corey Hinman @ Joy Garon on Mar 17, 2008 12:28 PM
      Mark Correct
      Correct Answer
      nope, just one. Confusing the bejesus out of me.
      Like • Show 0 Likes0
      Actions
      - Lucas Dexter @ Corey Hinman on Mar 17, 2008 6:31 PM
        Mark Correct
        Correct Answer
        Hello Corey,
        Can you browse to the file and find it? Here is how the rights work from the testing I have done:
        
        1) Group rights = Show working versions
        State rights = Read files (in Released state)
        Results = See everything that has gone through that state (released). Everything else is grayed out up to that state.
        
        2) Group = Do not show working versions
        State = Read files (Released)
        Results = See only revision no matter what. Does not tell user what state file is in other than released. History does show complete history.
        
        Hope this helps,
        
        Lucas
        Like • Show 0 Likes0
        Actions
        Lucas Dexter @ Lucas Dexter on Mar 17, 2008 6:38 PM
        Mark Correct
        Correct Answer
        Corey,
        One more of note, in scenerio #1, users can only get versions that gone thru that state, in this case it would be the Released state. Otherwise it gives a dialog that says they do not have rights to get the file.
        
        Lucas
        Like • Show 0 Likes0
        Actions
        Corey Hinman @ Lucas Dexter on Mar 17, 2008 6:59 PM
        Mark Correct
        Correct Answer
        I haven't had to use Solidworks with Enterprise (I know, I know)...but I wonder if it has to do with how our CAD guy bumped the revision. In the History it looks different between when it went to A and when it went to B.
        
        Also I did get latest version and the local Rev still show "no rev"
        
        See attachment.
        Like • Show 0 Likes0
        Actions
        Joy Garon @ Corey Hinman on Mar 17, 2008 7:44 PM
        Mark Correct
        Correct Answer
        Corey,
        
        In the search results, right click, Get Version on one of the documents and see what the versions are and if you can get a previous version.
        I noticed that the last event in your history was a rename. See what the document name was prior... you may want to search on a different variable like document number of something....
        
        Joy
        Like • Show 0 Likes0
        Actions
        Corey Hinman @ Joy Garon on Mar 17, 2008 7:46 PM
        Mark Correct
        Correct Answer
        If I get the one that says "A" it says the local revision is A also.
        Like • Show 0 Likes0
        Actions
        Joy Garon @ Corey Hinman on Mar 17, 2008 7:50 PM
        Mark Correct
        Correct Answer
        What happens if you get revision B (which should be version 8)?
        
        Like • Show 0 Likes0
        Actions
        Corey Hinman @ Corey Hinman on Mar 17, 2008 7:53 PM
        Mark Correct
        Correct Answer
        says local rev B.
        
        I can only see it because I'm in the admin group.
        Like • Show 0 Likes0
        Actions
        Joy Garon @ Corey Hinman on Mar 17, 2008 8:18 PM
        Mark Correct
        Correct Answer
        Well Corey -short of looking at your system directly I don't know what else to suggest. Have you contacted your VAR?
        Like • Show 0 Likes0
        Actions
        Corey Hinman @ Joy Garon on Mar 18, 2008 2:35 PM
        Mark Correct
        Correct Answer
        I think I might be able to solve this, but I'm unable to test. I'm trying to create a new work flow to send a file to and I'm getting the following error:
        
        Could not create xref tree
        could not access the item in the database
        Like • Show 0 Likes0
        Actions
        Corey Hinman @ Corey Hinman on Mar 18, 2008 7:11 PM
        Unmark Correct
        Correct Answer
        BINGO....In the workflow the "Ignore Permissions from Previous States" was checked on the States in question. I guess I misunderstood the real use for that little bitty checkbox that caused me so much frustration.
        Like • Show 0 Likes0
        Actions
        Joy Garon @ Corey Hinman on Mar 18, 2008 8:16 PM
        Mark Correct
        Correct Answer
        you know.... I thought about that but I was trying to figure out what commands it applied to... glad you figured it out... :-)
        Like • Show 0 Likes0
        Actions
Joy Garon Mar 17, 2008 6:27 PM
Mark Correct
Correct Answer
Hi Corey -

Are you saying that if a user in the Viewer group searches for document ABC.sldprt (which is in the vault as Released Rev A and Pending Rev B) and the group can 'read file contents' that nothing is coming up on search?

I can only think of two things:
1) permissions are not set correctly somewhere
2) search is not being performed correctly (clear search, select vault root and only search by filename)

Joy
Like • Show 0 Likes0
Actions
Jeff Sweeney Mar 19, 2008 4:08 PM
Mark Correct
Correct Answer
That option is so confusing! Can someone give me a practical reason for its use? i.e. what's the advantage of this option over simply setting the state permissions one at a time?
Like • Show 0 Likes0
Actions
John Stoltzfus Aug 14, 2017 2:59 PM
Mark Correct
Correct Answer
A Blast From the Past -

This caught my eye - "I Hate Mondays" -

Well today is Monday and "Monday's are very close to 1/7th of your life, make them Great"
Like • Show 2 Likes2
Actions

I hate Mondays...need help

Outcomes

Related Content

Recommended Content