Import reps (spec)

From RPM Wiki

Table of contents
1 Summary
2 File and data format
3 Common functionality
4 Type

4.1 Create
4.2 Update

5 Agency primary contact
6 Security

6.1 Staff users
6.2 Agent users
6.3 Modules

7 History
[edit]

Summary

An import used to create or update agent reps from an Excel file

[edit]

File and data format

[edit]

Common functionality

Start with the Import and Common import functionality (spec) pages.

[edit]

Type

The first column determines if this is a manager or a rep (or both)

[edit]

Create

  • If the cell contains "manager", case insensitive, the user will be a manager.
  • If the cell contains "both", case insensitive, the user will be both a rep and a manager.
  • Anything else (or nothing) will result in a rep user.
  • If a cell in the Relationship column contains "SA" the rep is a sub agent.
[edit]

Update

  • This column is the one exception to the normal behavior of updating an existing record. The problem is when a user is a manager and a rep, that's technically two separate things.
  • The importer will never delete objects. That means we can't change, say, a rep only user to a manager only user because that would mean deleting the rep.
  • So. the way the importer works when updating an existing rep/manager is that it will create the other object if that other type is specified (or "both" is specified), but will leave the existing object intact. The contact information will be shared between the manager and rep and will not be updated by the act of creating a new rep for an existing manager or vice versa. The same holds true for the "Rep commission access" setting.
    • Example: I have a rep, but the import has their name & agency, but "Manager" as the type. This will cause a manager to be created and the user will be a rep + manager.
[edit]

Agency primary contact

In RPM it's possible for a rep/manager to share the contact ID with a the agency primary contact. If this sharing is already in place when an agency or rep import updates existing contact information, that sharing updates the other record as well. However, the import will never setup this sharing where it doesn't already exist. For example, if a rep import is done where the first name & last name are the same as the agency primary contact, we still create the rep as a separate contact record.

[edit]

Security

[edit]

Staff users

  • The "Import forms" privilege is required
  • Also, a "Full" privilege for a process is required to import forms to it.
[edit]

Agent users

  • n/a
[edit]

Modules

The "Process management" module is required

[edit]

History

Retrieved from "http://rpmsoftware.com/wiki/index.php/Import_reps_%28spec%29"
  • This page was last modified 17:00, 26 Sep 2006.
  • This page has been accessed 830 times.