v_personnel_employment_history

v_personnel_employment_history

Purpose

  1. Personnel employment history records.


Relationships

  • v_personnel: Many-to-One (N:1)

    • Many history records link to one personnel

    • Referenced through user_id

  • v_fire_dept_user: Many-to-One (N:1)

    • Many history records created by one user

    • Referenced through created_by




Table



Column

Type

Description

id

integer

Primary key

event_date

date

Event date

event_type_code

varchar(100)

Event type

notes

text

Event notes

client_code

varchar(28)

Organization ID

created_by

varchar(255)

Creator name

user_id

integer

User reference

rank

varchar(100)

Rank at time



    • Related Articles

    • Personnel Record: Employment History Tab

      Purpose Statement The Employment History section provides a comprehensive tracking system for personnel career progression, assignment changes, and significant employment events within your department. This feature enables supervisors and ...
    • v_personnel_pay_rate

      Purpose Personnel pay rate history. Relationships v_personnel: Many-to-One (N:1) Many pay rates link to one personnel Referenced through personnel_id v_fire_dept_user: Many-to-One (N:1) Many pay rates link to one user Referenced through user_id Table ...
    • v_personnel_nemsis

      Purpose Personnel NEMSIS certification details. Relationships v_personnel: Many-to-One (N:1) Many NEMSIS records link to one personnel Referenced through personnel_id v_personnel_nemsis_licensure: One-to-Many (1:N) One NEMSIS record can have many ...
    • Viewing Call Shift History

      Purpose Statement The Call Shift History feature provides a comprehensive view of all call shifts within your department, allowing administrators and supervisors to track call shift activities, monitor response patterns, and maintain detailed records ...
    • v_personnel

      Purpose Personnel information and assignments. Relationships v_fire_dept_user: One-to-One (1:1) One personnel links to one user account Referenced through id/personnel_id f_all_schedule: One-to-Many (1:N) One personnel can have many schedules ...