This page (revision-15) was last changed on 17-Apr-2024 16:29 by Kevin Higgs

This page was created on 26-Nov-2021 10:22 by Kevin Higgs

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note
15 17-Apr-2024 16:29 10 KB Kevin Higgs to previous
14 23-Feb-2024 16:02 9 KB Kevin Higgs to previous | to last
13 23-Feb-2024 15:58 9 KB Kevin Higgs to previous | to last
12 23-Feb-2024 13:32 9 KB Kevin Higgs to previous | to last
11 23-Feb-2024 13:30 9 KB Kevin Higgs to previous | to last
10 23-Feb-2024 13:24 9 KB Kevin Higgs to previous | to last
9 31-Aug-2022 17:24 7 KB Karen Parrott to previous | to last
8 26-Nov-2021 10:22 6 KB Karen Parrott to previous | to last
7 26-Nov-2021 10:22 6 KB Karen Parrott to previous | to last
6 26-Nov-2021 10:22 6 KB Karen Parrott to previous | to last
5 26-Nov-2021 10:22 6 KB Kevin Higgs to previous | to last
4 26-Nov-2021 10:22 6 KB Kevin Higgs to previous | to last
3 26-Nov-2021 10:22 5 KB Kevin Higgs to previous | to last
2 26-Nov-2021 10:22 3 KB Kevin Higgs to previous | to last
1 26-Nov-2021 10:22 2 KB Kevin Higgs to last

Page References

Incoming links Outgoing links
XDCE...nobody
XDCE

Version management

Difference between version and

