You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ofbiz.apache.org by "Jacopo Cappellato (JIRA)" <ji...@apache.org> on 2008/04/10 11:00:05 UTC

[jira] Commented: (OFBIZ-1440) UI: Review/Improve/Cleanup the /accounting/control/EditAcctgTrans screen

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

Jacopo Cappellato commented on OFBIZ-1440:
------------------------------------------

Most, if not all, of the issues listed in my previous comments have been fixed, except for this one:

"I think it is time to prevent the ability to modify an accounting transaction that is posted. 
Instead of adding a bunch of use-when in the form definition's fields, I'd suggest that we create two new forms and we add a <section><condition>... area to the screen definition to include the editable or not editable ones according to the isPosted flag. "

It would be great to address this last issue and then close the task.

> UI: Review/Improve/Cleanup the /accounting/control/EditAcctgTrans screen
> ------------------------------------------------------------------------
>
>                 Key: OFBIZ-1440
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-1440
>             Project: OFBiz
>          Issue Type: Sub-task
>          Components: accounting
>            Reporter: Jacopo Cappellato
>            Assignee: Ashish Vijaywargiya
>         Attachments: CreateAcctgTrans.patch
>
>
> Review/Improve/Cleanup the /accounting/control/EditAcctgTrans screen: you can reach it from Accounting>General Ledger>Accounting>Accounting Transactions>then perform a search and click one of the accctgTransId
> - add more fields (from the AcctgTrans entity) to the form at the top of the screen
> - the form at the top of the screen, and the underlying updateAcctgTrans service, always allows to edit the fields of the AcctgTrans entity (even if the transactions are posted): should we limit this (both at the ui and service level)?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.