AnsweredAssumed Answered

How to flag edit-box properties as read-only after transition

Question asked by Vasin Paradorn on Feb 25, 2019
Latest reply on Feb 25, 2019 by Vasin Paradorn

Like • Show 0 Likes0
Comment • 7

Greetings!

GOAL : Part Number that can only be changed (through Data Card edit-box) in the Initial State & prior to transitioning out of the Initial State.
After leaving the Initial State, no one should be able to change or update it (except for Admin).

EXPLANATION :

I am in the process of configuring my development SOLIDWORKS PDM Professional environment.

I would like to know how I can "Flag" a Part Number Edit-Box property as Read-Only after transitioning out of the initial state.

The plan is to only allow user to change the Part Number only in the Work In Process state (Initial State).

Once the object transition out of the Work In Process state, the object will never return to this state.

The work flow is:

Work In Process (Initial State) ----Release----> Released ----Request Change----> Change Pending ----Release----> Released.

I have looked at

1. Version Free Variable (No Good):

1.1 Does have State Specific Permission (Edit version free variable data)

1.2 Does NOT not map to SWs Custom Property.

2. Deriving Part Number from File Name (No Good):

2.1 Does have State Specific Permission (Add or rename file)

2.2 Does map to SWs Custom Property

2.3 Does NOT want "John Doe - Test Part Number 1" as the Part Number

NOT every file will have a Part Number (users will most likely not tolerate Part Number File Name only requirement)

Would anyone have any recommendations / suggestions?

Thank you very much!

-Vasin

Craig Schultz Feb 25, 2019 12:00 PM

Correct Answer

Shot in the dark here, but.....

Make another variable ie "WIPRename"

Set your PN variable with a control to grey out if WIPRename text equals yes,

When the parts go into the workflow set the variable to "yes"

Once the file transitions out of the WIP state, create an action to set WIPRename to no.

That should grey out the variable after it goes past the first state. And it'll stay that way as long as you don't create an action to set it back to "yes". You will probably have to create an initial state so you can set the variable once files are added to the vault. I do this to set/reset variable when doing copy tree actions. Initial state -- (auto transition setting variables)--> WIP would be the first transition. Then WIP --> prototype--> production --> WIP or whatever your workflow is.

See the reply in context

No one else had this question

Outcomes

Craig Schultz Feb 25, 2019 12:00 PM

Shot in the dark here, but.....

Make another variable ie "WIPRename"

Set your PN variable with a control to grey out if WIPRename text equals yes,

When the parts go into the workflow set the variable to "yes"

Once the file transitions out of the WIP state, create an action to set WIPRename to no.

Actions

Ants Palgi @ Craig Schultz on Feb 25, 2019 1:26 PM

Whatever clever things you invite in PDM datacard, don’t forgot that users can change everything from part custom properties via SolidWorks...

Actions

Vasin Paradorn @ Craig Schultz on Feb 25, 2019 3:35 PM

Hi Craig,

Thank you for the reply.

I have completely forgotten about the Control --> Control Logic for a specific object in the Data Card.

Based on what you said, I could tie the "Grey out" action to all of the states not equal (!=) to Work In Process:

That means, only Work In Process state will allow user to update the Part Number field.

I believe that this will work. As Ants said, user can always change everything from the SWs File Custom Properties but I am hoping that I can find a way of reloading the Part Number from the Previous State (Released). Since it should not have changed.

Thanks again for the pointer. Have a good one!
-Vasin

Actions

Kamil Wilkosz Feb 25, 2019 1:23 PM

Hello Vasin,

If you don't want to have file names like "John Doe - Test file..." you should add state like "waiting for approval" or similar where the names will be verifying. Because you cannot set that part number have to have defined structure, you can only set minimum or maximum number of characters. So if you allow user to modify part number you allow them to write whatever they want (if this won't be verifying).

In my opinion the point 2 which you were testing is a good way. Does the Part Number is generated via Serial Number? Becasue if it does, you may try to not allow change part number on data card but only via file name generated via Serial Number. If user would like to change a file name, he/she can use "Move Tree" command to do that. But it still do not protect you from file name like "John Doe - Test file...".

Actions

Vasin Paradorn @ Kamil Wilkosz on Feb 25, 2019 3:39 PM

Hi Kamil,

Thank you for your reply.

Please note that I will not be using a serial number generator for the file name (I probably should).
Thank you again for your response!

