Our organization maintains a parcel fabric of about 2.4 million parcels. We have strict business logic we adhere to, which we enforce via a number of validation style attribute rules. We have also implemented a custom reconcile and post tool to ensure mappers have successfully validated all rules prior to posting. Since our business logic is so critical to our data quality, we also want to ensure none of the mappers accidentally edit default directly, so we have a constraint attribute rule in place that prevents this:
However, we have discovered the evaluate rules process does not appear to honour this attribute rule, and mappers can accidentally evaluate rules against the default version of the database. In our case, this ended up crashing our entire production service. Typically, we would run evaluate rules only on features modified in this version - but in the case, since the mapper was accidentally running evaluate rules against default, there were no features modified in this version, so the entire database was evaluated (and it was goodnight on our service).
We would like to request that the evaluate rules process honour the constraint rule to prevent editing against default.
