projekt kivitendo

=head1 NAME

arap.pl - helper functions or customer/vendor retrieval

=head1 SYNOPSIS

Don't use anyting in this file without extreme care, and even then be prepared for massive headaches.

It's a collection of helper routines that wrap the customer/vendor dropdown/textfield duality into something even complexer.

=head1 FUNCTIONS

=head2 check_name customer|vendor

check_name was originally meant to update the selected customer or vendor. The

way it does that has generted more hate than almost any other part of this

software.

=over 4

It checks if a vendor or customer is given. No failsafe, vendor fallback if

$_[0] is something fancy.

It assumes, that there is a field named customer or vendor in $form.

It assumes, that this field is filled with name--id, and tries to split that.

sql ledger uses that combination to get ids into the select keys.

It looks for a field selectcustomer or selectvendor in $form. sql ledger used

to store a copy of the html select in there. (again, don't ask)

If this field exists, it looks for a field called oldcustomer or oldvendor, in

which the old name--id string was stored in sql ledger, and compares those.

if they don't match, it will set customer_id or vendor_id in $form, load the

entry (which will clobber everything in $form named like a column in customer

oder vendor) and return.

If there was no select* entry, it assumes that vclimit was lower than the

number of entries, and that an input field was generated. In that case the

splitting is omitted (since users don't generally include ids in entered names)

It looks for a *_id field, and combines it with the given input into a name--id

entry and compares it to the old* entry. (Missing any of these will instantly

break check_namea.

If those do not match, $form->get_name is called to get matching results.

get_name only matches by *number and name, not by id, don't try to get it to do

so.

The results are stored in $form>{name_list} but a count is returned, and

checked.

If only one result was found, *_id, * and old* are copied into $form, the entry

is loaded (like above, clobbering)

If there is more than one, a selection dialog is rendered

If none is found, an error is generated.

Since get_customer and get_vendor clobber a lot of fields, make sure what

changes exactly.

If you still want to use it, you can disable this feature, like this:

In that case multiple matches will trigger an error.

=cut