|
|
|
|
|
|
|
[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"
|
|
|
|
|
|
|
|
|
|
|
## ⚠️ SCENARIO: Adding/Removing a Standard Route (HO & Onsite)
|
|
## ⚠️ SCENARIO: Adding/Removing a Standard Route (HO & Onsite)
|
|
|
|
|
|
|
|
[Standard Route](## "e.g Finance, HR, Admin, Service Desk") is a route that will always be included in the routing clearance.
|
|
[Standard Route](## "e.g Finance, HR, Admin, Service Desk") is a route that will always be included in the routing clearance.
|
| ... | @@ -53,7 +61,7 @@ EXAMPLE: |
... | @@ -53,7 +61,7 @@ EXAMPLE: |
|
|
> - Currently routing clearances with the removed route will remain routing and Approvers of the said department/route should still process the remaining clearance applications.
|
|
> - Currently routing clearances with the removed route will remain routing and Approvers of the said department/route should still process the remaining clearance applications.
|
|
|
-------
|
|
-------
|
|
|
|
|
|
|
|
### Add/Removing department concerned route (HO & Onsite)
|
|
### ✓ Add/Removing department concerned route (HO & Onsite)
|
|
|
|
|
|
|
|
Adding and removing a department concerned routes is a once a blue moon scenario *(Adding a department to a clearance route also means adding a route)*.
|
|
Adding and removing a department concerned routes is a once a blue moon scenario *(Adding a department to a clearance route also means adding a route)*.
|
|
|
|
|
|
| ... | @@ -93,7 +101,7 @@ Apart from this Approver rules. Some specific considerations should be kept in m |
... | @@ -93,7 +101,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>
|
|
<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.](##) since its implementation. See the explanation why on the **Clearance Tech Debt wiki**. You can however use the **Hierarchy Module** to add Department Concerned for HO but I highly discourage it.
|
|
> 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.
|
|
|
|
|
|
|
|
<br>
|
|
<br>
|
|
|
|
|
|
| ... | @@ -126,7 +134,7 @@ EXAMPLE: |
... | @@ -126,7 +134,7 @@ EXAMPLE: |
|
|
|
|
|
|
|
<center><img src="/clearance/images/add_department_concerned_onsite.png" width="700"></center>
|
|
<center><img src="/clearance/images/add_department_concerned_onsite.png" width="700"></center>
|
|
|
|
|
|
|
|
> This is considered a [Clearance Tech Debt](##). Since it is cumbersome to follow this set of rules to insert a department concerned route.
|
|
> This is considered a [Clearance Tech Debt][100]. Since it is cumbersome to follow this set of rules to insert a department concerned route.
|
|
|
|
|
|
|
|
|
|
|
|
|
-------------
|
|
-------------
|
| ... | | ... | |