Actions

Jeremiah Feist Feb 25, 2019 3:03 PM

if you are willing to have the state change move the file to a different folder, you can have different data cards for the different folders...

Actions

Vasin Paradorn @ Jeremiah Feist on Feb 25, 2019 3:42 PM

Hi Jeremy,

Thank you for your reply.

I was thinking about that as well. However, there are multiple organizations that will be using the same Vault and Workflow. So I am not sure if I can perform a move within the organizations' main folder. I believe that Control Logic might be sufficient for my need. If it is not, I will certainly explorer the move possibilities.

Actions

7 Replies

Craig Schultz Feb 25, 2019 12:00 PM
Unmark Correct
Correct Answer
Shot in the dark here, but.....

Make another variable ie "WIPRename"
Set your PN variable with a control to grey out if WIPRename text equals yes,

When the parts go into the workflow set the variable to "yes"

Once the file transitions out of the WIP state, create an action to set WIPRename to no.

That should grey out the variable after it goes past the first state. And it'll stay that way as long as you don't create an action to set it back to "yes". You will probably have to create an initial state so you can set the variable once files are added to the vault. I do this to set/reset variable when doing copy tree actions. Initial state -- (auto transition setting variables)--> WIP would be the first transition. Then WIP --> prototype--> production --> WIP or whatever your workflow is.
Like • Show 0 Likes0
Actions
- Ants Palgi @ Craig Schultz on Feb 25, 2019 1:26 PM
  Mark Correct
  Correct Answer
  Whatever clever things you invite in PDM datacard, don’t forgot that users can change everything from part custom properties via SolidWorks...
  Like • Show 0 Likes0
  Actions
- Vasin Paradorn @ Craig Schultz on Feb 25, 2019 3:35 PM
  Mark Correct
  Correct Answer
  Hi Craig,
  
  Thank you for the reply.
  
  I have completely forgotten about the Control --> Control Logic for a specific object in the Data Card.
  Based on what you said, I could tie the "Grey out" action to all of the states not equal (!=) to Work In Process:
  That means, only Work In Process state will allow user to update the Part Number field.
  
  I believe that this will work. As Ants said, user can always change everything from the SWs File Custom Properties but I am hoping that I can find a way of reloading the Part Number from the Previous State (Released). Since it should not have changed.
  
  Thanks again for the pointer. Have a good one!
  -Vasin
  Like • Show 0 Likes0
  Actions
Kamil Wilkosz Feb 25, 2019 1:23 PM
Mark Correct
Correct Answer
Hello Vasin,

If you don't want to have file names like "John Doe - Test file..." you should add state like "waiting for approval" or similar where the names will be verifying. Because you cannot set that part number have to have defined structure, you can only set minimum or maximum number of characters. So if you allow user to modify part number you allow them to write whatever they want (if this won't be verifying).

In my opinion the point 2 which you were testing is a good way. Does the Part Number is generated via Serial Number? Becasue if it does, you may try to not allow change part number on data card but only via file name generated via Serial Number. If user would like to change a file name, he/she can use "Move Tree" command to do that. But it still do not protect you from file name like "John Doe - Test file...".
Like • Show 0 Likes0
Actions
- Vasin Paradorn @ Kamil Wilkosz on Feb 25, 2019 3:39 PM
  Mark Correct
  Correct Answer
  Hi Kamil,
  
  Thank you for your reply.
  
  Please note that I will not be using a serial number generator for the file name (I probably should).
  Thank you again for your response!
  Like • Show 0 Likes0
  Actions
Jeremiah Feist Feb 25, 2019 3:03 PM
Mark Correct
Correct Answer
if you are willing to have the state change move the file to a different folder, you can have different data cards for the different folders...
Like • Show 0 Likes0
Actions
- Vasin Paradorn @ Jeremiah Feist on Feb 25, 2019 3:42 PM
  Mark Correct
  Correct Answer
  Hi Jeremy,
  
  Thank you for your reply.
  
  I was thinking about that as well. However, there are multiple organizations that will be using the same Vault and Workflow. So I am not sure if I can perform a move within the organizations' main folder. I believe that Control Logic might be sufficient for my need. If it is not, I will certainly explorer the move possibilities.
  Like • Show 0 Likes0
  Actions

How to flag edit-box properties as read-only after transition

Outcomes

Related Content

Recommended Content