Export & Import Requirements
Used to make bulk Adds and Changes and to the Requirements.
On this page:
| Table of Contents |
|---|
Export
Use the Export button (e.g.)
Will download an Excel Worksheet to a folder as per your browser setup
The excel worksheet can then be edited with the necessary changes
Imports use the Requirement Unique Reference as the key for Imports
Import
Use the Import button (e.g.)
If you are NOT using a previously Exported Excel spreadsheet then you will need to first download a Bulk Template using the Download Bulk Template button
Use it to prepare an Import file
Choose the type of Upload option:
Insert & Update (Default) - Will Insert any Requirement with a new Unique Reference and update any existing Requirements based on the Unique References in the Import file.
Insert Only - Will Insert any Requirement with a new Unique Reference only
Update Only - Will update any Requirement with existing Unique References only
Select the (prepared) Files you wish to import
Select the Perform to Upload button
Refresh the Import Queue to view the current status of the Import
Track the Import status by Refreshing both the Requirements table as well as the Requirements Import Queue at intervals
Once the Import has completed Refresh the Requirement List to show the updated Requirements and Meta Data, and if needed use the Search to filter what you wish to view.
| Note |
|---|
During the Import the process calculates matching % for all users. Therefore, imports can take a while. It is dependent on the number of users, so especially for work-spaces with 100+ users, expect it to take a while. Note: The Owner field is ignored during an Import. Refer: https://skillstx.atlassian.net/wiki/spaces/TXADM/pages/2221506669/6.2+Export+Import+Requirement#Format2221506669#Format-of-the-Import-File%2FTemplate |
Format of the Import File/Template
(* - Indicates a Compulsory field). Many of the fields are optional, and free format text, so able to be used as preferred by the organization. Some fields are Select-able, and have specific values that can be selected.
Some fields which are “Select-able”, have specific values that can be selected. Two of these values:
Other (Please Comment)
Not Applicable
Are legacy values based on a previous (no longer used) ability to make use of surveys to generate Requirements, and are provided for compatibility reasons. For new Requirements they can be ignored, and the field rather left blank.
Column Name | Options | Description | ||
|---|---|---|---|---|
Name* | Name of the Requirement | Must be unique | ||
Seniority* (Select-able) |
| The seniority of the Role that this Requirement applies to | ||
Employment Status* (Select-able) |
| The employment status of the Role that this Requirement applies to | ||
Unique Reference* | Reference Number | Must be unique | ||
Customer reference | For use as required | Non-unique. e.g. HR Reference | ||
ReportingTo | Name of a role (or person) | Usually refers to a role that the role for this Requirement would report to. Could be the name of a person, but this would require extra maintenance for changes | ||
Department | Name of a department | Name of a department or business area to which this Requirement could be assigned | ||
Location | Location name | Name of a location. Often business office, or city name is used | ||
Purpose | Purpose of the Requirement | An overview purpose for this Requirement. Equivalent of a Job/Role purpose overview | ||
Key Accountabilities | List of accountabilities | List of accountabilities this requirement is required to fulfill | ||
Key Processes | List of Processes | List of processes this requirement is involved in | ||
Education Requirements | Education Requirements | e.g. Bachelor Computer Science | ||
Qualification Requirements | Qualification Requirements | e.g. Prince 2 Certification | ||
Other Requirements | Other Requirements | Other requirements specific to the role | ||
Who Can See* (Select-able) |
| Who is able to be assigned the Requirement or select for themselves | ||
Inactive* (Select-able) |
| Setting a Requirement to Inactive is designed for the development stage of a Requirement. When a Requirement is set to Inactive:
| ||
LoR Addressed or Blank |
| Must be in the format of AUTOn, INFLn, COMPn,KLGEn, BSKLn (separated by commas) where “n” is the valid Attribute level (between 1-7) | ||
Required Skills Addressed or Blank |
| Required Skills for the Requirement Must be valid Skill Codes and Levels separated by commas. E.g. PRMG4, USUP3 | ||
Desirable Skills Addressed or Blank |
| Desirable Skills for the Requirement (Cannot be a duplicates of Required skills/Levels as per above) Must be valid Skill Codes and Levels separated by commas. E.g. QUMG4,QUAS3 | ||
Default Language | One of the Languages available:
| When the Default language is set, then the Requirement Report will be translated into the Default Language selected. If Blank then it will report in English.
| ||
Owner | The name of the owner if someone has been selected. | The person selected as the owner of the Requirement.
| ||
Include in Self Registration Role Based Survey |
| Set - Yes, if this Role is to be included in a selection specifically for Self-Registration. Used in conjunction with Self-Registration feature. Refer: https://skillstx.atlassian.net/wiki/spaces/TXADM/pages/2221506615/17.+Manage+Features+Settings#Self-Registration-feature |
Related Help pages
| Filter by label (Content by label) | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|