Histórico da Página
...
| Painel | ||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||
In an Request to access the system process, the requester needs to enter who their manager is and why they need access to the tool they are requesting. Before being forwarded to the IT department, responsible for granting access, the request is sent to the requester's manager for approval or denial of access. The manager responsible for approval varies depending on the requester. Thus, we can define the access approval assignment mechanism – Activity component – as:
→ This means that, when the request goes to the Manager approval stage, the person responsible for it and who will receive the request is the one entered in the Manager field of the process form. Therefore, the assignment mechanism ensures that each request is directed directly to the responsible person, facilitating the management and approval of access requests.
|
...
| Informações | ||
|---|---|---|
| ||
If the specific person defined in this mechanism is inactive when the request is moved moves to the stage, the request is sent goes to the process manager. |
| Estado | ||||||||
|---|---|---|---|---|---|---|---|---|
|
As it targets a specific person, we recommend it is recommended for stages that deal with confidential information, critical or sensitive data, or for approvals that only one person is authorized to make.
| Estado | ||||||||
|---|---|---|---|---|---|---|---|---|
|
If the stage is not critical or sensitive, defining only one responsible person can create bottlenecks and cause stall the request to be stalled for a long time, it . It can overload the responsible person with tasks that you could be distributed distribute among several people, in addition to the risk of delays in the process if the person is unavailable at any period or day.
| Painel | ||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||
In a Contract Approval process, the person responsible for approving and releasing the contract signature is the director of the Contracts area of the company. Only this director can access the necessary information to approve or not approve the signing of contracts. Thus, we can define the assignment mechanism for contract approval – Activity component – as:
→ This means that when you send the request is sent to the Director Approval stage, the person responsible for it, who will receive the request, is Maria da Cunha; only she can decide on this approval. Thus, the assignment mechanism ensures that the responsibility for approving the contract is clearly defined and that only the configured person can execute this stage, ensuring the efficiency, accountability, and confidentiality of the information in the process.
|
...
Examples
...
We have gathered several scenarios here in which different assignment mechanisms can be applied. The examples include the mechanism, the scenario where it will be is applied, and what happens when the request is moved moves to the stage in which it was configured.
Examples We demonstrate examples with some types of assignment mechanisms are demonstrated. Click on each scenario to see its details.
...
Visão Geral
Import HTML Content
Conteúdo das Ferramentas
Tarefas