user import process steps -...

User Import process stepsThis section describes the CSV file creation process for the User Import process into the Talent Suite.

Procedure

Create or update users in the Talent Suite by creating a row for every intended user.

Parent topic: Creating and Uploading a User Import CSV File

Common User Fields

Procedure

Create and/or update Common User fields using the specifications in the following table.

Table 1. General User Import CSV Column Specifications. Create and/or update Common User fields using the specifications in the General User Import CSV Column Specifications table.Column Header Required on

CreateRequiredonUpdate

Description MaxCharacterCount

Value Format Example

HRIS_EMPLOYEE_ID Yes Yes This is the unique identifier of theuser in the Talent Suite.

Note: Once it is set, it can NEVERbe updated. It MUST always be sentfor the user.

15 Alphanumeric

(case sensitive)

HRSYS1234

USER_NAME Yes No Username associated with the user.

This is a unique identifier for eachuser.

Note: You cannot have more than oneuser with the same username in thesame client.

255 Alphanumeric jwtaylor

FIRST_NAME Yes No First name of the user.

Note: BrassRing has the 30character limit.

30 Alphanumeric John

LAST_NAME Yes No Last name of the user.


30 Alphanumeric Smith

EMAIL_ADDRESS Yes No Email address associated with theuser.

Note: + or # are NOT validcharacters. DO NOT use them.

255 Standard email address format. [email protected]

LOCALE Yes No The language ID of the user. 5 ISO Locale Code. en_US

Note: If a locale is not provided, theuser will fail.

If a locale is provided and one of theapplications is not configured for it,the user will fail and tell you whichapplication needs to be updated.

Supported ISO Locales for TalentSuite

(en_US) English (UnitedStates)(en_GB) English (GreatBritain)(de_DE) German(it_IT) Italian(es_ES) Spanish (Spain)(es_MX) Spanish (Mexico)(fr_FR) French(fr_CA) French Canadian(zh_CN) Chinese(zh_TW) Chinese(Traditional)(cs_CZ) Czech(nl_NL) Dutch(ja_JP) Japanese(ko_KR) Korean(pl_PL) Polish(pt_PT) Portuguese(pt_BR) Portuguese (Brazil)(ru_RU) Russian(th_TH) Thai(da_DK) Danish(hu_HU) Hungarian

ACTIVE No No Status of the Talent Suite user.

This value will default to 1 (active).

Note: If this value is set to 0(inactive), the user will be active inthe downstream applications but allaccess to the Talent Suite will bedisabled.

In order to make the user inactive inthe downstream applications refer tothe app ACCESS columns.

1 1 or 0 0

MIDDLE_NAME No No Middle name of the user.


30 Alphanumeric William

PHONE_NUMBER No No Phone number of the user. 50 Alphanumeric 1231234567PHONE_EXTENSION No No Extension of phone number. 10 Alphanumeric 321JOB_TITLE No No Job Title of the user. 50 Alphanumeric AccountantCOUNTRY No No Country/geographical location of the

user.3 ISO ALPHA 3 Country Code USA

FAX_NUMBER No No Fax number of the user. 40 Alphanumeric 1231234568TIMEZONE No No Timezone of the user in UTC format. 9 UTC Format UTC 05:00EXPIRATION_DATE No No The expiration date of the user.

Note: Once expired, the user will nolonger have access to the Talent

20 yyyy‐MM‐dd 3000 01 01

longer have access to the TalentSuite.

If no value is set, the user will neverexpire.

VALIDITY_DATE No No The validity date of the user.(Indicates when the user becomesenabled, this date may be set in thefuture.)

Note: The user cannot log in until thevalidity date is passed.

If no value is set, it defaults to thecurrent date.

20 YYYY‐MM‐DD 2000 01 01

SSO_ENABLED No No Indicator of whether a user is SSOenabled or not.

1= true

0= false

If this field is not present or not valuedin the CSV file, the value will defaultto what is set on the client level.

For example:

If the client is SSO enabled, all userswill be SSO enabled unless specifiedotherwise.

