Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
A AIS modular
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Metrics
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Matthew Chavez
  • AIS modular
  • Wiki
    • Clearance
  • Technical Debt

Technical Debt · Changes

Page history
Multiple Updates: authored Jun 17, 2021 by Matthew Chavez's avatar Matthew Chavez
Clearance Wiki:
- Added Form Types to Overview
- Added Route Types to Overview
- Added Improved Hr/SuperUser management in Tech debt
- Modified Clearance Route insertion in Tech debt
Hide whitespace changes
Inline Side-by-side
Showing with 25 additions and 1 deletion
+25 -1
  • clearance/Technical-Debt.md clearance/Technical-Debt.md +25 -1
  • No files found.
clearance/Technical-Debt.md
View page @ f8f561b3
...@@ -93,4 +93,28 @@ Sales Logistic Department has many BU/Teams under its wing, and those BU or Busi ...@@ -93,4 +93,28 @@ Sales Logistic Department has many BU/Teams under its wing, and those BU or Busi
## Tech Debt 3: Clearance Routes is inserted on clearance submit application . ## Tech Debt 3: Clearance Routes is inserted on clearance submit application .
This is an old tech debt that I am fully aware of since the day of implementation but unable to publish the updates due to the requirements being requested occasionally outdating the pending updates further more. This is an old tech debt that I am fully aware of since the day of implementation but unable to publish the updates due to the requirements being requested occasionally outdating the pending updates further more.
\ No newline at end of file
[Routes](##) are automatically inserted once the employee have field their clearance application form. This have both advantage and disadvantages.
The advantage of doing this implementation are the following:
- The HR/Superuser would be able to identify the routes immediately using the `sql script` used to retrieve the clearance applications. See [Image: Dashboard Route Summary](images/dashboard-route-summary.png).
- Doing so will hasten the clearance status updating of the HR/Superuser as the route insertion is done on the clearance application filing instead of routing phase.
The disadvantages of doing this implementation are the following:
- The HR/Superuser won't be able to change the [Route](##) currently inserted to the clearance. This will require a SuperAdmin/MIS intervention to manipulate the route.
- A related **Tech debt** will be needing this feature to be implemented. See [Improved HR/SuperUser management](##).
## Tech Debt 4: Improved HR/SuperUser management
This Tech Debt is pending feature that has been abruptly requested a long time ago has not been not taken notice as it is only considered a **"*nice to have feature*"**.
This feature composes of a fine grained control over the clearance application form drastically reducing the interference of MIS support to the module. See image below for layout draft:
<center><img src="/clearance/images/" width="700"></center>
The prospect feature composes of the following:
- This will be able to add, edit and delete a [Route](##) that is currently assigned to the clearance.
- Separate tab to update the Employee clearance application form details allowing the HR/SuperUsers to focus only to the important detail.
- Separate tab for the routing process. This will fine grain the clearance logging to be saved in the clearance row in the database such as **"Timestamp Routed"**, **"Timestamp completely Routed"**, **"Timestamp processed"** and **Timestamp modified**.
\ No newline at end of file
Clone repository
  • Hubstaff
    • Common Support and Issues
    • Overview
  • Warehouse Delivery Tracking (WDT API Only)
    • Common Support and Issues
    • Overview
    • Technical Debt
  • clearance
    • Common Support and Issues
    • Overview
    • Technical Debt
  • Home