Skip to main content
M
MarcoB904-Participant
4-Participant
October 8, 2024
Solved

Editable DATE parameter linked to PTC_WM_CREATED_ON

  • October 8, 2024
  • 2 replies
  • 1294 views

Hello everyone,

I am trying to create a DATE parameter for my startparts, which at the creation of a new part is linked to the parameter PTC_WM_WM_CREATED_ON by a relation, but which can be modified later, if necessary. This, avoiding that users have to modify or remove relations.

 

With these relations the DATA parameter is editable from the day after creation, but I would like to use something better:

 

IF PTC_WM_CREATED_ON == PTC_WM_MODIFIED_ON
DATE=PTC_WM_CREATED_ON
ENDIF

 

I don’t want to be forced to wait a day, but I don’t know if there is another way to do that, using only relations and existing parameters.

Any ideas?

 

Thank you

Marco

 

p.s.

I'm using CREO 8.0.9.0 and Windchill 12.0.2.10 and the date format in Windchill is set on dd-mm-yyyy (08-10-2024)

 

 

Best answer by pausob

Hmm, I am not sure I would do this in the way you describe.

 

I suppose the logic would work if your Windchill system was configured to have the date that also includes the time stamp, which is the case in our system.

 

However, even then there seem to be some flakey issues with the above relation.   For example, a quick test reveals that even though PTC_WM_CREATED_ON == PTC_WM_MODIFIED_ON evaluates to NO, the DATE parameter remains locked and uneditable:

pausob_0-1728408863193.png

Oh, wait, upon making some more changes and uploading the test file again, the DATE parameter became unlocked:

pausob_1-1728408985265.png

So this is troubling and anyway, this won't work when Windchill is configured such that PTC_WM_... dates don't include the time stamp.

 

 

So I would consider having a YES/NO parameter called USE_CUSTOM_DATE, by default set to NO and the relation be:

IF USE_CUSTOM_DATE == NO
 DATE = PTC_WM_CREATED_ON
ENDIF

 

pausob_3-1728409731846.png

 

 

2 replies

M
MartinHanak24-Ruby III
24-Ruby III
October 8, 2024

Hi,

I guess that no solution exists OOTB.

Maybe some Creo -OR- Windchill customization provides requested solution. Please ask PTC Support.

    P
    19-Tanzanite
    pausob19-TanzaniteAnswer
    19-Tanzanite
    October 8, 2024

    Hmm, I am not sure I would do this in the way you describe.

     

    I suppose the logic would work if your Windchill system was configured to have the date that also includes the time stamp, which is the case in our system.

     

    However, even then there seem to be some flakey issues with the above relation.   For example, a quick test reveals that even though PTC_WM_CREATED_ON == PTC_WM_MODIFIED_ON evaluates to NO, the DATE parameter remains locked and uneditable:

    pausob_0-1728408863193.png

    Oh, wait, upon making some more changes and uploading the test file again, the DATE parameter became unlocked:

    pausob_1-1728408985265.png

    So this is troubling and anyway, this won't work when Windchill is configured such that PTC_WM_... dates don't include the time stamp.

     

     

    So I would consider having a YES/NO parameter called USE_CUSTOM_DATE, by default set to NO and the relation be:

    IF USE_CUSTOM_DATE == NO
 DATE = PTC_WM_CREATED_ON
ENDIF

     

    pausob_3-1728409731846.png

     

     

      M
      MarcoB904-ParticipantAuthor
      4-Participant
      October 10, 2024

      Yes you are right, I tested my relation and does not work well. It only works if I check-in the part from the day after creation. Till that, rightly, PTC_WM_CREATED_ON is equal to PTC_WM_MODIFIED_ON. Too unpractical.
      Your proposal is a good idea, although I was looking for a more "automatic" method, but it seems not to be manageable only with relations.

       

      Thank you

      Terms & ConditionsCookie settingsAccessibility statement