sys:incomplete aspect

[dozyarmadillo]

Can someone (ideally from Alfresco Engineering) tell me what the purpose of the 'sys:incomplete' aspect is?

I could be wrong but it appears that the aspect is automatically applied to content at creation time (but not at specialise-type time) if values have not been supplied for mandatory properties of a node.

I would like to highlight documents that are missing mandatory metadata through a custom indicator (using org.alfresco.web.evaluator.HasAspectEvaluator for aspect 'sys:incomplete'). Consequently I would like to understand what 'sys:incomplete' is used for and why it isnt applied at specialise-type time.

Many thanks

Mark

BTW apologies for the double post - it originally asked this question at https://forums.alfresco.com/forum/end-user-discussions/alfresco-explorer/mandatory-properties-and-sy....

[afaust]

Hello,

I am not from Alfresco Engineering but as a partner have a decent amount of insight into the architecture / code of Alfresco. It is indeed the case that the 'sys:incomplete' aspect is not applied if you "only" change the type of a node. The relevant policy (IncompleteNodeTagger) is only triggered by node creation, property updates, aspect updates, creation and deletion of (child) associations. Unfortunately, changing the type is - as far as I see at the moment - the only change to an object that does not trigger one of these policies (apart from deletion, which is irrelevant for this use case).

I suppose this is not an intentional lack of policy coverage and personally would classify it as a bug against the documentation. Suggest you raise a JIRA to have that clarified.

Regards
Axel

[mrogers]

Yes its rather obscure and old functionality and I agree changeType has possibly a bug…  It is certainly worth a debate or investigation.

The purpose is to support UI use cases where you must first create a node and then add the property values in a subsequent transaction.  Without this back-door you cant create a node with mandatory properties since you can't display the form to get the properties without a node of the correct type already existing … which you can't create since it lacks mandatory properties.

[dozyarmadillo]

Thanks for the replies. I've raised a JIRA.

[jservajean]

Hi,

It turns out appareantly share search UI (4.2.f community + SOLR) doen't find nodes (from avanced search custom form) if those are "incomplete", even on auto-extracted properties like "name".
As the custom mandatory properties are set, the same search works !

Any idea if this is a normal behaviour (sounds weird) ?

Any idea of how to bypass it ?

thx

[mrogers]

Yes its expected behaviour.    You shouldn't be able to do anything with an incomplete node other than set its properties (so its complete) or delete it.    

There's no point in being able to search for it.