I am trying to determine how to name buttons in a global element document:
There are two types of scenarios where buttons are used: (1) User submits a request and (2) Approver approves or rejects the request.
The nature of the request changes. Sometimes, it is to create a new entity in the system. Sometimes it is to ask for an association between the user profile and an existing entity (ex. a region). Sometimes it is to register for a program. Etc. But fundamentally, the requests are always to "activate" an association (to a program, to a region, etc.) or to "cancel" (de-activate) the association between the user profile and the other entity (program, region, etc.)
The nature of approvals is always the same: accept, or reject the request. This causes no issue for the buttons: we keep accept and reject as buttons.
For the request buttons, can we keep "activate" and "cancel" as generic names throughout the site to accommodate all the scenarios and uses? Is it better to customize them according to the scenario? I am trying to understand what the best practice may be for standardizing buttons having the same behavior but potentially a different label.