[
https://issues.apache.org/jira/browse/OFBIZ-1440?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12587879#action_12587879
]
Jacopo Cappellato commented on OFBIZ-1440:
------------------------------------------
David,
thanks, this is an important point actually.
I've checked the code and unfortunately the flag is not checked by the
underlying services.
For this reason, in order to complete the task, we have also to add the logic
(and return an error if the transaction has been already posted:
AcctgTrans.isPosted==Y) to the following services:
- updateAcctgTrans
- deleteAcctgTrans
- createAcctgTransEntry
- updateAcctgTransEntry
- deleteAcctgTransEntry
- completeAcctgTransEntries
Jacopo
> 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.