The only time this field needs to bevalued is if the client is SSO enabled,however, the user being createdneeds to log into the Talent Suite.

1 1or 0 0

DEPARTMENT No No The department of the user in bothBrassRing and Talent Manager.

50 Alphanumeric Accounting

USER_CATEGORY No No This field sets a category on the user.

This is used when distinguishingusers for exports.

When a New Hire completes OnboardStart, they will appear in the UI withthe user category of NEW_HIRE.

When a New Hire becomes a systemuser, the user category should be setto EMPLOYEE in the CSV file so thatthe user will export as an employeeinstead of a new hire.

The other categories available are forthe client's discretion. Setting thevalue to something other thanNEW_HIRE or EMPLOYEE means

18 Case Sensitive.

It MUST be one of the followingvalues:

NEW_HIREEMPLOYEEEXTERNALEXTERNAL_CANDIDATEIBMINTERNAL_CANDIDATEINTERNAL_NEW_HIREMANAGER

EMPLOYEE

NEW_HIRE or EMPLOYEE meansthat the only time the user will beseen in the export is if all users areexported.

SEND_PASSWORD_EMAIL No No This field allows for the first timelogin email to be suppressed oncreate if the client chooses to notsend it.

Set the value as True or 1 to sendthe email as expected, or False or 0to suppress the email.

If the value is True but theuser fails, has a validity datein the future, or is an SSOenabled user, the user willstill not receive the email.If a user is updated andSEND_PASSWORD_EMAIL= True, and if the user hasnot logged in before, they willreceive a first time loginemail again.

1 1 or 0 0

BrassRing Hiring Fields

Procedure

To provision a user for the BrassRing Hiring application, follow the instructions in the BrassRing Hiring Fields table.

Table 2. BrassRing Hiring Fields. Provision a user for the BrassRing Hiring application by following the instructions in the BrassRing Hiring Fields table.Column Header Required on Create Required

onUpdate



BR_HIRING_ACCESS Yes No This field determines whether ornot the user is provisioned forBrassRing in the Talent Suite.

Note: This field is only requiredif you are trying to provision theuser for BrassRing.

This field supports the followingstates:

ACTIVE = User is active in thesystem and will have access tothe application through theTalent Suite. (We also support[1] for this state.)

INACTIVE = User is inactive inthe system and will not have

16 Alphanumeric.

(Not case sensitive.)

ACTIVE

the system and will not haveaccess to the applicationthrough the Talent Suite. (Wealso support [0] for this state.)

ACTIVE_NO_ACCESS = Useris Active in the system but willnot have access to theapplication through the TalentSuite.

Note: TheACTIVE_NO_ACCESS state ishow the Talent Suite nowsupports theBR_EXPRESS_USERscenario.

The following fields only apply when you are provisioning a user for access to the BrassRing application.

Table 3. BrassRing Hiring Fields used for provisioning a user for access to the BrassRing application. Use this table when provisioning a user for access to the BrassRing application.Column Header Required on




BR_HIRING_USER_TYPE* Yes No User type of the user inBrassRing.

Note: *This field namechanged, it was previouslycalled BR_USER_TYPE.

255 Alphanumeric.

(Case sensitive.)

Hiring Manager

BR_USER_GROUP Yes No User group of the user inBrassRing.

Note: User Groups are usedwhen utilizing the systemsResume Security feature.

The values MUST alreadyexist in BrassRing.

Multiple user groups for theuser are separated by |*|.(Each |*| counts as 3characters towards the maxcharacter count.)

255 Alphanumeric.

(Case sensitive.)

StandardGroup|*|Group_2

BR_ORGANIZATION_GROUP Yes No Required only if Org Groupsare being used by the client.

Organizational Group theuser belongs to. Org Groupscontrol a user's access toCommunications, ReqTemplates, Talent Gatewaysand Agency Manager.The values MUST alreadyexist in BrassRing.

2000 Alphanumeric.

(Case sensitive.)

Global|*|Standard

exist in BrassRing.

