Difference between revisions of "News:Changes to the Approval function for Vouchers."

From Marathon Documentation
Jump to: navigation, search
(Marked this version for translation)
 
Line 1: Line 1:
 
<translate>
 
<translate>
  +
<!--T:1-->
 
{{News
 
{{News
 
|Changes to the Approval function for Vouchers
 
|Changes to the Approval function for Vouchers
Line 10: Line 11:
 
}}
 
}}
   
  +
<!--T:2-->
 
Changes to the Approval function for Vouchers.
 
Changes to the Approval function for Vouchers.
   
  +
<!--T:3-->
 
- When correcting a already Approved Voucher the Correction is now always saved with a new voucher number.
 
- When correcting a already Approved Voucher the Correction is now always saved with a new voucher number.
   
  +
<!--T:4-->
 
- When pressing the button Approve, it is now not possible to Approve if the Voucher already have been Approved.
 
- When pressing the button Approve, it is now not possible to Approve if the Voucher already have been Approved.
   
  +
<!--T:5-->
 
{{ExpandImage|GAP 1665 1.png}}
 
{{ExpandImage|GAP 1665 1.png}}
   
  +
<!--T:6-->
 
{{ExpandImage|GAP 1665 2.png}}
 
{{ExpandImage|GAP 1665 2.png}}
   

Latest revision as of 16:29, 9 October 2018

Changes to the Approval function for Vouchers
Published 2018-10-09
Module Accounting
Version 546
Revision 44287
Case number 1051139

Changes to the Approval function for Vouchers.

- When correcting a already Approved Voucher the Correction is now always saved with a new voucher number.

- When pressing the button Approve, it is now not possible to Approve if the Voucher already have been Approved.