Publication Date: 8/17/2026 Share Print

Previous Topic

Next Topic

Book Contents

Book Index

Authorizer Button, via Requisition Header

If you must edit the Requisition Header information, click on the Authorizer but_authorizer_button button to open the fields for edit as required.

When selecting the Authorizer but_authorizer_button button, if so configured, TRAX will ask the user to enter his/her wall password:

Req_wall password

If the user is set up to be able to authorize requisitions in the TRAX Security Explorer, TRAX allows the user to access the requisition.

The Save Prompt will be displayed, as follows:

SAVE_prompt_standard

Select Cancel to abort the transaction. Select OK to proceed.

The Authorizer but_authorizer_button button, if selected, displays a list of individuals in a pop-up window who are able to authorize the requisition:

Req Authorizer

The Requisition Header will then allow for edits, as illustrated below:

REQ_mgmt_req_header_reopen

Once the Requisition Header record is saved with the edited information it goes to the Requisition Detail window.

The requisition must undergo the standard authorization process.

Note: Refer to the Requisition Detail, General Tab page in this manual for Requisition Header field information. Any information that is modified will be saved in the audit trail (Audit Tab).

After the requisition is updated and released for authorization, it is then displayed in the Requisition Authorization Explorer (Control Panel/ Requisition/ Explorer/ Requisition Authorization Explorer), as follows:

Req Auth Explorer

Users are able to authorize requisitions based upon their access to requisitions in the Security Explorer. The TRAX Administrator may establish user groups in the Requisition Authorization Group Explorer based upon unique tasks the user must perform with respect to requisitions, however, even though a user may be part of a user group, if they are not setup with access to Requisitions in the Security Explorer, the user will not be able to perform his or her requisition related tasks.

Example:

The following screen displays the user 'Abel Hernandez' as a member of the Authorization Group 'REQGRP':

Req group explorer_1

However, it is important that this user be established with access to Requisitions in the Security Explorer to be able to access Requisitions and perform necessary tasks:

Req group explorer_2

The above screen illustrates the user 'Abel Hernandez' as being authorized (via the check next to the user name) to access the Requisition Authorization Group Explorer. So, this user is not only a part of the above listed group 'REQGRP,' but can also authorize requisitions.

See Also

Requisition Header Buttons

Notes Button, via Requisition Header

Print Button, via Requisition Header

Image Button, via Requisition Header

Document Control Button, via Requisition Header

Audit Button, via Requisition Header

Top of Page Publication Date: 8/17/2026 Share Print