Multiple org groups for theuser are separated by |*|.(Each |*| counts as 3characters towards the maxcharacter count.)

BR_APPROVAL_GROUPS No No This identifies the user as aform Approval.


Multiple approval groups forthe user are separated by |*|.(Each |*| counts as 3characters towards the maxcharacter count.)

255 Alphanumeric.

(Case sensitive.)

HR_VP|*|COO

BR_CODE_ACCESS_GROUPS No No Code Access Groups can beconfigured in order tominimize the number of jobcodes that a user has tosearch through whencreating a new Requisition.


Multiple code access groupsfor the user are separatedby|*|. (Each |*| counts as 3characters towards the maxcharacter count.)

255 Alphanumeric.

(Case sensitive.)

Code1|*|Code2

BR_KIB_USER_GROUP No No This identifies the user'sKenexa Interview BuilderUser Group.


Multiple KIB user groups forthe user are separated by |*|.(Each |*| counts as 3characters towards the maxcharacter count.)

255 Alphanumeric.

(Case sensitive.)

Administrator|*|Deity

BR_MANAGER No No Defines if the user is amanager in BrassRing.

1 1 or 0 1

BR_RECRUITER No No Defines if the user is arecruiter in BrassRing.

1 1 or 0 1

SENDER_EMPLOYEE_ID Yes No A valid Employee ID for auser that exists in bothBrassRing and TalentManager for the integration

to work.

50 Alphanumeric. HRXMLUSER

BR_REQUISITION_PRIVILEGES No No Assigns a Req Privilege to auser.

The Client MUST beconfigured for ReqPrivileges and the valueMUST exist in BrassRing.

4000 Alphanumeric.

(Case sensitive.)

Legal

BR_CUSTOM_APPROVAL_ROLE_ID No No Assigns the user to SmartApproval.

The Client MUST beconfigured for SmartApproval.

Note: It will take 24 hrs. forthe user to appear in theSmart Approval section inBrassRing.

100 Alphanumeric. SA Manager

BR_CUSTOM_APPROVAL_SUPERVISOR_ID No No Assigns the user to SmartApproval.

The Client MSUT beconfigured for SmartApproval.

Note: It will take 24 hrs. forthe user to appear in theSmart Approval section inBrassRing.

40 Alphanumeric. 103

Onboard Hiring Manager Fields

Procedure

To provision a user for the Onboard Hiring application, follow the instructions in the Onboard Hiring Fields table.

Table 4. Onboard Hiring Manager Fields. Use this Onboard Hiring Manager Fields table when provisioning a user for the Onboard Hiring application.Column Header Required on Create Required

onUpdate



OB_MANAGER_ACCESS Yes No This field determines whetheror not the user is provisionedfor Onboard in the Talent Suite.

Note: This field is only requiredif you are trying to provision theuser for Onboard.


ACTIVE = User is active in the

system and will have access tothe application through the

16 Alphanumeric.


ACTIVE

the application through theTalent Suite. (We also support[1] for this state.)

INACTIVE = User is inactive inthe system and will not haveaccess to the applicationthrough the Talent Suite. (Wealso support [0] for this state.)

ACTIVE_NO_ACCESS = Useris active in the system but willnot have access to theapplication through the TalentSuite.

The following fields only apply when provisioning a user for the Onboard Manager application.

Table 5. Onboard Hiring Fields used for provisioning a user for access to the Onboard Manager application. The fields in this table only apply when provisioning a user for the OnboardManager application.Column Header Required on Create Required

onUpdate



OB_MANAGER_USER_TYPE* Yes No User type of the user inOnboard.

The value MUST alreadyexist in Onboard.

Note: *This field namechanged. It was previouslycalled OB_USER_TYPE.

255 Alphanumeric.

(Case sensitive.)

Hiring Manager

OB_USER_GROUP Yes No User group of the user inOnboard.

The value MUST alreadyexist in Onboard.

Multiple user groups for theuser are separated by |*|.(Each |*|counts as 3characters towards the maxcharacter.)

255 Alphanumeric.

(Case sensitive.)

