Quick Form - To support data entry faster for large documents using keyboard only

Description

This ticket is to contribute Quick Data Entry features in iDempiere project. The feature is described at https://logilite.com/idempiere-quick-entry-form/

Goal of this feature is to allow user to enter larges sale order or invoice with use of keyboard only.
Quick Form fields are system admin configurable to avoid performance issue caused by inappropriate usage of this features. The toolbar button to launch quick entry form is enabled only of there is fields configured to have quick entry. The form support all call outs configured on AD_Tab and display logic features.

Environment

None

Activity

Show:
Heng Sin Low
April 6, 2020, 2:17 AM
Edited

There are some code added to SessionManager apparently to prevent the opening of "already open" quick entry form. Since the quick entry form is open in highlighted mode (i.e when it is open, it is the only active window), I can't see why this is needed at all.

, can you please clarify on this ? If is it not needed, it should be removed.

Heng Sin Low
April 6, 2020, 2:36 AM

Hi , there are some comments in the code referring to “parent and child quick entry form” feature (seems abstractadwindowcontent.set/getCurrQGV is created for that) but from reading the code, it seems that’s not implemented yet. Can you please clarify on that as well ?

thanks,

Low

Deepak Pansheriya
April 6, 2020, 5:22 AM

we support short cut keys. When user use short cut key while Quick Form dialog is open, it was re opening dialog. So avoid same, we have added that logic. Shift + F2 is used to open current tab as quick form, ctrl + F2 used to open child tab of current tab as quick form. I missed documenting short cut key, So let me add it.

Heng Sin Low
April 6, 2020, 6:58 AM

Hi ,

The code to avoid reopen shouldn't goes to SessionManager as it isn't a session scope thing. It is local to a window and should be managed at the window level, i.e it should be manged at AbstractADWindowContent as an instance variable instead.

For the current and child tab handling - do you means to maintain link between the two quick form/tab or you just want to close the previous quick form/tab that's still open ? If later is the case here, it should be the same as above - it should be straightforward if the open quick form is maintain as instance variable at AbstractADWindowContent.

Regards,
Low

Deepak Pansheriya
May 8, 2020, 8:18 AM

Pull request created with suggestion from carlos as well as hengsin.

Assignee

Deepak Pansheriya

Reporter

Deepak Pansheriya

Labels

None

Tested By

None

Components

Fix versions

Priority

Major
Configure