Process panel - mandatory flag is not respected

[teosarca]

Test case:

• try running a process which have mandatory parameters

NOTE:

• mandatory parameters are NOT marked in a way, so user have no idea what's mandatory and what not
• mandatory parameters are not validated so basically when user presses "Start" it relies on backend to throw an exception because one of the mandatory params were not set

e.g.

[damianprzygodzki]

Mandatory fields are marked in a way. How do you want to marked them? We assumed that mandatory fields have blue outline.

[teosarca]

ahhh, forgot... but on the other hand seems that it wan't intuitive for me :))

Ok, we have just to solve the second part. How shall we deal with mandatory fields.
Atm, frontend it's just asking the backend the start the process and the backend throws an exception.
But from UX it would be nice if the user would notified in a nicer way...
wdyt?

[damianprzygodzki]

1. I can just avoid to sending call if all mandatory fields are not filled (that's how we handle now most of mandatory fields) - but there won't be notification.
2. Displaying notifications with errors is one possible way for now to display errors in forms/widgets because we never talked about handling errors by widgets.

[teosarca]

@damianprzygodzki you are right. I think we shall improve the backend as described here: metasfresh/metasfresh-webui-api-legacy#88

wdyt?

[teosarca]

UPDATE: for any field we are providing now 2 more properties:

• valid : true | false
• validReason: "string" // reason why field is not valid

[damianprzygodzki]

#253 Check this related issue, and i think we should apply it for every widget (i am describing this particular case). Before implementation, we need assumption here, or there.

[cadavre]

@teosarca can you please verify if this issue is still up-to-date?

[teosarca]

quick checked, the "validStatus" is still not considered.

[teosarca]

not sure if the backend shall provide something more....

[cadavre]

AFAIK "when user presses "Start" it relies on backend to throw an exception" is what we all agreed on as front-end is not made for data validation – backend is responsible for it. In this perspective this issue is not valid.

[teosarca]

yup, ofc, the backend is validating it. let's close it for now.