Skip to main content
A
ASodeik1-Visitor
1-Visitor
October 18, 2019
Question

Viewing rule conflicts in a big structure - Windchill 11 M010

  • October 18, 2019
  • 2 replies
  • 2967 views

We have a number of Business Rules in place - which work fine. But the rule conflict tells the user to solve it on the top level part only. But not specifically where in the structure the conflict is. Our structures are huge. 

 

Any idea or experience how to point the user to the conflict location in a huge structure?

 

thanks in advance    Andreas

2 replies

J
jmomber12-Amethyst
12-Amethyst
December 2, 2019

Are they custom business rules? We have a lot of them as well, and I give the user the information about which part is actually the problem in the error message.

 

Example:

@RBEntry("The component {0} has a blank Find Number value.")
public static final String FIND_NUMBER_ERROR_NULL = "FIND_NUMBER_ERROR_NULL";

A
ASodeik1-VisitorAuthor
1-Visitor
December 3, 2019

Thanks for your answer - I will forward it to our developer.

What is filling the find number value in your setup?

thanks in advance Andreas

J
jmomber12-Amethyst
12-Amethyst
December 3, 2019

We actually made a custom attribute and don't use the OOTB findNumber attribute. Our attribute is a String value. Was that your question? 🙂

B
BjoernRueegg17-Peridot
17-Peridot
December 4, 2019

The message which is being displayed to the user can be customized. There are multiple possibilities and it depends on how far the programmer goes. He can stop at the first error and shows only a general error. Or he can identify the component which does make troubles or he even can run thru the complete structure and collects all the components which are not correct and shows all the errors at once.

    Terms & ConditionsCookie settingsAccessibility statement