Árvore de páginas

Versões comparadas

Chave

  • Esta linha foi adicionada.
  • Esta linha foi removida.
  • A formatação mudou.

...

The functioning of each of the mechanisms is detailed below.


Any

...

Person

...

This mechanism allows defining that any person with an active registration on the platform can be responsible for the steps in which it was configured; that is, any person can receive the request when it is sent to this steps, or any person can open requests for the process if it is the initial step.

...

Painel
borderColor#ebecf0

Estado
subtletrue
titleEXAMPLE OF USE

In a Technical Support process for the IT area, anyone who encounters difficulties or has any issues with any tool used in the company can 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:

StepType of mechanism
Open ticketAnyone

→ This means that anyone in the company can open a ticket to request support.

Multimedia
namemecanismo-qualquer-pessoa.mp4
width100%
pagePlataforma ❙ Mecanismos de atribuição
autostarttrue
spacefluig
height5%


Specific

...

Group

...

This mechanism allows defining:

...

Painel
borderColor#ebecf0

Estado
subtletrue
titleEXAMPLE

In a Supplier Payment process, the Accounts Payable department of the company, which consists of 5 employees, executes the last step. All of the employees are capable of taking on this step and making the actual payment, but only one person must take on the request.

Thus, we can define the assignment mechanism for this step – Activity component – as follows:

StepType of mechanismPossible responsible parties for the stepExecution method of the stepRequest submission method
Make PaymentSpecific groupMembers of the Accounts Payable groupIndividual activitySubmission to all in the group (pool)

→ This means that when you send the request to the Make Payment step, all members of the Accounts Payable group see the request as pending, and any of the individuals can take it on. As soon as one person takes on the request, they become responsible for making the payment, and the interface no longer displays the request as a pending item for the rest of the group. Therefore, the assignment mechanism facilitates the distribution of activities among the group, so when one person finishes their current activity, they can take on the next pending one, ensuring a constant flow of requests.

Multimedia
namemecanismo-grupo-específico.mp4
width100%
pagePlataforma ❙ Mecanismos de atribuição
autostarttrue
spacefluig
height5%


Specific

...

Role

...

This mechanism allows defining:

...

Painel
borderColor#ebecf0

Estado
subtletrue
titleEXAMPLE OF USE

In a marketing campaign launch process, the company's vice presidents need to agree with the content and approach of the campaign in order to launch it 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:

StepType of mechanismPossible responsible parties for the stepExecution method of the stepRequest submission methodConsensus
VPs ApprovalSpecific groupMembers of the Vice-presidents groupJoint activitySubmission to all in the group (pool)80%

→ This means that when the request goes to the VPs Approval step, all members of the Vice-presidents group see the request as pending, and any of the individuals can take it on. 80% of the group members must to take on the step and take the same action (approve it) to reach the consensus for the request to proceed. Thus, the assignment mechanism ensures that the majority of vice presidents are aware of and agree with the campaign to launch it to the market, avoiding any type of information mismatch or misunderstandings.

Multimedia
namevídeo-mecanismo-atribuição.mp4
width100%
pagePlataforma ❙ Mecanismos de atribuição
spacefluig
height5%


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.

...