Skip to main content
V
Vishwa_RADDI10-Marble
10-Marble
June 10, 2024
Question

How to set the conflict description message for implementing rename using custom listener

  • June 10, 2024
  • 2 replies
  • 3188 views

Version: Windchill 12.1

 

Use Case: I have written custom listener will use the event "IdentityServiceEvent.PRE_CHANGE_IDENTITY" for if WTPart New Number is NOT 10-digit validation and not able to dispay the conflict description message in Event Console


Description:

I have written custom listener will use the event "IdentityServiceEvent.PRE_CHANGE_IDENTITY" for if WTPart New Number is NOT 10-digit validation and not able to dispay the conflict description message in Event Console

2 replies

D
18-Opal
d_graham18-Opal
18-Opal
June 11, 2024

@Vishwa_RADDI ,

I saw your post and it seemed very doable.

 

I renumbered a WTPart to be 6 characters long.

d_graham_0-1718105112771.png

As expected, I get a failure and the error description is exactly what I coded.

Seems to work to your spec, unless I'm misunderstand your post.

d_graham_2-1718105332093.png

 

David

windchill.developer@yahoo.com 

 

 

V
Vishwa_RADDI10-MarbleAuthor
10-Marble
June 11, 2024

Hi David,

 

how do you set this custom message on Conflict event console? I have tried using WTException(new WTMessage); and just throwing an exception its not working. let me know how do we set?

 

Thanks,

Vishvanatha

 

HelesicPetr
22-Sapphire II
HelesicPetr22-Sapphire II
22-Sapphire II
June 12, 2024

Hi @Vishwa_RADDI 

It is more complicated then just throw WTException.

You should create object a ConflictException with a ConflictElement that contains a ResolutionType and a ConflictType with your message to a user. 

 

I did similar exception for deleting WTPart that is linked to a process plan. User has a option to repeat and finish deletion or nothing else. 

PetrH

M
marshall_brock10-Marble
10-Marble
August 27, 2025

Hi @Vishwa_RADDI 

 

Were you ever able to accomplish this? I would like to do something similar but the responses you got here seem to be deliberately obscure for some reason. I posted about it here in hopes of finding a solution.

 

Thanks,

Marshall

Terms & ConditionsCookie settingsAccessibility statement