RELATED IDEAS
Completeness calculation ignore fieldset specific fields
Please, fill in the below fields to enable the processing of your idea.
Who would benefit? |
Product data managers / inriver Enrich users |
What impact would it make? |
See context |
How should it work? |
The completeness rule calculation should take in account whether fields are actually part of the entity with the selected fieldset. When that entity has a fieldset active where some of the completeness rules apply on, it should calculate them. BUT, when an entity has no OR a different fieldset and some completeness rules DON't apply, it should ignore this in the calculation. |
Why is it needed? |
Completeness is now not usable with fields that are linked to a fieldset |
Additional feedback, background or context:
At the moment Completeness rules can be configured on all Fields (FieldTypes), for example with a 'Field not empty' type rule. Fieldsets will hide/show specific Fields. When a completeness rule uses a Field that is within a Fieldset, this Field will always be empty unless you select that Fieldset and fill it in. The completeness percentage will never reach 100% if you include fieldset specific fields in completeness rules and thus will never be complete.
The consequence is that fieldset specific fields are just not usable in completeness, by my opinion totally overshooting that target of completeness. The fieldset specific fields are generally more meaningfull and more applicable for articles.
If inriver completeness will ignore fieldset specific fields, we could configure them and improve workflows with 'Completed' groups way better and thus improving the usability with a huge step.
I have already implemented this as an extension. My experience is that it cannot be made performant enough on entities which have a large number of fields (100+). Remember, this will run EVERY save!
The mk2 of the solution was so have a scheduled extension to do the calculation and save the result into an integer field on the entity (this has a nice side effect that it is "queryable" and you can see history). I then created a new CVL extension that takes this integer field and assigns the completeness percentage.