StandardGroup|*|Update Group

OB_USER_LOCATION No No Sets the location of the user inOnboard.

The value passed MUST bethe EntryAlphaKey of thelocation found in Onboard.

4000 Alphanumeric.

(Case sensitive.)

Local

Talent Manager Performance Fields

Procedure

To provision a user for the Talent Manager Performance application, follow the instructions in the Talent Manager Performance Fields table.

Table 6. Talent Manager Performance Fields. Use the Talent Manager Performance Fields table when provisioning a user for the Talent Manager Performance application.Column Header Required on Create Required

onUpdate



TM_PERFORMANCE_ACCESS Yes No This field determines whetheror not the user is provisionedfor Talent Manager in the TalentSuite.

Note: This field is only requiredif you are trying to provision theuser for Talent Manager.





16 Alphanumeric.


ACTIVE

The following fields are required only apply when provisioning a user for the Talent Manager Performance application.

Table 7. Talent Manager Performance Hiring Fields used for provisioning a user for access to the Talent Manager Performance application. The fields in this table are required only applywhen provisioning a user for the Talent Manager Performance application.Column Header Required on Create Required

onUpdate



TM_PERFORMANCE_USER_TYPE* Yes No User type of the user in TalentManager.

The value MUST alreadyexist in Talent Manager.

The value MUST be one ofthe following:

ADM = Administrator

255 Alphanumeric.

(Case sensitive.)

EMP

CA = Comp Analyst

EMP = Employee

HR = Human Resources

HRIS = HRIS Admin

HRM = HR Manager

IMGR = Incentive Manager

LA = Language Assistance

MGR = Line Manager

SADM = IBM Administrator

Note: *This field namechanged. It was previouslycalled TM_USER_TYPE.

SENDER_EMPLOYEE_ID Yes No A valid Employee ID for auser that exists in TalentManager for the integration towork.

50 Alphanumeric. HRXMLUSER

Talent Insights Fields

Procedure

To provision a user for Talent Insights, follow the instructions in the Talent Insights Fields table.

Table 8. Talent Insights Fields. Use the Talent Insights Fields table when provisioning a user for Talent Insights.Column Header Required on Create Require

onUpdate



TI_TALENT_INSIGHTS_ACCESS Yes No This field determines whetheror not the user is provisionedfor Talent Insights in the TalentSuite.

Note: This field is only requiredif you are trying to provision theuser for Talent Insights.



INACTIVE = User is inactive inthe system and will not have

16 Alphanumeric.


ACTIVE

access to the applicationthrough the Talent Suite. (Wealso support [0] for this state.)


The following fields are only applicable when provisioning a user for Talent Insights.

Table 9. Talent Insights Field used for provisioning a user for to Talent Insights. The fields in this table are only applicable when provisioning a user for Talent Insights.Column Header Required on Create Required

onUpdate



TI_TALENT_INSIGHTS_USER_TYPE* Yes No User type of the user inTalent Insights.

The value MUST alreadyexist in Talent Insights.

Note: *This field namechanged. It was previouslycalled.

255 Alphanumeric.

(Case sensitive.)

HR Executive

TI_ROLE_ID Yes No Unique ID that correspondsto a specific user type inTalent Insights.

3 Numeric 1

Admin Application Fields

Procedure

To provision a user for the Talent Suite Admin application, follow the instructions in the Admin Application Fields table.

Table 10. Admin Application Fields. Use the Admin Application Fields table when provisioning a user for the Talent Suite Admin application.Column Header Required on Create Required

onUpdate



TS_ADMIN_ACCESS Yes No This field determines whether ornot the user is provisioned forTalent Suite Admin in the TalentSuite.

Note: This field is only requiredif you are trying to provision theuser for Talent Suite Admin.


ACTIVE = User is active in thesystem and will have access to

16 Alphanumeric.


ACTIVE




The following field is only applicable when provisioning a user for the Talent Suite Admin application.

