-
Notifications
You must be signed in to change notification settings - Fork 105
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
(proposal) Underlying EDITED
flag on financial entities
#2047
Labels
Comments
I'll take this one. |
jniles
added a commit
to jniles/bhima
that referenced
this issue
Nov 5, 2017
This commit implements the EDITED flag on records of transactions that have been modified via the posting journal edit tool. This signals the user that the transaction has been edited and the data might be out of date. Closes Third-Culture-Software#2047.
jniles
added a commit
to jniles/bhima
that referenced
this issue
Nov 5, 2017
This commit adds the edited flag at the top of the record dropdowns for cash, vouchers, and invoices. The icon and text denote that the record has been modified at the Journal and the receipt is likely out of date. Closes Third-Culture-Software#2047.
jniles
added a commit
to jniles/bhima
that referenced
this issue
Nov 9, 2017
This commit implements the EDITED flag on records of transactions that have been modified via the posting journal edit tool. This signals the user that the transaction has been edited and the data might be out of date. Closes Third-Culture-Software#2047.
jniles
added a commit
to jniles/bhima
that referenced
this issue
Nov 9, 2017
This commit adds the edited flag at the top of the record dropdowns for cash, vouchers, and invoices. The icon and text denote that the record has been modified at the Journal and the receipt is likely out of date. Closes Third-Culture-Software#2047.
jniles
added a commit
to jniles/bhima
that referenced
this issue
Nov 11, 2017
This commit implements the EDITED flag on records of transactions that have been modified via the posting journal edit tool. This signals the user that the transaction has been edited and the data might be out of date. Closes Third-Culture-Software#2047.
jniles
added a commit
to jniles/bhima
that referenced
this issue
Nov 11, 2017
This commit adds the edited flag at the top of the record dropdowns for cash, vouchers, and invoices. The icon and text denote that the record has been modified at the Journal and the receipt is likely out of date. Closes Third-Culture-Software#2047.
jniles
added a commit
to jniles/bhima
that referenced
this issue
Nov 16, 2017
This commit implements the EDITED flag on records of transactions that have been modified via the posting journal edit tool. This signals the user that the transaction has been edited and the data might be out of date. Closes Third-Culture-Software#2047.
jniles
added a commit
to jniles/bhima
that referenced
this issue
Nov 16, 2017
This commit adds the edited flag at the top of the record dropdowns for cash, vouchers, and invoices. The icon and text denote that the record has been modified at the Journal and the receipt is likely out of date. Closes Third-Culture-Software#2047.
jniles
added a commit
to jniles/bhima
that referenced
this issue
Nov 17, 2017
This commit implements the EDITED flag on records of transactions that have been modified via the posting journal edit tool. This signals the user that the transaction has been edited and the data might be out of date. Closes Third-Culture-Software#2047.
jniles
added a commit
to jniles/bhima
that referenced
this issue
Nov 17, 2017
This commit adds the edited flag at the top of the record dropdowns for cash, vouchers, and invoices. The icon and text denote that the record has been modified at the Journal and the receipt is likely out of date. Closes Third-Culture-Software#2047.
bors bot
added a commit
that referenced
this issue
Nov 17, 2017
2276: Feat: edit flag on transactions r=DedrickEnc a=jniles This PRimplements the EDITED flag on records of transactions that have been modified via the posting journal edit tool. This signals the user that the transaction has been edited and the data might be out of date. This PR also improves the bhAutoDropup in some corner cases by accurately estimating the window size on startup and any resize events that occur. Previously, the first click might have an inaccurate window size. Furthermore, it implements debounce to ensure that the event loop is not blocked and the DOM is only manipulated a single time. Finally, a client-side flag is added to the registries and it looks like this: ![editedrecordflag](https://user-images.githubusercontent.com/896472/32416624-dc23f51e-c254-11e7-8b5d-12d9a4b4f230.PNG) _Fig 1: Edited Record Flag_ Closes #2047.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently there is no way of knowing if a BHIMA document has had its underlying transaction edited or changed during the posting process. There currently is not a use case for this however it may be useful to show on an invoice that the financial details of this document may have changed.
I propose that when an editing session is complete on a transaction it then uses the
identifiers.js
map to lookup the reference table and set anEDITED
flag toTRUE
.The
EDITED
flag would be added to:For example:
The text was updated successfully, but these errors were encountered: