[jira] [Comment Edited] (OFBIZ-5559) Usability improvement for management of manual Gl transactions

[Nicolas Malin (Jira)]

    [ https://issues.apache.org/jira/browse/OFBIZ-5559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13944030#comment-13944030 ]

Pierre Smits edited comment on OFBIZ-5559 at 3/22/14 11:34 AM:
---------------------------------------------------------------

Testing the patch generated following results:

*1. display GlAccount tree (issue description aspect #1)*
The tree is shown sorted on accountCode in stead of glAccountId as described. Expanding the tree
When the creation of a new gl account succeeded, the screen returned shows the data entered in the edit GL part of the screen, but Gl Account Id showed with ‘Could not find GlAccount with ID []’.

Also, the first click on the tree (after a creation of a new glAccount) to expand the tree doesn’t respond with expanding the tree. It requires an additional click. Whereas when updating an existing glAccount it performs on the first click by expanding the tree.

Otherwise the patch segment functioned as stated in description aspect #1

But, now the sort order of the chart of accounts in Global GL Settings is different than the sort order of the tree (glAccountId vs accountCode).

*2. Displaying the transaction description (issue description aspect #2)*
Content of description field is shown in the overview. However, it can't be used in the search criteria. That would be another improvement.

*3. Create an accounting transaction (issue description aspect #3)*
When creating a new Accounting Transaction and adding some content to the description field still doesn't get copied to the description field in the transaction entry form.
Upon creation of a new transaction entry the description in the transaction entries overview of the transaction is not editable/updatable, while other fields are.
The field format of the description of a transaction entry is not the same as in other applications /forms (there the field is typed as text-area).



was (Author: pfm.smits):
Testing the patch generated following results:

* 1. display GlAccount tree (issue description aspect #1) *
The tree is shown sorted on accountCode in stead of glAccountId as described. Expanding the tree
When the creation of a new gl account succeeded, the screen returned shows the data entered in the edit GL part of the screen, but Gl Account Id showed with ‘Could not find GlAccount with ID []’.

Also, the first click on the tree (after a creation of a new glAccount) to expand the tree doesn’t respond with expanding the tree. It requires an additional click. Whereas when updating an existing glAccount it performs on the first click by expanding the tree.

Otherwise the patch segment functioned as stated in description aspect #1

But, now the sort order of the chart of accounts in Global GL Settings is different than the sort order of the tree (glAccountId vs accountCode).

* 2. Displaying the transaction description (issue description aspect #2) *
Content of description field is shown in the overview. However, it can't be used in the search criteria. That would be another improvement.

* 3. Create an accounting transaction (issue description aspect #3) *
When creating a new Accounting Transaction and adding some content to the description field still doesn't get copied to the description field in the transaction entry form.
Upon creation of a new transaction entry the description in the transaction entries overview of the transaction is not editable/updatable, while other fields are.
The field format of the description of a transaction entry is not the same as in other applications /forms (there the field is typed as text-area).

> Usability improvement for management of manual Gl transactions
> --------------------------------------------------------------
>
>                 Key: OFBIZ-5559
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-5559
>             Project: OFBiz
>          Issue Type: Improvement
>          Components: accounting
>    Affects Versions: SVN trunk
>            Reporter: Anahita Goljahani
>            Priority: Minor
>         Attachments: accounting.patch
>
>
> I have recently tried to use OFBiz to manually enter GL transactions from the UI. I found some usability issues that I have fixed in the attached patch. The patch contains some basic modifications that render the manual management of transactions more user-friendly.  
> The main modifications are as follows.
> 1.  In Applications -> Accounting -> Global GL Settings -> CHART OF ACCOUNTS -> NAVIGATE ACCOUNTS:
> -  the patch visualizes the "Account Code" instead of the "Gl Account Id" next to the nodes of the tree in the "Navigate Accounts" form. The reason is that the "Account Code" is typically defined and used by accountants, whereas the "Gl Account Id" is an internal key. This is also in line with other screens in the OFBiz Accounting application;
> - the patch renders the "Gl Account Id" field not editable and leaves to the software the task of generating a unique Id for the account;
>    
> - the patch adds the default value "Not Applicable" for "Gl Account Type Id" and "Gl Resource Type Id" in the "Edit GL Account" form. The reason is that the setting of "Gl Account Type Id" is not influential when accounting  transactions  are manually inserted and "Gl Resource Type Id"  is not applicable in some of the transactions.
> 2.  In Applications -> Accounting ->Organization GL Settings -> ACCOUNTING (of any organization)-> ACCOUNTING TRANSACTIONS the patch adds the DESCRIPTION field to the list of transactions that is displayed when the "Search" button is pressed in the "Accounting Transactions" form.  It helps to quickly understand what the transactions in the list are about.
> 3.  In Applications -> Accounting ->Organization GL Settings -> ACCOUNTING (of any organization)-> ACCOUNTING TRANSACTIONS -> "Create an Accounting Transaction" button, the patch adds the default value "Not Applicable"  to the field "Acctg Trans Type". The reason is that the value of "Acctg Trans Type" is not influential when transactions are entered manually. Moreover, when the button "Create" is pressed in the "Create an Accounting Transaction", the "Description" of the transaction is no more automatically copied in the "Description" field of the form "Add Transaction Entry". The reason is that repeating by default the transaction's description in every entry  is redundant and not very useful. Entries' "Description" should be used to insert additional information.  

--
This message was sent by Atlassian JIRA
(v6.2#6252)