Table 11. Talent Suite Admin Field used for provisioning a user for access to the Talent Suite Admin application. The fields in this table are only applicable when provisioning a user for theTalent Suite Admin application.Column Header Required on Create Required

onUpdate



TS_ADMIN_USER_TYPE Yes No User type of the user inTalent Suite.

The value MUST alreadyexist in Talent Suite.

255 Alphanumeric.

(Case sensitive.)

IBM_ADMIN

Talent Gateway Jobs field

Procedure

To provision a user for the Talent Gateway Jobs application, follow the instructions in the Talent Gateway Jobs field table.

Table 12. Talent Gateway Jobs field. Use the Talent Gateway Jobs field table when provisioning a user for the Talent Gateway Jobs application.Column Header Required on Create Required

onUpdate



BRTG_JOBS_ACCESS Yes No This field determines whether ornot the user is provisioned forTalent Gateway in the TalentSuite.

Note: This field is only requiredif you are trying to provision theuser for Talent Gateway.


ACTIVE = User is active in thesystem and will have access to

16 Alphanumeric.


ACTIVE




Connections Social Cloud field

Procedure

To provision a user for the Connections Social Cloud application (the Social components of the Talent Suite), follow the instructions in the Connections Social Cloud field table.

Table 13. Connections Social Cloud field. Use the Connections Social Cloud field table when provisioning a user for the Connections Social Cloud application.Column Header Required on




CONNECTIONS_SOCIAL_CLOUD_ACCESS Yes No This field determines whetheror not the user is provisionedfor Social in the Talent Suite.

Note: This field is onlyrequired if you are trying toprovision the user for Social.

This field supports thefollowing states:

ACTIVE = User is active in thesystem and will have accessto the application through theTalent Suite. (We also support[1] for this state.)

INACTIVE = User is inactivein the system and will not haveaccess to the applicationthrough the Talent Suite. (Wealso support [0] for this state.)

ACTIVE_NO_ACCESS =User is active in the systembut will not have access to theapplication through the TalentSuite.

16 Alphanumeric.


ACTIVE

Expertise Manager fields

Procedure

To provision a user for the Expertise Manager application, follow the instructions in the Expertise Manager Application Fields table.

Table 14. Expertise Manager Application Fields. Use the Expertise Manager Application Fields table when provisioning a user for the Expertise Manager application.Column Header Required on Create Required

onUpdate



EM_ACCESS Yes No This field determines whether ornot the user is provisioned forSocial in the Talent Suite.

Note: This field is only requiredif you are trying to provision theuser for Social.





16 Alphanumeric.


ACTIVE

The following field is only applicable when provisioning a user for the Expertise Manager application.

Table 15. Talent Suite Expertise Manager Field used for provisioning a user for access to the Expertise Manager application. The fields in this table are only applicable when provisioning auser for the Expertise Manager application.Column Header Required on Create Required

onUpdate



EM_USER_TYPE Yes No User type of the user inExpertise Manager.

255 Alphanumeric.

(Case sensitive.)

EE

Employee Voice Application Fields

Procedure

To provision a user for the Talent Suite Employee Voice application, follow the instructions in the Employee Voice Application Fields table.

Table 16. Employee Voice Application Fields. Use the Employee Voice Application Fields table when provisioning a user for the Employee Voice application.Column Header Required on Create Required

onUpdate



EMPLOYEEVOICE_ACCESS Yes No Provisions the user for theEmployee Voice application.

This field determines whetheror not the user is provisionedfor Employee Voice in theTalent Suite.

Note: This field is only requiredif you are trying to provision theuser for Talent Suite EmployeeVoice.





16 Alphanumeric.


ACTIVE

The following field is only applicable when provisioning a user for the Employee Voice application.

Table 17. Talent Suite Employee Voice Field used for provisioning a user for access to the Employee Voice application. The fields in this table are only applicable when provisioning a userfor the Employee Voice application.Column Header Required on Create Required

onUpdate



EMPLOYEEVOICE_USER_TYPE Yes No User type of the user in EmployeeVoice.

Administrator

