Skip to main content
L
LH_96384075-Regular Member
5-Regular Member
August 25, 2022
Solved

Windchill issue - Rules

  • August 25, 2022
  • 2 replies
  • 2082 views

I am using Windchill PDMLink Release 10.2
Group has been created in Windchill for mfg team and rules have been set to restrict access/view for "Obsolete" state Cad data, file.
functionality is not working and user defined group (mfg/Sales) are able to view previous "released " state files . while they should not have access to complete data once obsoleted.

Best answer by HelesicPetr

Hello @LH_9638407 

 

There are several ways how to achieve your needs.

1.

It is possible to create workflow process  for promotion request or any other change workflow process, or modify existing. 

In the end of workflow process 

In the workflow, you can use a robot where you can define java code with if statement that do a job what you need. 

 

2.

Modify lifecycle and change it to a advanced. 

Create simple workflow with a robot java code to just change all version state to Obsolete.

In Lifecycle define for Obsolete state that workflow and always the state is reached all versions will be change to that state by simple WF.

 

3. 

Create customization function for that process to change all states of version. 

 

 

All options needs to know how to crate java script that change the state of all versions

 

PetrH 

2 replies

HelesicPetr
22-Sapphire II
HelesicPetr22-Sapphire II
22-Sapphire II
August 25, 2022

Hi @LH_9638407 

That is normal behavior if the previous versions are in Released state.

If you need to do not allow them see all versions you need to change states of all versions to obsolete.

 

ACL rules apply to a object State and if previous version is not in that restricted state user will see them if there is rule to allow it.

 

You expect different behavior then Windchill is designed I guess.

 

PetrH

    L
    LH_96384075-Regular MemberAuthor
    5-Regular Member
    August 25, 2022

    Thank you for your quick response. 

     

    Can you please let us know if there is any method / process to set released state of all revision to obsolete at once?

    example : part has revision A,B,C,D , All revision are released, 
    Obsoleting D revision should obsolete all revision (A,B,C) at released state. 

     

    Thank you!

    HelesicPetr
    22-Sapphire II
    HelesicPetr22-Sapphire IIAnswer
    22-Sapphire II
    August 25, 2022

    Hello @LH_9638407 

     

    There are several ways how to achieve your needs.

    1.

    It is possible to create workflow process  for promotion request or any other change workflow process, or modify existing. 

    In the end of workflow process 

    In the workflow, you can use a robot where you can define java code with if statement that do a job what you need. 

     

    2.

    Modify lifecycle and change it to a advanced. 

    Create simple workflow with a robot java code to just change all version state to Obsolete.

    In Lifecycle define for Obsolete state that workflow and always the state is reached all versions will be change to that state by simple WF.

     

    3. 

    Create customization function for that process to change all states of version. 

     

     

    All options needs to know how to crate java script that change the state of all versions

     

    PetrH 

      L
      LH_96384075-Regular MemberAuthor
      5-Regular Member
      August 25, 2022

      Also, Is there a possibility for members with certain group to not access/view files when it is obsolete in latest revision?.

      Example: Cad data has rev A, B, C .   Rev A, B is released/ unreleased and C is obsolete. Rules/configuration is customized for not to show whole cad data   considering "obsolete"  state in any of the revision?.

       

      Thank you!

      T
      23-Emerald IV
      TomU23-Emerald IV
      23-Emerald IV
      September 9, 2022

      No, it doesn't work that way.  The access rules are going to show someone everything they're allowed to see, even if it's not the latest revision (or iteration).  If you allow someone to see 'Released' objects, then they can see all of the release objects.

       

      A..1 - In Work

      A.2 - In Work

      A.3 - Released

      B.1 - In Work

      B.2 - Released

      C.1 - In Work

      C.2 - Obsolete

       

      If someone is allowed to see 'In Work', they are probably also allowed to see 'Released' and 'Obsolete', so they could see everything above.

       

      Someone who's only allowed to see 'Released' will only see A.3 and B.2.  They won't even be able to tell that C.1 or C.2 exist.  When they search for 'Latest', they're going to get B.2 (the latest version they can see.)  If you allow them to see both 'Released' and 'Obsolete', then when they search for 'Latest' they will get C.2 (the latest version they can see.)

        L
        LH_96384075-Regular MemberAuthor
        5-Regular Member
        February 7, 2023

        Thank you for the explanation!

        Terms & ConditionsCookie settingsAccessibility statement