projekt kivitendo

sub update_entries_for_authorized_users {

  my ($class) = @_;

  my %employees_by_login = map { ($_->login => $_) } @{ $class->get_all };

  require SL::DB::AuthClient;

  foreach my $user (@{ SL::DB::AuthClient->new(id => $::auth->client->{id})->load->users || [] }) {

    my $user_config = $user->config_values;

    my $employee    = $employees_by_login{$user->login} || SL::DB::Employee->new(login => $user->login);

    $employee->update_attributes(

      name      => $user_config->{name},

      workphone => $user_config->{tel},

      deleted   => 0,

    );

  }

}

__END__

=pod

=encoding utf8

=head1 NAME

SL::DB::Manager::Employee - RDBO manager for the C<employee> table

=head1 SYNOPSIS

  my $logged_in_employee = SL::DB::Manager::Employee->current;

=head1 FUNCTIONS

=over 4

=item C<current>

Returns an RDBO instance corresponding to the currently logged-in user.

=item C<update_entries_for_authorized_users>

For each user created by the administrator in the admin section an

entry only exists in the authentication table, but not in the employee

table. This is where this function comes in: It iterates over all

authentication users that have access to the current client and ensure

than an entry for them exists in the table C<employee>. The matching

is done via the login name which must be the same in both tables.

The only other properties that will be copied from the authentication

table into the C<employee> row are C<name> and C<workphone>. In

addition C<deleted> is always set to 0.

The intention is that this function is called automatically during the

login process.

=back

=head1 BUGS

Nothing here yet.

=head1 AUTHOR

Moritz Bunkus E<lt>m.bunkus@linet-services.deE<gt>

=cut

use SL::DB::Employee;

  if (!$update_available) {

    SL::DB::Manager::Employee->update_entries_for_authorized_users;

    return LOGIN_OK();

  }

  # If $self->dbupdate2 returns than this means all upgrade scripts

  # have been applied successfully, none required user

  # interaction. Otherwise the deeper layers would have called

  # ::end_of_request() already, and return would not have returned to

  # us. Therefore we can now use RDBO instances because their supposed

  # table structures do match the actual structures. So let's ensure

  # that the "employee" table contains the appropriate entries for all

  # users authorized for the current client.

  SL::DB::Manager::Employee->update_entries_for_authorized_users;