Property Checker feedback

Speckle Help
,
1

  1. For Property checker - Can we have an “OR” based rule?

  2. In Property checker rules - we have a match pattern rule - can you explain how it works? (For example, pattern should " Initiator company-Discipline code-Description: XXX-X-Description")

2

IS LIKE checks whether a text value follows a pattern that you specify. It is useful for enforcing naming conventions and for structuring code exactly as you describe. It is an SQL-style regular expression pattern match.

You write a pattern using % as a wildcard, where % means “anything can go here”.

A few important points up front:

  • % matches any number of characters
  • The pattern must describe the whole value, not just a fragment
  • Matching is not case-sensitive

In your example, if you expect values like: ABC-A-Core walls
(where the format is InitiatorCompany-DisciplineCode-Description)

You can use this pattern: [A-Z]{3}-[A-Z]-%

Read it as:

  • three capital letters
  • a hyphen
  • one capital letter
  • a hyphen
  • then anything else as the description

Useful patterns

  • %
    accepts any value
  • ABC-%
    accepts anything that starts with ABC-
  • %-A-%
    accepts anything that contains -A- somewhere in the text

One thing to be aware of

After % is expanded, the pattern is evaluated as a normal regular expression. That means characters like ., (, ), [, and ] are treated as special pattern characters rather than as literal text.

1 Like
3

We can certainly look at OR-style rules as part of a broader review of filtering. That said, OR is one of those deceptively simple ideas that often becomes confusing once it is expressed in a rule-based UI.

People tend to think about OR in a very local, conversational way, while the underlying logic applies globally. As soon as AND and OR are mixed, questions of grouping and precedence appear, and the results often stop matching what users expect. This is something we have seen cause years of frustration in other tools.

For now, Property Checker stays intentionally strict and predictable. All rules are evaluated using AND logic.

If you need OR-like behaviour today, use “is one of” on a single property. This lets a rule pass when the property matches any value in a list. For example:

Discipline is one of A, S

This behaves like an OR for that property, and can still be combined with other rules using AND.

OR logic across different properties, or grouped combinations of AND and OR, is not supported in the current UI.

5

Thank you.

The main objective of this request is to identify elements that do not have values for mandatory parameters such as Classification Code, IFC Name, and Mark Value. Typically, we maintain a list of parameters that must be filled for all elements.

The rule should be defined as follows:

  • FAIL if any one of these parameters (Uniclass, NRM, Discipline Code) is missing a value.

Please note that we cannot have multiple widgets for parameter checking within a single dashboard.

6

We are working on a more extensive Model Validation suite for Intelligence as I write this. I would be happy to loop you in when it’s available for testing.

cc: @chuck

In the meantime, while it isn’t ideal for what you are asking, others are doing just that, with multiple simple Property Checker widgets in play at once. They can interplay to drill down into results.

1 Like
7

Hey, did something change with the Regular expression? I can’t manage to make it work even with the simplest pattern.

8

This was amended a little while ago

rather than trying to support multiple ways to define patterns and try and detect them, a regex will require wrapping in / JS style.

We have docs that cover this and the wildcard pattern matching Filters - Speckle Docs

9

Thanks! Missed that

1 Like
10

This topic was automatically closed after 7 days. New replies are no longer allowed.