HRQB 57 - many-to-one relationships for LibHR table #201
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Purpose and background context
This PR allows the
LibHR Employee Appointments
table to have multiple rows for employee and/or headcount ID (HC ID
). This allows a headcount ID likeL-001
to have multiple rows, where new columnsBegin Date
andEnd Date
will show when that headcount ID was applied and to whom.In turn, this supports reports in Quickbase that show the employee's associated with a single headcount ID, vacancy reports, etc.
Includes new or updated dependencies?
YES:
cryptography
had a required update forsafety
vulnerabilityNOTE: other dependencies were not updated at this time, as updates to
mypy
andruff
are bringing lots of linting errors. This will be handled in a future maintenance update.Changes expectations for external applications?
YES: Quickbase receiving new data
What are the relevant tickets?
Developer
Code Reviewer(s)