The authorizing concept

The maker-checker concept

GCP CashWeb follows the maker-checker concept.

· A maker is the user who can generate, edit or delete the master definitions or transactions. A maker might or might not have authorizing rights.

· A checker is the user who can verify the authenticity of the record and authorize it.

Thus any record generated by a maker must be authorized by a checker.

In GCP CashWeb, the record entries that are generated are termed as definitions. All the newly created or edited definitions or transactions entered in GCP CashWeb, are required to be authorized using the authorization menu. Similarly, disabling or enabling of definitions or transaction requests must be authorized.

On any screen that displays the list of the definitions or transactions, you can view the maker-checker history for the last change done on the record.

Clickto view history details of the record.

In this topic

States of definition

Authorizing a request

States of a definition

Every definition in the GCP CashWeb has a state, which indicates the current action the definition has gone through. The following are various states associated with a definition depending upon the action performed:

· New: Indicates a newly added definition which is not yet authorized.

· Authorized: A definition that is authorized.

· Modified: Indicates a changed definition but not authorized.

· Disabled: Indicates a definition that is disabled and authorized. Definitions with status as Authorized can be disabled.

· Disable Request: A definition that is disabled and is pending in request mode for authorization.

· Enable Request: A disabled definition that is enabled and is pending in request mode for authorization.

· Rejected: A new definition that is rejected after authorization. It can either be modified or deleted.

· Modified Reject: A modified definition is rejected after authorization. It can either be discarded or edited. If discarded, its status changes to the status, prior to modification.

· Disable Request Reject: A disable request is rejected during authorization.

· Enable Request Reject: An enable request is rejected during authorization.

· New Reject: A new definition rejected before authorization.

Authorizing a request

Authorization is a process of approving the request related to a definition. This request may be for modifying, enabling, or disabling a definition. In the process, a request can either be accepted or rejected. The State column indicates the authorization status of the definition. Authorization needs to be done in the following cases:

Requests to be Authorized	Pre-Authorization State	Post-Authorization State
New definition: Any new definition that has been created	New	If authorized: Authorized If rejected: New Reject In this case, the definition can either be modified or deleted.
Modify definition: Any existing definition that has been modified	New or Enabled	If authorized: Authorized If rejected: Modified Reject (a) If the modified transaction is a new one, it can either be modified or deleted. (b) If the modified definition is authorized, then modify request has to be discarded so that the definition retains the Authorized state.
Disable definition: Any authorized definition that has been disabled by the Maker	Disable Request	If authorized: Disabled If rejected: Disable Request Reject In this case, the disable request by the maker has to be discarded so that the definition retains the Authorized state.
Enable Definition: Any disabled definition that has been enabled by the Maker	Enable Request	If authorised: Enabled If rejected: Enable Request Reject In this case, the enable request by the maker has to be discarded so that the definition retains the Disabled state.

Top of Page

Back