Skip to main content
B
BF_1381190014-Alexandrite
14-Alexandrite
October 20, 2025
Solved

Date Selection

  • October 20, 2025
  • 2 replies
  • 559 views

Version: Windchill 13.0

 

Use Case: I would like to be able to prevent users in my Windchill instance to pick dates in the future when populating a timestamp attribute.


Description:

Can this be achieved?

Best answer by joe_morton

It sounds then what you might need would be some Listener and custom code. You could have the Listener run when the part instance is created, and validate that the date is not in the future. I think the out of the box constraints only allow for setting a static date range.

2 replies

avillanueva
23-Emerald I
avillanueva23-Emerald I
23-Emerald I
October 22, 2025

If this is in a workflow, yes this can be done but you need a check step after or you can add code to the transition section of the workflow task to do a date compare. Is there a particular UI entry section that you are looking to validate? There is also creating a validator if its a different part of the UI, not workflow related.

    B
    BF_1381190014-AlexandriteAuthor
    14-Alexandrite
    October 28, 2025

    Hi. I am looking to prevent users from picking a date in the future when populating an attribute of a part instance, for example. So, I don't believe this is workflow related.

    joe_morton
    18-Opal
    joe_morton18-OpalAnswer
    18-Opal
    November 12, 2025

    It sounds then what you might need would be some Listener and custom code. You could have the Listener run when the part instance is created, and validate that the date is not in the future. I think the out of the box constraints only allow for setting a static date range.

    A
    anursinghCommunity Manager
    Community Moderator
    October 27, 2025

    Hi @BF_13811900,

     

    I wanted to see if you got the help you needed.

    If so, please mark the appropriate reply as the Accepted Solution. It will help other members who may have the same question.
    Of course, if you have more to share on your issue, please pursue the conversation. 

     

    Thanks,
    Anurag 

    Terms & ConditionsCookie settingsAccessibility statement