Skip to main content
6-Contributor
March 19, 2024
Solved

restrict change of lifecycle state through Importable spreadsheet

  • March 19, 2024
  • 2 replies
  • 2249 views
I am using Windchill PDMLink Release 12.1 and Datecode with CPS 12.1.0.0

How can we restrict users from changing the lifecycle state using the importable spreadsheet?
We attempted to deny/absolutely deny access to set state, but users can still change the state via the importable spreadsheet.
Additional context: Users should have access to use the importable spreadsheet but rights should be restricted only on changing the lifecycle state.
    Best answer by RandyJones

    One workaround is to simply not have the state column in the spreadsheet. It will then leave State unchanged.

    Unlike the Name and End Item columns which are required. One has to go to a lot of extra work to make sure these are not changed when importing a spreadsheet.

    2 replies

    Fadel
    23-Emerald I
    March 19, 2024

    just to be on the same wave , when u are importing the spreadsheet the state in the excel is applied to the new iteration right , the old one keep its state ?

    Fadel_0-1710859911545.png

     

    Buiꓘa
    6-Contributor
    March 19, 2024

    Thank you for your reply!

    Yes when importing the spreadsheet the state in excel is applied to the new iteration. 

    The state is editable in the spreadsheet and once uploaded you can see the changed state in the new iteration. 

    We want the user to be able to use the importable spreadsheet for updating WTParts attributes. However the user should not be able to change the state with this functionality; is there any configurations/access permission control to avoid that a user can make changes on the lifecycle state through the importable spreadsheet. 

    Fadel
    23-Emerald I
    March 19, 2024

    this use case is not a state change ,State change is within same version .

    I'm not sure if this request is possible OOTB .

     

    Buiꓘa
    20-Turquoise
    March 19, 2024

    One workaround is to simply not have the state column in the spreadsheet. It will then leave State unchanged.

    Unlike the Name and End Item columns which are required. One has to go to a lot of extra work to make sure these are not changed when importing a spreadsheet.

    18-Opal
    March 20, 2024

    You’d still need a way to automatically check that the state has been removed 🤷‍♂️

    20-Turquoise
    March 20, 2024

    @d_graham wrote:

    You’d still need a way to automatically check that the state has been removed 🤷‍♂️


    That is for sure. However assuming that most of the time the admin is the one giving the users a sample spreadsheet to use it would be up to the admin to leave out the state column in the sample.