User Import process steps

Transcription

1 User Import process steps This secti describes the CSV file creati process for the User Import process into the Talent 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 Comm User Fields Create and/or update Comm User fields using the specificatis in the following table. Table 1. General User Import CSV Column Specificatis. Create and/or update Comm User fields using the specificatis in the General User Import CSV Column Specificatis table. Column Header Required Create Descripti Required HRIS_EMPLOYEE_ID Yes Yes This is the unique identifier of the user in the Talent Note: Once it is set, it can NEVER be updated. It MUST always be sent for the user. 15 Alphanumeric (case sensitive) HRSYS1234 USER_NAME Yes No Username associated with the user. 255 Alphanumeric jwtaylor This is a unique identifier for each user. Note: You cannot have more than e user with the same username in the same client. FIRST_NAME Yes No First name of the user. 30 Alphanumeric John Note: BrassRing has the 30 character limit. LAST_NAME Yes No Last name of the user. 30 Alphanumeric Smith Note: BrassRing has the 30 character limit. _ADDRESS Yes No address associated with the user. 255 Standard address format. Jwsmith@ .com Note: + or # are NOT valid characters. DO NOT use them. LOCALE Yes No The language ID of the user. 5 ISO Locale Code. en_us

2 Note: If a locale is not provided, the user will fail. If a locale is provided and e of the applicatis is not cfigured for it, the user will fail and tell you which applicati needs to be updated. ACTIVE No No Status of the Talent Suite user. Supported ISO Locales for Talent Suite (en_us) English (United States) (en_gb) English (Great Britain) (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 (Traditial) (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 1 1 or 0 0 This value will default to 1 (active). Note: If this value is set to 0 (inactive), the user will be active in the downstream applicatis but all access to the Talent Suite will be disabled. In order to make the user inactive in the downstream applicatis refer to the app ACCESS columns. MIDDLE_NAME No No Middle name of the user. 30 Alphanumeric William Note: BrassRing has the 30 character limit. PHONE_NUMBER No No Phe number of the user. 50 Alphanumeric PHONE_EXTENSION No No Extensi of phe number. 10 Alphanumeric 321 JOB_TITLE No No Job Title of the user. 50 Alphanumeric Accountant COUNTRY No No ry/geographical locati of the user. 3 ISO ALPHA 3 ry Code USA FAX_NUMBER No No Fax number of the user. 40 Alphanumeric TIMEZONE No No Timeze of the user in UTC format. 9 UTC Format UTC 05:00 EXPIRATION_DATE No No The expirati date of the user. Note: Once expired, the user will no lger have access to the Talent 20 yyyy MM dd

3 lger have access to the Talent If no value is set, the user will never expire. VALIDITY_DATE No No The validity date of the user. (Indicates when the user becomes enabled, this date may be set in the future.) 20 YYYY MM DD Note: The user cannot log in until the validity date is passed. If no value is set, it defaults to the current date. SSO_ENABLED No No Indicator of whether a user is SSO enabled or not. 1 1or 0 0 1= true 0= false If this field is not present or not valued in the CSV file, the value will default to what is set the client level. For example: If the client is SSO enabled, all users will be SSO enabled unless specified otherwise. The ly time this field needs to be valued is if the client is SSO enabled, however, the user being created needs to log into the Talent DEPARTMENT No No The department of the user in both BrassRing and Talent Manager. USER_CATEGORY No No This field sets a category the user. This is used when distinguishing users for exports. When a New Hire completes Onboard Start, they will appear in the UI with the user category of NEW_HIRE. When a New Hire becomes a system user, the user category should be set to EMPLOYEE in the CSV file so that the user will export as an employee instead of a new hire. 50 Alphanumeric Accounting 18 Case Sensitive. It MUST be e of the following values: NEW_HIRE EMPLOYEE EXTERNAL EXTERNAL_CANDIDATE IBM INTERNAL_CANDIDATE INTERNAL_NEW_HIRE MANAGER EMPLOYEE The other categories available are for the client's discreti. Setting the value to something other than NEW_HIRE or EMPLOYEE means

4 NEW_HIRE or EMPLOYEE means that the ly time the user will be seen in the export is if all users are exported. SEND_PASSWORD_ No No This field allows for the first time login to be suppressed create if the client chooses to not send it. 1 1 or 0 0 Set the value as True or 1 to send the as expected, or False or 0 to suppress the . If the value is True but the user fails, has a validity date in the future, or is an SSO enabled user, the user will still not receive the . If a user is updated and SEND_PASSWORD_ = True, and if the user has not logged in before, they will receive a first time login again. BrassRing Hiring Fields To provisi a user for the BrassRing Hiring applicati, follow the instructis in the BrassRing Hiring Fields table. Table 2. BrassRing Hiring Fields. Provisi a user for the BrassRing Hiring applicati by following the instructis in the BrassRing Hiring Fields table. Column Header Required Create Required Descripti BR_HIRING_ACCESS Yes No This field determines whether or not the user is provisied for BrassRing in the Talent 16 Alphanumeric. (Not case sensitive.) ACTIVE Note: This field is ly required if you are trying to provisi the user for BrassRing. This field supports the following states: ACTIVE = User is active in the system and will have access to the applicati through the Talent (We also support [1] for this state.) INACTIVE = User is inactive in the system and will not have

5 the system and will not have access to the applicati through the Talent (We also support [0] for this state.) ACTIVE_NO_ACCESS = User is Active in the system but will not have access to the applicati through the Talent Note: The ACTIVE_NO_ACCESS state is how the Talent Suite now supports the BR_EXPRESS_USER scenario. The following fields ly apply when you are provisiing a user for access to the BrassRing applicati. Table 3. BrassRing Hiring Fields used for provisiing a user for access to the BrassRing applicati. Use this table when provisiing a user for access to the BrassRing applicati. Column Header Required Create Descripti Required BR_HIRING_USER_TYPE* Yes No User type of the user in BrassRing. Note: *This field name changed, it was previously called BR_USER_TYPE. Hiring Manager BR_USER_GROUP Yes No User group of the user in BrassRing. Note: User Groups are used when utilizing the systems Resume Security feature. The values MUST already exist in BrassRing. Multiple user groups for the user are separated by *. (Each * counts as 3 characters towards the max character count.) BR_ORGANIZATION_GROUP Yes No Required ly if Org Groups are being used by the client. Organizatial Group the user belgs to. Org Groups ctrol a user's access to Communicatis, Req Templates, Talent Gateways and Agency Manager. The values MUST already exist in BrassRing Alphanumeric. Standard Group * Group_2 Global * Standard

6 exist in BrassRing. Multiple org groups for the user are separated by *. (Each * counts as 3 characters towards the max character count.) BR_APPROVAL_GROUPS No No This identifies the user as a form Approval. The values MUST already exist in BrassRing. Multiple approval groups for the user are separated by *. (Each * counts as 3 characters towards the max character count.) HR_VP * COO BR_CODE_ACCESS_GROUPS No No Code Access Groups can be cfigured in order to minimize the number of job codes that a user has to search through when creating a new Requisiti. The values MUST already exist in BrassRing. Multiple code access groups for the user are separated by *. (Each * counts as 3 characters towards the max character count.) Code1 * Code2 BR_KIB_USER_GROUP No No This identifies the user's Kenexa Interview Builder User Group. The values MUST already exist in BrassRing. Multiple KIB user groups for the user are separated by *. (Each * counts as 3 characters towards the max character count.) Administrator * Deity BR_MANAGER No No Defines if the user is a manager in BrassRing. BR_RECRUITER No No Defines if the user is a recruiter in BrassRing. SENDER_EMPLOYEE_ID Yes No A valid Employee ID for a user that exists in both BrassRing and Talent Manager for the integrati to work. 1 1 or or Alphanumeric. HRXMLUSER

7 BR_REQUISITION_PRIVILEGES No No Assigns a Req Privilege to a user. The Client MUST be cfigured for Req Privileges and the value MUST exist in BrassRing Alphanumeric. Legal BR_CUSTOM_APPROVAL_ROLE_ID No No Assigns the user to Smart Approval. 100 Alphanumeric. SA Manager The Client MUST be cfigured for Smart Approval. Note: It will take 24 hrs. for the user to appear in the Smart Approval secti in BrassRing. BR_CUSTOM_APPROVAL_SUPERVISOR_ID No No Assigns the user to Smart Approval. 40 Alphanumeric. 103 The Client MSUT be cfigured for Smart Approval. Note: It will take 24 hrs. for the user to appear in the Smart Approval secti in BrassRing. Onboard Hiring Manager Fields To provisi a user for the Onboard Hiring applicati, follow the instructis in the Onboard Hiring Fields table. Table 4. Onboard Hiring Manager Fields. Use this Onboard Hiring Manager Fields table when provisiing a user for the Onboard Hiring applicati. Column Header Required Create Required Descripti OB_MANAGER_ACCESS Yes No This field determines whether or not the user is provisied for Onboard in the Talent 16 Alphanumeric. (Not case sensitive.) ACTIVE Note: This field is ly required if you are trying to provisi the user for Onboard. This field supports the following states: ACTIVE = User is active in the system and will have access to the applicati through the

8 the applicati through the Talent (We also support [1] for this state.) INACTIVE = User is inactive in the system and will not have access to the applicati through the Talent (We also support [0] for this state.) ACTIVE_NO_ACCESS = User is active in the system but will not have access to the applicati through the Talent The following fields ly apply when provisiing a user for the Onboard Manager applicati. Table 5. Onboard Hiring Fields used for provisiing a user for access to the Onboard Manager applicati. The fields in this table ly apply when provisiing a user for the Onboard Manager applicati. Column Header Required Create Required Descripti OB_MANAGER_USER_TYPE* Yes No User type of the user in Onboard. The value MUST already exist in Onboard. Note: *This field name changed. It was previously called OB_USER_TYPE. Hiring Manager OB_USER_GROUP Yes No User group of the user in Onboard. The value MUST already exist in Onboard. Multiple user groups for the user are separated by *. (Each * counts as 3 characters towards the max character.) OB_USER_LOCATION No No Sets the locati of the user in Onboard. The value passed MUST be the EntryAlphaKey of the locati found in Onboard Alphanumeric. Standard Group * Group Local Talent Manager Performance Fields

9 To provisi a user for the Talent Manager Performance applicati, follow the instructis in the Talent Manager Performance Fields table. Table 6. Talent Manager Performance Fields. Use the Talent Manager Performance Fields table when provisiing a user for the Talent Manager Performance applicati. Column Header Required Create Required Descripti TM_PERFORMANCE_ACCESS Yes No This field determines whether or not the user is provisied for Talent Manager in the Talent Note: This field is ly required if you are trying to provisi the user for Talent Manager. This field supports the following states: ACTIVE = User is active in the system and will have access to the applicati through the Talent (We also support [1] for this state.) INACTIVE = User is inactive in the system and will not have access to the applicati through the Talent (We also support [0] for this state.) ACTIVE_NO_ACCESS = User is active in the system but will not have access to the applicati through the Talent 16 Alphanumeric. (Not case sensitive.) ACTIVE The following fields are required ly apply when provisiing a user for the Talent Manager Performance applicati. Table 7. Talent Manager Performance Hiring Fields used for provisiing a user for access to the Talent Manager Performance applicati. The fields in this table are required ly apply when provisiing a user for the Talent Manager Performance applicati. Column Header Required Create Required Descripti TM_PERFORMANCE_USER_TYPE* Yes No User type of the user in Talent Manager. The value MUST already exist in Talent Manager. The value MUST be e of the following: ADM = Administrator EMP

10 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 name changed. It was previously called TM_USER_TYPE. SENDER_EMPLOYEE_ID Yes No A valid Employee ID for a user that exists in Talent Manager for the integrati to work. 50 Alphanumeric. HRXMLUSER Talent Insights Fields To provisi a user for Talent Insights, follow the instructis in the Talent Insights Fields table. Table 8. Talent Insights Fields. Use the Talent Insights Fields table when provisiing a user for Talent Insights. Column Header Required Create Require Descripti TI_TALENT_INSIGHTS_ACCESS Yes No This field determines whether or not the user is provisied for Talent Insights in the Talent Note: This field is ly required if you are trying to provisi the user for Talent Insights. This field supports the following states: ACTIVE = User is active in the system and will have access to the applicati through the Talent (We also support [1] for this state.) INACTIVE = User is inactive in the system and will not have 16 Alphanumeric. (Not case sensitive.) ACTIVE

11 access to the applicati through the Talent (We also support [0] for this state.) ACTIVE_NO_ACCESS = User is active in the system but will not have access to the applicati through the Talent The following fields are ly applicable when provisiing a user for Talent Insights. Table 9. Talent Insights Field used for provisiing a user for to Talent Insights. The fields in this table are ly applicable when provisiing a user for Talent Insights. Column Header Required Create Required Descripti TI_TALENT_INSIGHTS_USER_TYPE* Yes No User type of the user in Talent Insights. The value MUST already exist in Talent Insights. HR Executive Note: *This field name changed. It was previously called. TI_ROLE_ID Yes No Unique ID that correspds to a specific user type in Talent Insights. 3 Numeric 1 Admin Applicati Fields To provisi a user for the Talent Suite Admin applicati, follow the instructis in the Admin Applicati Fields table. Table 10. Admin Applicati Fields. Use the Admin Applicati Fields table when provisiing a user for the Talent Suite Admin applicati. Column Header Required Create Required Descripti TS_ADMIN_ACCESS Yes No This field determines whether or not the user is provisied for Talent Suite Admin in the Talent 16 Alphanumeric. (Not case sensitive.) ACTIVE Note: This field is ly required if you are trying to provisi the user for Talent Suite Admin. This field supports the following states: ACTIVE = User is active in the system and will have access to

12 the applicati through the Talent (We also support [1] for this state.) INACTIVE = User is inactive in the system and will not have access to the applicati through the Talent (We also support [0] for this state.) ACTIVE_NO_ACCESS = User is active in the system but will not have access to the applicati through the Talent The following field is ly applicable when provisiing a user for the Talent Suite Admin applicati. Table 11. Talent Suite Admin Field used for provisiing a user for access to the Talent Suite Admin applicati. The fields in this table are ly applicable when provisiing a user for the Talent Suite Admin applicati. Column Header Required Create Required Descripti TS_ADMIN_USER_TYPE Yes No User type of the user in Talent The value MUST already exist in Talent IBM_ADMIN Talent Gateway Jobs field To provisi a user for the Talent Gateway Jobs applicati, follow the instructis in the Talent Gateway Jobs field table. Table 12. Talent Gateway Jobs field. Use the Talent Gateway Jobs field table when provisiing a user for the Talent Gateway Jobs applicati. Column Header Required Create Required Descripti BRTG_JOBS_ACCESS Yes No This field determines whether or not the user is provisied for Talent Gateway in the Talent 16 Alphanumeric. (Not case sensitive.) ACTIVE Note: This field is ly required if you are trying to provisi the user for Talent Gateway. This field supports the following states: ACTIVE = User is active in the system and will have access to

13 the applicati through the Talent (We also support [1] for this state.) INACTIVE = User is inactive in the system and will not have access to the applicati through the Talent (We also support [0] for this state.) ACTIVE_NO_ACCESS = User is active in the system but will not have access to the applicati through the Talent Cnectis Social Cloud field To provisi a user for the Cnectis Social Cloud applicati (the Social compents of the Talent Suite), follow the instructis in the Cnectis Social Cloud field table. Table 13. Cnectis Social Cloud field. Use the Cnectis Social Cloud field table when provisiing a user for the Cnectis Social Cloud applicati. Column Header Required Create Descripti Required CONNECTIONS_SOCIAL_CLOUD_ACCESS Yes No This field determines whether or not the user is provisied for Social in the Talent 16 Alphanumeric. (Not case sensitive.) ACTIVE Note: This field is ly required if you are trying to provisi the user for Social. This field supports the following states: ACTIVE = User is active in the system and will have access to the applicati through the Talent (We also support [1] for this state.) INACTIVE = User is inactive in the system and will not have access to the applicati through the Talent (We also support [0] for this state.) ACTIVE_NO_ACCESS = User is active in the system but will not have access to the applicati through the Talent

14 Expertise Manager fields To provisi a user for the Expertise Manager applicati, follow the instructis in the Expertise Manager Applicati Fields table. Table 14. Expertise Manager Applicati Fields. Use the Expertise Manager Applicati Fields table when provisiing a user for the Expertise Manager applicati. Column Header Required Create Required Descripti EM_ACCESS Yes No This field determines whether or not the user is provisied for Social in the Talent 16 Alphanumeric. (Not case sensitive.) ACTIVE Note: This field is ly required if you are trying to provisi the user for Social. This field supports the following states: ACTIVE = User is active in the system and will have access to the applicati through the Talent (We also support [1] for this state.) INACTIVE = User is inactive in the system and will not have access to the applicati through the Talent (We also support [0] for this state.) ACTIVE_NO_ACCESS = User is active in the system but will not have access to the applicati through the Talent The following field is ly applicable when provisiing a user for the Expertise Manager applicati. Table 15. Talent Suite Expertise Manager Field used for provisiing a user for access to the Expertise Manager applicati. The fields in this table are ly applicable when provisiing a user for the Expertise Manager applicati. Column Header Required Create Required Descripti EM_USER_TYPE Yes No User type of the user in Expertise Manager. EE Employee Voice Applicati Fields

15 To provisi a user for the Talent Suite Employee Voice applicati, follow the instructis in the Employee Voice Applicati Fields table. Table 16. Employee Voice Applicati Fields. Use the Employee Voice Applicati Fields table when provisiing a user for the Employee Voice applicati. Column Header Required Create Required Descripti EMPLOYEEVOICE_ACCESS Yes No Provisis the user for the Employee Voice applicati. This field determines whether or not the user is provisied for Employee Voice in the Talent 16 Alphanumeric. (Not case sensitive.) ACTIVE Note: This field is ly required if you are trying to provisi the user for Talent Suite Employee Voice. This field supports the following states: ACTIVE = User is active in the system and will have access to the applicati through the Talent (We also support [1] for this state.) INACTIVE = User is inactive in the system and will not have access to the applicati through the Talent (We also support [0] for this state.) ACTIVE_NO_ACCESS = User is active in the system but will not have access to the applicati through the Talent The following field is ly applicable when provisiing a user for the Employee Voice applicati. Table 17. Talent Suite Employee Voice Field used for provisiing a user for access to the Employee Voice applicati. The fields in this table are ly applicable when provisiing a user for the Employee Voice applicati. Column Header Required Create Required Descripti EMPLOYEEVOICE_USER_TYPE Yes No User type of the user in Employee Voice. Administrator (Gives the user access to cfigurati, respse 255 Single entry. Alphanumeric. Manager

16 rate, and reports in Manager Dashboard) Manager (Gives the user access to the respse rate and reports in Manager Dashboard) Ctent_Administrator (Gives the user access to all of Ctent Authoring) _Administrator (Gives the users access to Authoring) Use * to separate multiple selectis. Required ly if EMPLOYEEVOICE_ACCESS is set to 1. OrgMapper Applicati Fields To provisi a user for the Talent Suite OrgMapper applicati, follow the instructis in the OrgMapper Applicati Fields table. Table 18. OrgMapper Applicati Fields. Use the OrgMapper Applicati Fields table when provisiing a user for the OrgMapper applicati. Column Header Required Create Required Descripti OM_ACCESS Yes No Provisis the user for Organizatial Mapping. This field determines whether or not the user is provisied for OrgMapper in the Talent 16 Alphanumeric. (Not case sensitive.) ACTIVE Note: This field is ly required if you are trying to provisi the user for Talent Suite OrgMapper. This field supports the following states: ACTIVE = User is active in the system and will have access to the applicati through the Talent (We also support [1] for this state.)

17 INACTIVE = User is inactive in the system and will not have access to the applicati through the Talent (We also support [0] for this state.) ACTIVE_NO_ACCESS = User is active in the system but will not have access to the applicati through the Talent The following field is ly applicable when provisiing a user for the OrgMapper applicati. Table 19. Talent Suite OrgMapper Field used for provisiing a user for access to the OrgMapper applicati. The fields in this table are ly applicable when provisiing a user for the OrgMapper applicati. Column Header Descripti Required Create Required OM_USER_TYPE Yes No User type of the user in OrgMapper. Identifies the user s Organizatial Mapping User Group. Administrator (Gives the user access to all functiality in OrgMapper.) Coordinator (Gives the user access to everything in OrgMapper except data import and cfigurati.) Only accepts e value, the value MUST be from the preceding list. Required ly if OM_ACCESS is set to Single entry. Alphanumeric. Coordinator OM_ORG_SECURITY_LEVEL Yes No Identifies the user's security level at the organizati level. Required ly if OM_ACCESS is set to 1. The default value is ALL. ALL provides access to all nodes within the customer instance of OrgMapper. From customer Employee Bob Smith Employee ID = P0001 A user set setup with OM_ORG_SECURITY_LEVEL = P0001 The user has access to the entire record for ly 'Bob Smith' in OrgMapper and his entire downline.

18 The field value to reference for OM_ORG_SECURITY_LEVEL comes from the customer OrgMapper data file Employee ID field. If no value is provided, use Default Value of ALL. If an Employee ID is provided within a higher security level, it is assumed as having the higher access. Use * to separate multiple selectis. Alternate : A user is setup with OM_ORG_SECURITY_LEVEL = ALL The user has access to all records in their instance of OrgMapper. Note: A check is needed to have in place to prevent the client from going over the limit as this might be possible in the near future. Upload the CSV file to the Talent Suite 1. Once the.csv file has been created and is ready to upload to the Talent Suite, select the Browse butt in the Select CSV file field. The File Upload dialog window opens. Figure 1. File Upload (Browse to select CSV file)

19 2. In the File Upload dialog box, navigate to the locati of the.csv Import Users Specificatis file created following the process steps in the User Provisiing, Import and Management and Creating the.csv File sectis. 3. Select the.csv Import Users Specificatis file and then select Open. The file will upload to the Talent 4. Select the.csv Import Users Specificatis file and then select Open. The file then uploads to the Talent The.csv file appears in the Select CSV file field the Import Users page. Figure 2. Import Users page Uploaded CSV file

20 5. Select the Import butt to import the file into the Talent A message dialog window displays with a message asking the user if they wish to proceed. Are you sure you want to import this 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.

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