When you set up Completeness on an EntityType you can have different approaches.

I’ve taken a very simple example, a Brand entity that needs a unique identifier and an image. It can also have a description but that is not needed for it to be published online.

Only setup mandatory fields

You can configure the Completness for the fields that is needed and discard all others, Description in my example.

You will be able to use this Query editor to get all complete brands that lacks description.

Setup different Completeness Groups

You can also create different Completeness Groups for mandatory fields and for other fields.

You can also give them different weights if you like. 

You can weight “Web – Extended” with 0 and it will still work.

Since we can check different Completeness Groups in Query Editor you can search like this.

You can only search for one Completeness Group, but you can also Search for the Completess Value (score).

Setup 0 weighted rules

You can combined "mandatory" and "non-mandatory" fields in the same Completeness Group, by weighting the individual rules. 

In the image above "Has description" is incomplete, but the Group is still considered as Complete. This is due to that the Rule "Has description" is weighted to 0.

Completeness on FieldSets fields

If you don't have to many FieldSets you can use completeness for fields in FieldSets. 

In my example below I have a FieldSet called "Knife" and for all knifes a would like to have some fields set. 

I have weighted all "FieldSet" Completeness Groups to 0, but their rules are weighted as normal. 

With this approach you can search for incomplete Knifes with a Query like this. 

Disclaimer! If you have to many FieldSets this approach might not be the best from a performance perspective. 

Feel free to share other scenarios or other ways to play around with completeness.