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
  • Common Support and Issues

Common Support and Issues · Changes

Page history
Multiple Updates: authored Jun 17, 2021 by Matthew Chavez's avatar Matthew Chavez
* Fixed Clearance skeletal layout
* Added proper references to the clearance wiki
* Added WDT Skeletal layout
Show whitespace changes
Inline Side-by-side
Showing with 23 additions and 15 deletions
+23 -15
  • clearance/Common-Support-and-Issues.md clearance/Common-Support-and-Issues.md +23 -15
  • No files found.
clearance/Common-Support-and-Issues.md
View page @ 4ee478ab
<!-- EXTERNAL REDIRECT LINKS -->
[#external-link:ais]: https://ais.amti.com.ph "Redirect link to AMTI Integrated System"
[#external-link:ais-hierarchy]: https://ais.amti.com.ph/hierarchy "Redirect link to hierarchy module"
[#external-link:ais-users]: https://ais.amti.com.ph/user "Redirect link to AIS user module"
[#external-link:ais-signatory-managmenet]: https://ais.amti.com.ph/clearancesu/view "Redirect link to AIS signatory management"
[#external-link:ais-clearance-application-form-onsite]: https://ais.amti.com.ph/clearance/onsite "Redirect link to Clearance application"
[100]: https://gitlab.amti.com.ph/matthew.chavez/ais-modular/-/wikis/clearance/Clearance-Technical-Debt "Link to Clearance Tech Debts"
[101]: https://gitlab.amti.com.ph/matthew.chavez/ais-modular/-/wikis/clearance/Clearance-Technical-Debt#tech-debt-2-sales-logistics-special-conditions "Link to Sales Logistics special conditions"
[102]: https://gitlab.amti.com.ph/matthew.chavez/ais-modular/-/wikis/clearance/Clearance-Technical-Debt#tech-debt-1-approver-and-route-management "Link to Approver and Route Management Technical Debt"
<!-- WIKI REDIRECT LINK -->
[#tech-debt]: https://gitlab.amti.com.ph/matthew.chavez/ais-modular/-/wikis/clearance/Clearance-Technical-Debt "Link to Clearance Tech Debts"
[#tech-debt:sales-logistics]: https://gitlab.amti.com.ph/matthew.chavez/ais-modular/-/wikis/clearance/Clearance-Technical-Debt#tech-debt-2-sales-logistics-special-conditions "Link to Sales Logistics special conditions"
[#tech-debt:route-management]: https://gitlab.amti.com.ph/matthew.chavez/ais-modular/-/wikis/clearance/Clearance-Technical-Debt#tech-debt-1-approver-and-route-management "Link to Approver and Route Management Technical Debt"
## ⚠️ SCENARIO: Adding/Removing a Standard Route (HO & Onsite)
......@@ -12,7 +20,7 @@
#### ✓ ADDING STANDARD ROUTE
1. Go to AIS and access the [System Admin > Hierarchy.](https://ais.amti.com.ph/hierarchy "link to hierarchy module")
1. Go to AIS and access the [System Admin > Hierarchy.][#external-link:ais-hierarchy]
2. Click the **+ Add Hierarchy** on the upper left side of the page to add Department/Route.
<center><img src="/clearance/images/add_hierarchy.png" width="250"></center>
......@@ -50,7 +58,7 @@ EXAMPLE:
<center><img src="/clearance/images/add_standard_route.png" width="700"></center>
#### ✓ REMOVING/ARCHIVE STANDARD ROUTE
1. Go to AIS and access the [System Admin > Hierarchy.](https://ais.amti.com.ph/hierarchy "link to hierarchy module")
1. Go to AIS and access the [System Admin > Hierarchy.][#external-link:ais-hierarchy]
2. Search the department/route to be removed in the standard routes
3. Click the archive module represented with **[-]** button.
......@@ -71,8 +79,8 @@ Before **adding** department concerned to the clearance forms. Please refer to t
**CHECKLIST BEFORE ADDING:**
* **Head Office Department Concerned:**
Before adding department concerned for Head Office (HO). We must first consider the following to the requestor which is mostly the **HR/SuperUser**.
* [✓] Department Approver(s) must have an existing and active account in [AIS](https://ais.amti.com.ph "Redirect link to AMTI Integrated System")
* [✓] Approver(s) must have an existing and active AMTI Email account connected to its [User account](https://ais.amti.com.ph/user "Redirect link to AIS user module")
* [✓] Department Approver(s) must have an existing and active account in [AIS][#external-link:ais]
* [✓] Approver(s) must have an existing and active AMTI Email account connected to its [User account][#external-link:ais-users]
* [✓] Approver(s) must be advised that he/she will be a clearance approver.
......@@ -86,7 +94,7 @@ Apart from this Approver rules. Some specific considerations should be kept in m
#### ✓ ADDING DEPARTMENT CONCERNED FOR HEAD OFFICE:
1. Go to AIS and access the [System Admin > Signatory Mgmt.](https://ais.amti.com.ph/clearancesu/view)
1. Go to AIS and access the [System Admin > Signatory Mgmt.][#external-link:ais-signatory-managmenet]
2. Click the **[+]** on the upper right side of the page to add Department.
<center><img src="/clearance/images/add_signatory.png" width="700"></center>
......@@ -101,7 +109,7 @@ Apart from this Approver rules. Some specific considerations should be kept in m
<center><img src="/clearance/images/add_department_concerned_ho.png" width="700"></center>
> Note that [Signatory Mgmt](https://ais.amti.com.ph/clearancesu/view) is an old module. This is considered a [Clearance Tech Debt][100] since its implementation. See the explanation why on the [Tech Debt: Route Management][102]. You can however use the **Hierarchy Module** to add Department Concerned for HO but I highly discourage it.
> Note that [Signatory Mgmt][#external-link:ais-signatory-managmenet] is an old module. This is considered a [Clearance Tech Debt][#tech-debt] since its implementation. See the explanation why on the [Tech Debt: Route Management][#tech-debt:route-management]. You can however use the **Hierarchy Module** to add Department Concerned for HO but I highly discourage it.
<br>
......@@ -109,7 +117,7 @@ Apart from this Approver rules. Some specific considerations should be kept in m
1. Go to AIS and access the [System Admin > Hierarchy.](https://ais.amti.com.ph/hierarchy)
1. Go to AIS and access the [System Admin > Hierarchy.][#external-link:ais-hierarchy]
2. Click the **+ Add Hierarchy** on the upper left side of the page to add Department/Route.
<center><img src="/clearance/images/add_hierarchy.png" width="250"></center>
......@@ -119,7 +127,7 @@ Apart from this Approver rules. Some specific considerations should be kept in m
* [✓] Project name is enclosed with **( )**. *Project name is recommended to be capitalized*
* [✓] Suffix should exactly be: **- ONSITE**
> The enclosed **Project Name** will be used in the **Project Name** section in the [Clearance Application Form for Onsite](https://ais.amti.com.ph/clearance/onsite "Webpage sent to Onsite Employees")
> The enclosed **Project Name** will be used in the **Project Name** section in the [Clearance Application Form for Onsite][#external-link:ais-clearance-application-form-onsite]
```
EXAMPLE:
......@@ -134,7 +142,7 @@ EXAMPLE:
<center><img src="/clearance/images/add_department_concerned_onsite.png" width="700"></center>
> This is considered a [Clearance Tech Debt][100]. Since it is cumbersome to follow this set of rules to insert a department concerned route.
> This is considered a [Clearance Tech Debt][#tech-debt]. Since it is cumbersome to follow this set of rules to insert a department concerned route.
-------------
......@@ -149,15 +157,15 @@ We must first consider knowing the [Form Type](## "can be AFC or ONSITE") before
Both **form types** (HO and Onsite) can be modified in the **Hierarchy Module**, However it is difficult to find a specific department concerned on the **HO** using the said module due to the old implementation of the **Department Concerned** for HO.
Use only the [Hierarchy Module](https://ais.amti.com.ph/hierarchy "Link to Hierarchy Module") to replace approver if:
Use only the [Hierarchy Module][#external-link:ais-hierarchy] to replace approver if:
* [✔️] Replacement approver is a Standard route for AFC/HO Form Type.
* [✔️] Replacement approver is a Standard route for ONSITE Form Type.
* [✔️] Replacement approver is a department concerned for ONSITE Form Type.
Use only the [Signatory Management](https://ais.amti.com.ph/clearancesu/view "Link to Signatory Management Module") to replace approver if:
Use only the [Signatory Management][#external-link:ais-signatory-managmenet] to replace approver if:
* [✔️] Replacement approver is a department concerned for HO Form Type.
> The clearance module is highly dependent to the [AIS Hierarchy module](https://ais.amti.com.ph/hierarchy "Link to hierarchy module").
> The clearance module is highly dependent to the [AIS Hierarchy module][#external-link:ais-hierarchy]
-------------
......
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