Projekt

Allgemein

Profil

« Zurück | Weiter » 

Revision 20118160

Von Jan Büren vor mehr als 9 Jahren hinzugefügt

  • ID 2011816080c4a2fc413edca52a7ee6c792d17ca9
  • Vorgänger 66fcb1c6
  • Nachfolger abb346b2

Doku: POD für Invoice.pm erweitert

- Invoice anstatt Delivery Order bei new_from
- Beispiel-Code für Benutzung von new_from mit parameter attributes
- TODO angelegt, Controller sollten einige Datenfelder mit Hilfe
von Backend-Funktionen prüfen können - in diesem Fall transdate

Unterschiede anzeigen:

SL/DB/Invoice.pm
=item C<attributes>
An optional hash reference. If it exists then it is passed to C<new>
allowing the caller to set certain attributes for the new delivery
order.
allowing the caller to set certain attributes for the new invoice.
For example to set a different transdate (default is the current date),
call the method like this:
my %params;
$params{attributes}{transdate} = '28.08.2015';
$invoice = SL::DB::Invoice->new_from($self, %params)->post || die;
=back
......
=back
=head1 TODO
As explained in the new_from example, it is possible to set transdate to a new value.
From a user / programm point of view transdate is more than holy and there should be
some validity checker available for controller code. At least the same logic like in
Form.pm from ar.pl should be available:
# see old stuff ar.pl post
#$form->error($locale->text('Cannot post transaction above the maximum future booking date!'))
# if ($form->date_max_future($transdate, \%myconfig));
#$form->error($locale->text('Cannot post transaction for a closed period!')) if ($form->date_closed($form->{"transdate"}, \%myconfig));
=head1 AUTHOR
Moritz Bunkus E<lt>m.bunkus@linet-services.deE<gt>

Auch abrufbar als: Unified diff