Validation Rule logic blocks

No-Code Platform
1

Hey, I am trying to use the Inspection Profile Manager and see that is connected to logic underneath the hood but contains nothing at the moment.

Do we need to create our own logic and how would we validate broken references for interest sake.

2

Any feedback on the above topic? I need to understand if we can just run the profile without adding anything to that logic block under the hood, or if we need to cater for it by adding some logic of our own.

3

Hey Stefanus, you don’t need to create any logic to use the Inspection Profile Manager - those logic blocks are built into the platform. In order to use them all you need to do is run the “Run Inspection Profile” row action and provide it an Inspection Object Set Definition that defines which metadata you want to inspect.

1 Like
4

Ok thanks. Another question. How do you envisage the usage of those logic blocks?

1 Like
5

In the future there may be an opportunity to use your own LogicBlocks to validate metadata, but today that is not supported. The only rules available are those that shipped with the original inspection feature. Those rules are backed by LogicBlocks, work generically for all metadata types, and check if any of the table lookups on the records point to metadata that no longer exists or is an incompatible family relative to the original record. Let me know if I misunderstood your question

1 Like
6

Thanks Ethan. I would still like to understand how we would use this logic block to validate metadata. Is there new actions coming to LogicBlocks to allow for validation against certain metadata types?