(Gives the user access toconfiguration, response

255 Single entry.

Alphanumeric.

(Case sensitive.)

Manager

rate, and reports inManager Dashboard)

Manager

(Gives the user access tothe response rate andreports in ManagerDashboard)

Content_Administrator

(Gives the user access toall of Content Authoring)

Email_Administrator

(Gives the users accessto Email Authoring)

Use |*| to separate multipleselections.

Required only ifEMPLOYEEVOICE_ACCESS isset to 1.

OrgMapper Application Fields

Procedure

To provision a user for the Talent Suite OrgMapper application, follow the instructions in the OrgMapper Application Fields table.

Table 18. OrgMapper Application Fields. Use the OrgMapper Application Fields table when provisioning a user for the OrgMapper application.Column Header Required on Create Required

onUpdate



OM_ACCESS Yes No Provisions the user forOrganizational Mapping.

This field determines whether ornot the user is provisioned forOrgMapper in the Talent Suite.

Note: This field is only requiredif you are trying to provision theuser for Talent SuiteOrgMapper.



16 Alphanumeric.


ACTIVE



The following field is only applicable when provisioning a user for the OrgMapper application.

Table 19. Talent Suite OrgMapper Field used for provisioning a user for access to the OrgMapper application. The fields in this table are only applicable when provisioning a user for theOrgMapper application.Column Header Required on




OM_USER_TYPE Yes No User type of the user inOrgMapper.

Identifies the user’sOrganizational Mapping UserGroup.

Administrator

(Gives the user access toall functionality inOrgMapper.)

Coordinator

(Gives the user access toeverything in OrgMapperexcept data import andconfiguration.)

Only accepts one value, the valueMUST be from the preceding list.

Required only if OM_ACCESS isset to 1.

255 Single entry.

Alphanumeric.

(Case sensitive.)

Coordinator

OM_ORG_SECURITY_LEVEL Yes No Identifies the user's security levelat the organization level.

Required only if OM_ACCESS isset to 1.

The default value is ALL.

ALL provides access to all nodeswithin the customer instance ofOrgMapper.

255 Alphanumeric. From customer EmployeeBob Smith Employee ID =P0001

A user set setup withOM_ORG_SECURITY_LEVEL= P0001

The user has access to theentire record for only 'BobSmith' in OrgMapper and hisentire downline.

The field value to reference forOM_ORG_SECURITY_LEVELcomes from the customerOrgMapper data file EmployeeID field. If no value is provided,use Default Value of ALL.

If an Employee ID is providedwithin a higher security level, it isassumed as having the higheraccess. Use |*| to separatemultiple selections.

Note: A check is needed to havein place to prevent the client fromgoing over the limit as this mightbe possible in the near future.

Alternate Example:

A user is setup withOM_ORG_SECURITY_LEVEL= ALL

The user has access to allrecords in their instance ofOrgMapper.

Upload the CSV file to the Talent Suite

Procedure

1. Once the .csv file has been created and is ready to upload to the Talent Suite, select the Browse button in the Select CSV file field. The File Upload dialog window opens.

Figure 1. File Upload (Browse to select CSV file)

2. In the File Upload dialog box, navigate to the location of the .csv Import Users Specifications file created following the process steps in the User Provisioning, Import and Management and Creating the.csv File sections.

3. Select the .csv Import Users Specifications file and then select Open. The file will upload to the Talent Suite.4. Select the .csv Import Users Specifications file and then select Open. The file then uploads to the Talent Suite. The .csv file appears in the Select CSV file field on the Import Users page.

Figure 2. Import Users page Uploaded CSV file

5. Select the Import button to import the file into the Talent Suite. A message dialog window displays with a message asking the user if they wish to proceed. Are you sure you want to importthis file? The users you are importing will overwrite any existing users in the system.

Figure 3. Proceed to import CSV file message

6. Select Yes, proceed to import the .csv file or Cancel to exit without importing the .csv file.

7. If Cancel is selected, then select the x icon for the .csv file displayed in the Select CSV file field to remove the file for upload into the Talent Suite.

user import process steps -...

Documents