Histórico da Página
...
| Painel | ||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||
In a Technical Support process for the IT area, it is allowed for anyone who encounters difficulties or has any issues with any tool used in the company to open a ticket, which can be for errors, permissions, questions, requesting help, etc. In this case, we can define the assignment mechanism for this step – process Start component – as:
→ This means that anyone in the company can open a ticket to request support.
|
Specific group
...
This mechanism allows defining:
...
| Painel | ||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||
In a Supplier Payment process, the last step is executed by the Accounts Payable department of the company, which consists of 5 employees. All of them are capable of taking on this step and making the actual payment, but the request must be taken on by only one person. Thus, we can define the assignment mechanism for this step – Activity component – as follows:
→ This means that when the request is sent to the Make payment step, all members of the Accounts Payable group will see the request as pending, and it can be taken on by any of the individuals. As soon as one person takes on the request, they become responsible for making the payment, and the request is no longer displayed as a pending item for the rest of the group. Therefore, the assignment mechanism facilitates the distribution of activities among the group, allowing that when one person finishes their current activity, they can take on the next pending one, ensuring a constant flow of requests.
|
Specific role
...
This mechanism allows defining:
...
| Painel | ||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||
In a marketing campaign launch process, it is necessary for the company's vice presidents to agree with the content and approach of the campaign for it to be launched to the market. Therefore, one of the steps in the process is the Approval of the vice presidents. Thus, we can define the assignment mechanism for this step – Activity component – as follows:
→ This means that when the request is sent to the Approval VPs step, all members of the Vice-presidents group will see the request as pending, and it can be taken on by any of the individuals. It is necessary for 80% of the group members to take on the step and take the same action (approve) for the consensus to be reached and the request to proceed. Thus, the assignment mechanism ensures that the majority of vice presidents are aware of and agree with the campaign for it to be launched to the market, avoiding any type of information mismatch or misunderstandings.
|
By form field
...
This mechanism allows defining that only the person indicated in a field of the request form in a previous step is responsible for the step in which it was configured, meaning that only this person receives the request when it is sent to this step.
...
| Painel | ||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||
In an access request process for a system, the requester needs to inform 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 will be sent to the requester's manager for approval or denial of access. The manager responsible for approval varies according to the requester. Thus, we can define the access approval assignment mechanism – Activity component – as:
→ This means that when the request is sent to the Manager approval stage, the person responsible for it and who will receive the request will be the one informed 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.
|
Specific Person
...
This mechanism allows defining that only a specific person is responsible for the stage in which it was configured, meaning that only this person receives the request when it is sent to this stage or only this person can open requests for the process, if it is the initial stage.
...
| 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 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 efficiency, accountability, and confidentiality of the information in the process.
|
Usage 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 applied, and what happens when the request is moved to the stage in which it was configured.
...
| Section | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Dúvidas frequentes
|
Frequently Asked Questions
...
Check here some frequently asked questions about the assignment mechanismsConfira aqui algumas dúvidas frequentes sobre os mecanismos de atribuição.
| HTML |
|---|
<script>
(function() {
function toggleAreas(isExpand, $parent) {
var $items = $parent.find('.panel');
$.each($items, function(idx, el) {
var $arrow = $(el).find('span.cloakToggle').find('span');
var $content = $(el).find('span.cloak');
if (isExpand) {
$arrow.removeClass('cloakDefaultOpen').addClass('cloakDefaultClose');
$content.show();
} else {
$arrow.addClass('cloakDefaultOpen').removeClass('cloakDefaultClose');
$content.hide();
}
});
}
$(document).on('click', '#toggleAll-2', function(ev) {
ev.preventDefault();
var isExpand = $(this).data('expand');
var $parent = $(this).nextAll('.sectionColumnWrapper').first();
toggleAreas(isExpand, $parent);
$(this).data('expand', !isExpand);
});
})();
</script>
<a id="toggleAll-2" href="#" data-expand="true">Abrir>Open/fecharclose todasall as dúvidas<questions</a> |
| Section | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
| Informações | ||
|---|---|---|
| ||
This documentation is valid from the Voyager update (2.0). If you are using a previous update, it may contain information different from what you see on your platform. |
...