An initial population of application data is possible
using a formatted CSV file. The location and naming of each of the
required folders is located in the <installation directory>\configuration\integration.properties.
The import process is an unattended process. Results of the import
are found in Activity Log located in Setup > System.
- Obtain a sample person import data
file (import-person-sample.csv) from the distribution in the
\integration\samples\ folder.
- You must have the Authority permission Import Manager: Full
Access to process imports in the
\integration\import\ folder.
- To start the Import Manager, set the field Run Import Manager
as to <self> located in Setup System > Import
Manager > Initial Import.
| Important Import Information |
- CSV is the required format. If the
file format is changed to facilitate populating the data, the end
result must be in the formatted CSV file provided - otherwise the
import manager will not process the file.
- Do not rename columns. Column titles are case sensitive.
- Do not change the format. Columns must be formatted correctly.
- Do not add alternate data formats. Alternate data formats are
not supported.
- Data entry and labels must be consistent to prevent the creation
of duplicate items. For example, if you inadvertently import a shift
labeled ‘S1:Shift1’ and ‘S1:Shift 1’ two distinct
shifts will be created. If you label the same region ‘R1:Region
1’ and then somewhere else in the file you have ‘R1:Reg1’
then you will create two entirely distinct regions which could result
in a re-import.
- Use concise labels when possible. For example, use TTh instead
of Tuesday and Thursday.
- When labeling items in the application be sure that labels
make sense in a staffing environment and fit staffing configuration
requirements.
- When feeding application data to a third-party system use the
same naming conventions for the required fields only; for example,
if the third-party system requires a shift labeled ‘E123’, and end-users
know this shift as ‘Evenings’, use the shift abbreviation field
to hold the ‘E123’ requirement and use the shift long name field
to hold the name ‘Evenings’; for example: E123:Evenings
|
| Real-Time Update |
- Importing data can overwrite existing
application data. Before you import review and set Import Manager
settings as desired in System > Import Manager> People Data Settings.
- Before running an import, be sure to back up the < application
name > database.
|
| - - - Institution Focus and Timezones - - - |
| All institutions and shifts must exist prior
to subsequent imports. This means if you are using the Import Manager
to update the database, any new Institution or Shift must exist
and have a shift or institution association in the database prior
to import. |
To import personnel and structure:
- Populate the Person-In CSV file with your data.
The default application configuration is set for performing
initial imports.
- Place your Person-In CSV file in the integration\import\person.in folder.
- The application looks for a new file on a periodic basis
and will begin to process the file.
- Check the <installation directory>\integration\import\person.processed folder
for successful imports and
person.errors folder
for failed imports.
Data from the spreadsheet is imported into the application;
mapped data elements from the file have been created or updated.