A generic note would do, even though it leaves a lot of cognitive effort for the user if for instance we say:
"Form cannot be shared as a webform because it is not published, or it is a monitoring form or because it contains a signature, geoshape or a caddisfly question type or a repeat question group."
It leaves the user with a lot of stuff to process, but since we are actually validating each of these flags automagically, we know the flag that causes a disabling of the action and a direct messaging would simplify the context for Salim and also resolving it, if he decides to do so..
Alternatively, we could bunch up the question type and group message - leaving Salim to figure out which of those flags applies - and have two more direct messaging 1) form type and 2) publishing..
A generic note would do, even though it leaves a lot of cognitive effort for the user if for instance we say:
"Form cannot be shared as a webform because it is not published, or it is a monitoring form or because it contains a signature, geoshape or a caddisfly question type or a repeat question group."
It leaves the user with a lot of stuff to process, but since we are actually validating each of these flags automagically, we know the flag that causes a disabling of the action and a direct messaging would simplify the context for Salim and also resolving it, if he decides to do so..
Alternatively, we could bunch up the question type and group message - leaving Salim to figure out which of those flags applies - and have two more direct messaging 1) form type and 2) publishing..
Originally posted by @Kiarii in https://github.com/akvo/akvo-flow/issues/3145#issuecomment-630657330