[
https://issues.apache.org/jira/browse/OFBIZ-13257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17983653#comment-17983653
]
Jacopo Cappellato commented on OFBIZ-13257:
-------------------------------------------
This is simply a bug. According to the EditCalendarExceptionDay.ftl
directives, when a record is selected for update, it should display a new
update form before the Add form, that is supposed to be always displayed.
I suspect that the root cause of the error is due to the record selection
constraint containing a date, that is not correctly parsed by the UI. This is a
general issue that is affecting several other screens in the system.
So, I don't think your design proposal applies to this case, since it is just a
bug.
Please, also notice that wrong labels are used, i.e.,
PageTitleEditCalendarExceptionWeek PageTitleAddCalendarExceptionWeek
instead of
PageTitleEditCalendarExceptionDay PageTitleAddCalendarExceptionDay
> The "Select" button in the Calendar Exception Day section functions as an
> edit action but lacks appropriate context and UI feedback, leading to user
> confusion.
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: OFBIZ-13257
> URL: https://issues.apache.org/jira/browse/OFBIZ-13257
> Project: OFBiz
> Issue Type: Improvement
> Components: manufacturing
> Affects Versions: Upcoming Branch
> Reporter: Yashwant Dhakad
> Priority: Trivial
>
> *Description*
> In the Calendar tab of the Manufacturing module, users can add exception days
> using the "Add Calendar Exception Week" form. Once added, the exception days
> appear in a list above the form, each entry displaying two buttons: Select
> and Delete.
> When the Select button is clicked, the corresponding exception day’s details
> populate the form fields. While this allows users to modify existing entries,
> the rest of the form remains unchanged — particularly:
> * The button label remains "Add", not indicating any change in mode.
> * There is no visual indication that the user is now editing an existing
> record instead of creating a new one.
> This lack of feedback creates ambiguity, especially for new users, as the
> system does not clearly distinguish between "add" and "edit" operations.
> *Proposed Improvements*
> To enhance usability and align the interface with user expectations, the
> following changes are recommended:
> Rename the Select button to Edit to more accurately reflect its function.
> When Edit is clicked:
> * Switch the form into edit mode.
> * Replace the "Add" button with an Update button.
> * Optionally, introduce visual cues (e.g., form highlighting or a message) to
> indicate that the form is now in edit mode.
> *Benefits*
> * Reduces user confusion by clearly distinguishing between adding and editing
> actions.
> * Improves consistency in UI behavior and terminology.
> * Enhances overall user experience, particularly in scenarios with frequent
> calendar configuration changes.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