At line 3 changed 12 lines
!!Purpose
Customers using NEOGOV products can synchronize their data from Personality.\\
\\
__NEW HIRE Feed From NEOGOV to Personality__- To create a data feed __FROM__ NEOGOV, personality customers require both Insight and Onboard. The feed provided can be loaded into Personality using [UEINH].\\
\\
To send data to NEOGOV "TMS" products, clients can create data feeds for Position and Employee records.\\
\\
__Employee Data__ - Clients must have purchased at least one of the following products to be able to synchronize employee information;\\
*Onboard
*Eforms
*Learn
*Perform
!!!PURPOSE
At line 16 changed 7 lines
The employee data feed is maintained via the [UEEF] program with a pre-defined interface supplied within the system on [IDIF] called "HL$NGV_LEARN". \\
\\
__Position Data__ - Clients using any TMS product would be able to send Position updates from Personality to NEGOV TMS.\\
\\
The __XDCE__ program creates the data feed required to maintain position information within NEOGOV TMS. The extract is created in the form of multiple .csv files created on the clients database server in a predefined layout mapped based on the NEOGOV system requirements.
The XDCE program creates an extract in the form of a .csv from Personality in a predefined layout for importing to the NEOGOV system.
At line 25 removed 2 lines
Sample over view of options for interfacing with NEOGOV products - [XDCE/Extract Options.jpg]
At line 43 removed one line
\\
At line 45 removed one line
\\
At line 47 changed 3 lines
||Report Parameters ||Description
|Departments |Mandatory, Lexicon (Yes or No) - Select Yes if you wish for a Department extract file to be created.\\ The filename will be SITE_CODE_dept_YYYYMMDD.csv
|Divisions |Mandatory, Lexicon (Yes or No) - Select Yes if you wish for a Division extract file to be created.\\ The filename will be SITE_CODE_div_YYYYMMDD.csv
||Report Parameters ||Description
|Departments |Mandatory, Lexicon (Yes or No) - Select Yes if you wish for a Department extract file to be created.\\ The filename will be SITE_CODE_dept_YYYYMMDD.csv
|Divisions |Mandatory, Lexicon (Yes or No) - Select Yes if you wish for a Division extract file to be created.\\ The filename will be SITE_CODE_div_YYYYMMDD.csv
At line 51 removed one line
|Positions |Mandatory, Lexicon (Yes or No) - Select Yes if you wish for a Position extract file to be created.\\ The filename will be SITE_CODE_pos_YYYYMMDD.csv
At line 53 changed 6 lines
|As of Date |Optional, Date - Extract the records that are effective as of this date
|Department Status|Lexicon - This will filter the records in the extract according to the selected status.\\ If no value selected on the parameter, the process will extract records that have the status null.
|Division Status|Lexicon - This will filter the records in the extract according to the selected status.\\ If no value selected on the parameter, the process will extract records that have the status null.
|Class Spec Status|Lexicon - This will filter the records in the extract according to the selected status.\\ If no value selected on the parameter, the process will extract records that have the status null.
|Position Status|Lexicon - This will filter the records in the extract according to the selected status.\\ If no value selected on the parameter, the process will extract records that have the status null.
|Exception Level |Values of ‘0’ to ‘9’ (more exception messages are displayed when a higher level number is used)
|Positions |Mandatory, Lexicon (Yes or No) - Select Yes if you wish for a Position extract file to be created.\\ The filename will be SITE_CODE_pos_YYYYMMDD.csv
|Exception Level |Values of ‘0’ to ‘9’ (more exception messages are displayed when a higher level number is used)
At line 60 removed one line
\\
At line 62 changed 62 lines
\\
!DEPARTMENTS
\\
||Personality Field ||NEOGOV Mapping ||Notes
|ddp.department_code |DepartmentCode |From [IDDP]
|ddd.department_name |DepartmentName |From the detail record of [IDDP]
|dln.address_line_1 |Address1 |Based on the [DLN_ID] associated to the the [IDDP]
|dln.address_line_2 |Address2 |Based on the [DLN_ID] associated to the the [IDDP]
|dln.locality |City |Based on the [DLN_ID] associated to the the [IDDP]
|dsp.state_province_code |State |Based on the [DSP_ID] found on the [DLN_ID] associated to the the Department
|dln.zip_postal |ZipCode |Based on the [DLN_ID] associated to the the [IDDP]
|dln.phone_number |Phone1 |Based on the [DLN_ID] associated to the the [IDDP]
|dln.alt_phone_number |Phone2 |Based on the [DLN_ID] associated to the the [IDDP]
|Not Used in Personality |WebSiteURL |There is currently no corresponding column
|ddp.standing |Status |Standing of Active will be return '1', all other values will return '2'
\\
!DIVISIONS
||Personality Field ||NEOGOV Mapping ||Notes
|ddv.division_code |DivisionCode |From [IDDV]
|ddv.division_name |DivisionName |From [IDDV]
|ddp.department_code |Department |From [IDDP]
|ddv.division_status |Status |From [IDDV]. Value of lexicon [X_STANDING]. Saved value of "Active" will be return '1', all other values will return '2'
\\
\\
!CLASS SPECIFICATIONS
||Personality Field ||NEOGOV Mapping ||Notes
|djb.job_code |ClassCode |From IDJB
|djd.effective |EstablishedDate |Latest date effective record found on IDJB
|djd.job_title |ClassTitle |From the recruiting tab found on the detail record of IDJB
|djd.class_concept |ClassConcept |From the recruiting tab found on the detail record of IDJB
|djd.example_of_duties |ExampleOfDuties |From the recruiting tab found on the detail record of IDJB
|djd.minimum_qualifications |MinimumQualifications |From the recruiting tab found on the detail record of IDJB
|djd.supplemental_info |SupplementalInfo |From the recruiting tab found on the detail record of IDJB
|djd.other_requirements |OtherRequirements |From the recruiting tab found on the detail record of IDJB
|djd.other_title_1 |OtherTitle1 |From the recruiting tab found on the detail record of IDJB
|djd.ngv_salary_min |SalaryMin |From the recruiting tab found on the detail record of IDJB
|djd.ngv_salary_max |SalaryMax |From the recruiting tab found on the detail record of IDJB
|djd.billable_hours |BillableHours |Lexicon X_BILLABLE_HOURS From the Recruiting Tab found on the detail record of IDJB
|djd.rate_basis |SalaryPaidCode |Lexicon X_RATE_BASIS\\*'HR' = 'Hour'\\*'MO' = 'Month'\\*'YR' = 'Year'\\*'BW' = 'BiWeekly'\\*'WK' = 'Week'\\*'SM' = 'Semi-month'\\*'DY' = 'Day'
|djd.show_salary_hourly |SalaryBreakdownHourly |Toggle found on IDJB
|djd.show_salary_daily |SalaryBreakdownDaily |Toggle found on IDJB
|djd.show_salary_weekly |SalaryBreakdownWeekly |Toggle found on IDJB
|djd.show_salary_biweekly |SalaryBreakdownBiweeky |Toggle found on IDJB
|djd.show_salary_semimonthly |SalaryBreakdownSemiMonthly |Toggle found on IDJB
|djd.show_salary_monthly |SalaryBreakdownMonthly |Toggle found on IDJB
|djd.show_salary_annually |SalaryBreakdownAnnually|Toggle found on IDJB
|dun.unit_code |BargainingUnitCode |Unit Code found on the IDJB
|'N/A' |PhysicalClassCode |There is currently no corresponding column
|rnb.benefits_code |BenefitCode |From the recruiting tab found on the detail record of IDJB. Set up on the [IRNB] Maintain NGV Benefits form
|doc.occupation_code |OccupationalGroupCode |From the recruiting tab found on the detail record of IDJB. Set up on the [IDOC] Define Occupation Code form
|djd.ngv_flsa |FLSA |Lexicon X_NGV_FLSA "Exempt" or "Non-Exempt"
|djd.eeo_category |EEO |Lexicon X_EEO_CATEOGRY found on the detail record of IDJB
|djd.job_interest_cards |AcceptJobInterestCards |From the recruiting tab found on the detail record of IDJB. Toggle
|djd.notes |Notes |From the recruiting tab found on the detail record of IDJB.
\\
\\
!OCCUPATIONAL GROUPS
||Personality Field ||NEOGOV Mapping ||Notes
|doc.Occupation_code |OccupationCode |
|doc.occupation_group |OccupationalGroup |Lexicon X_OCCUPATION_GROUP
|doc.description |Description |
|No DB VALUE |1 |Defaults to value of '1'. No DB VALUES
!Departments
||Personality Field ||NEOGOV Mapping ||Notes
|ddp.department_code |DepartmentCode |From IDDP
|ddd.department_name |DepartmentName |From the detail record of IDDP
|dln.address_line_1 |Address1 |Based on the DLN_ID associated to the the IDDP
|dln.address_line_2 |Address2 |Based on the DLN_ID associated to the the IDDP
|dln.locality |City |Based on the DLN_ID associated to the the IDDP
|dsp.state_province_code |State |Based on the DSP_ID found on the DLN_ID associated to the the Department
|dln.zip_postal |ZipCode |Based on the DLN_ID associated to the the IDDP
|dln.phone_number |Phone1 |Based on the DLN_ID associated to the the IDDP
|dln.alt_phone_number |Phone2 |Based on the DLN_ID associated to the the IDDP
|Not Used in Personality |WebSiteURL |There is currently no corresponding column
|ddp.standing |Status |Standing of Active will be return '1', all other values will return '2'
At line 125 changed 20 lines
!POSITIONS
||Personality Field ||NEOGOV Mapping ||Notes
|dps.position_code|PositionCode|Code or Unique Identifier for this Position Code. This will be used as the primary key for updates to this record. If this code already exists in Insight it will be updated. Otherwise, a new record will be created.
|dps.standing|Active|Send A or I (A = Active I = Inactive) \\ \\__NOTE: Positions that are “Active” will be available on the Requisitions page__
|dpd.dps_id_reporting_to|ReportsToPosition|The position code of the parent position that this job reports to. \\This position code must exist in Insight before being linked.\\ It is a view only field. \\ __NOTE: To make a functional direct manager relationship, use the employee import. The ReportsToPosition information is not functionally displayed in NEOGOV.__
|dps.standing|PositionStatus|Send A, E, G, P, F, V, I, or FI \\A = Approved\\E = Eliminated\\ G = Generated \\ P = Proposed \\ F = Frozen \\ V = Vacant \\ I = Inactive \\ FI = Filled
|ddp.department_code|DepartmentCode|(Level 1) The code of the department that exists in Insight (Admin/Definition Tables/Departments)
|ddv.division_code|DivisionCode|(Level 2) The code of the division that exists in Insight. It should also belong to the corresponding Department. (Admin/Definition Tables/Division)
|dun.unit_code|BargainingUnitCode|The code of the Bargaining Unit that exists in Insight (Admin/Definition Tables/Bargaining Unit)
|dpd.std_hours_per_pay|StandardHours|Hours per week, bi-weekly, monthly, etc. Must be a whole number only.
|Null|MaxHeadCount|Maximum headcount for this position Must be a whole number only.
|Null|CurrentHeadCount|Current headcount for this position Must be a whole number only.
|dpd.authorized_fte|MaximumFTE|Maximum FTE for this position. Must be a number only, can include up to 2 decimals.
|Null|CurrentFTE|Current FTE for this position. Must be a number only, can include up to 2 decimals.
|dpd.position_title|JobTitle|Position Title
|NULL|JobTermCode|If Onboard is implemented, this is the Position Type Code located in Positions/Positions Types. If only Insight is implemented, this is the code for Job Type that exists in Insight under Admin/Definition Tables/Job Types.
|dpd.djb_id|ClassCode|(optional)Code or Unique Identifier for the Job Class. This is an optional column that can be configured per agency. If included, values are expected. If not included, import file should not include column.
----
![Notes|Edit:Internal.XDCE]
[{InsertPage page='Internal.XDCE' default='Click to create a new notes page'}]
!Divisions
||Personality Field ||NEOGOV Mapping ||Notes
|ddv.division_code |DivisionCode |
|ddv.division_name |DivisionName |
|ddp.department_code |Department |
|ddv.division_status |Status |Standing of Active will be return '1', all other values will return '2'
!Class Specifications
||Personality Field ||NEOGOV Mapping ||Notes
|djb.job_code |ClassCode |From IDJB
|djd.effective |EstablishedDate |Latest date effective record found on IDJB
|djd.job_title |ClassTitle |From the recruiting tab found on the detail record of IDJB
|djd.class_concept |ClassConcept |From the recruiting tab found on the detail record of IDJB
|djd.example_of_duties |ExampleOfDuties |From the recruiting tab found on the detail record of IDJB
|djd.minimum_qualifications |MinimumQualifications |From the recruiting tab found on the detail record of IDJB
|djd.supplemental_info |SupplementalInfo |From the recruiting tab found on the detail record of IDJB
|djd.other_requirements |OtherRequirements |From the recruiting tab found on the detail record of IDJB
|djd.other_title_1 |OtherTitle1 |From the recruiting tab found on the detail record of IDJB
|djd.ngv_salary_min |SalaryMin |From the recruiting tab found on the detail record of IDJB
|djd.ngv_salary_max |SalaryMax |From the recruiting tab found on the detail record of IDJB
|djd.billable_hours |BillableHours |Lexicon X_BILLABLE_HOURS From the Recruiting Tab found on the detail record of IDJB
|djd.rate_basis |SalaryPaidCode |Lexicon X_RATE_BASIS\\*'HR' = 'Hour'\\*'MO' = 'Month'\\*'YR' = 'Year'\\*'BW' = 'BiWeekly'\\*'WK' = 'Week'\\*'SM' = 'Semi-month'\\*'DY' = 'Day'
|djd.show_salary_hourly |SalaryBreakdownHourly |Toggle found on IDJB
|djd.show_salary_daily |SalaryBreakdownDaily |Toggle found on IDJB
|djd.show_salary_weekly |SalaryBreakdownWeekly |Toggle found on IDJB
|djd.show_salary_biweekly |SalaryBreakdownBiweekly |Toggle found on IDJB
|djd.show_salary_semimonthly |SalaryBreakdownSemiMonthly |Toggle found on IDJB
|djd.show_salary_monthly |SalaryBreakdownMonthly |Toggle found on IDJB
|djd.show_salary_annually |SalaryBreakdownAnnually |Toggle found on IDJB
|dun.unit_code |BargainingUnitCode |Unit Code found on the IDJB
|'N/A' |PhysicalClassCode |There is currently no corresponding column
|rnb.benefits_code |BenefitCode |From the recruiting tab found on the detail record of IDJB. Set up on the [IRNB] Maintain NGV Benefits form
|doc.occupation_code |OccupationalGroupCode |From the recruiting tab found on the detail record of IDJB. Set up on the [IDOC] Define Occupation Code form
|djd.ngv_flsa |FLSA |Lexicon X_NGV_FLSA "Exempt" or "Non-Exempt"
|djd.eeo_category |EEO |Lexicon X_EEO_CATEOGRY found on the detail record of IDJB
djd.job_interest_cards |AcceptJobInterestCards |
djd.notes |Notes
This page (revision-15) was last changed on 17-Apr-2024 16:29 by Kevin HiggsTop