Skip to content

Request - Appoval

Overview

Design an concept for request - approval component

Usecase of this design:

  • Handle the process for operation in inno-data-operation and Inno-Portal project

  • Use case for Build approval

Specification:

  • Có Maker/Checker

  • Multiple level approval

  • Handle the process database design with centralized component

  • Exposure to filter global configuration for

  • Has enough term for overall team to know

Maker-checker is an authorization workflow that ensures that at least 2 people are involved in a transaction. A Maker is responsible for making the request and a checker is responsible for approving the request. The segregation of duties in maker-checker helps keep a strict check over the use of software and data.

For keeping track of all the operations performed using maker-checker, we decided to have an audit trail of them in the application DB. An audit trail is a series of records or events about user activities on an application. Therefore, all maker-checker requests made on Alfred are logged as well as persisted in the DB.

Maker - Checker

Flow for maker checker

Maker: The data operation officer that is the

Checker:

Model for component

The table of maker - checker

Type
maker
checker

Business Logic

2 luồng trạng thái

luồn trạng thái gì ngoài việc chỉ có view/update/edit?

Operation Diagrams

[1] Operation tools:

Cần process để cần.

(a) Schedule chạy và kết nối được với source

(b) Data:

  • khi có sự thay đổi giá + quyền -> đã được điều chỉnh

  • oustanding-share -> monitor. Có report, log

Use case example

An employee wants to execute a billing waiver operation for a customer.

S/he will undertake the following steps:

S/he makes the request for the action with the relevant parameters and their values.

  1. S/he selects the checker for the request and specifies the purpose behind making the request.

  2. The checker receives an email having details about the action and the configured parameters. The checker can either decline or accept the request via buttons available in the mail or in the past requests tab in the Alfred app.

  3. A notification mail is sent to the maker regarding the outcome. i.e whether the request was accepted and executed successfully or the request was declined.

Source Reference