Análisis de accidentes por zona con edad de los ciclistas y de los otros

Loaders are available to set up objects related to partner management features. These correspond to tasks and objects in the Partner360 module. They are described in detail in the Operative.One Partner Man- agement User’s Guide.

Partners

This loader is used to import partner organizations and partner users. Partner organizations are created in the Administration module under System > Organizations > Organizations or through the Partner360 mod- ule. You can also create partners through either this loader or the Organization loader. Partner users are created in the Partner360 module on a partner’s Users tab or through the loaders.

Users with the support_ops role can download theImport_Partners.xlssample template from the tem- plates directory introduced inTemplate Environmentson page 7.

To import the completed loader into Operative.One, go to theAdministrationmodule >Systemtab >Cat- egories> Tools>Object Import/Export, and selectPartnerfrom the drop-down list.

The following functions are supported:

l Create l Update

Be aware of the following when using this loader:

l You can add multiple users to the same partner by repeating the partner details multiple times in

this file.

l Before loading a partner, its parent business entity must already exist. Operative recommends pla-

cing partners under business entities rather than under the global default organization.

l Partner custom fields cannot be set through the loader.

The following fields appear in the loader template.

Field Description Data

Type Required Limits Organization This should be left empty. It is not needed. Text No

ID When using the loader to update a record, this must be the ID assigned by Operative.One when the organization was created. It must be empty for a cre- ate, and it must be an existing ID during an update.

Integer Update only

Name This is the name of the organization. Text Yes 50 characters Parent Id This is the ID of the organization above this organ-

ization in the hierarchy. This organization must already exist. You can identify the parent by using either this ID or the name in the next column.

Type Parent Name This is the name of the organization above this

organization in the hierarchy. This organization must already exist. You can identify the parent by using either the name or the id in the previous column.

Text Yes

Parent Type This identifies the type of parent organization and must be one of the following, matching the parent’s type: l Global Organization l Approval Group l Team l Business Entity Text Yes

Status This must be one of the following (case sensitive):

l active l inactive

Text Yes

Email This is the email address for the organization. It must be in the form of an email address with an “@” and “.”.

Text No 50 characters

Phone This is the Phone field for the organization. Text No 25 characters Fax This is the Fax field for the organization. Text No 25 characters Billing

Address: Address Line 1

This is the Billing Address: Address Line 1 field for the organization. The next five columns correspond to the other billing address fields. The column head- ers match their UI names.

Text No 255 char- acters Billing Address: Address Line 2 Text No 255 char- acters Billing Address: City Text No 25 characters Billing Address: State / Province / Region Text No 50 characters Billing Address: ZIP / Postal Code Text No 25 characters

Field Description Data

Type Required Limits Billing Address: Country Text No 25 characters Shipping Address: Address Line 1

This is the Shipping Address: Address Line 1 field for the organization. The next five columns cor- respond to the other shipping address fields. The column headers match their UI names.

Text No 255 char- acters Shipping Address: Address Line 2 Text No 255 char- acters Shipping Address: City Text No 25 characters Shipping Address: State / Province / Region Text No 50 characters Shipping Address: ZIP / Postal Code Text No 25 characters Shipping Address: Country Text No 50 characters

Site URL This is a free text entry field. Text No 150 char- acters First Name This sets the first name of the partner user. These

are the users you can create in the Partner360 mod- ule. If you specify any of the user fields in the loader, you must specify all six of them.

Text No unless importing a user

50 characters

Last Name This sets the last name of the partner user. Text No unless importing a user

50 characters

Email This sets the email address of the partner user. Text No unless importing a user

Type UID This sets the login name of the partner user. On an

update, if this is an existing login name, the user is updated.

This should not include the @company.ext portion of the name. Integer No unless importing a user 50 characters (but must account for @company .ext portion) Password This sets the password associated with the UID. Text No

unless importing a user Status When specifying a user, this must be one of the fol-

lowing (case sensitive) for the user:

l active l inactive Text No unless importing a user Primary Contact

This sets a partner user associated with the partner. It must be the first name and last name of an Oper- ative.One user with the Partner role that is asso- ciated with a partner organization.

Text No

Manager This sets the user responsible for managing the part- ner relationship. It must be the first name and last name of an Operative.One user with the Partner Manager role.

Text No

Payment Terms

This sets payment terms that determine how partner payments are calculated. It must match the name of payment terms defined in the Partner360 module. It is required.

Text Yes

Monthly Impression Quota

This sets the impression quota that appears in the Partner360 module on a partner’s Performance tab.

Integer No