You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, entering GR-LotResult-ReceivedSubmissions is unnecessarily complicated. In addition, the rules for input, which are in the description, cannot be validated in a practical way.
My suggestion for this group is to simply make all entries in the code list into a separate field. For example, the number of requests to participate received could be entered in BT-759(a). The number of tenders received in BT-759(b), the number of tenders received electronically in BT-759(c), etc.
With this change, the user could simply enter the number of respective submissions without having to add an element each time and select the corresponding value from the code list. In addition, the mandatory fields could simply be assigned to the corresponding subtypes.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Currently, entering GR-LotResult-ReceivedSubmissions is unnecessarily complicated. In addition, the rules for input, which are in the description, cannot be validated in a practical way.
My suggestion for this group is to simply make all entries in the code list into a separate field. For example, the number of requests to participate received could be entered in BT-759(a). The number of tenders received in BT-759(b), the number of tenders received electronically in BT-759(c), etc.
With this change, the user could simply enter the number of respective submissions without having to add an element each time and select the corresponding value from the code list. In addition, the mandatory fields could simply be assigned to the corresponding subtypes.
Beta Was this translation helpful? Give feedback.
All reactions