Title Name for identifying the process. When you open requests for the process in the Start request feature, this is the name that is displayed. You can edit the process name at any time. | Painel |
|---|
| In a resource request process for a trip – such as transportation, accommodation, meals – the title could be Travel Approval.
|
Icon Graphic element to facilitate the visual identification of the process. To change the icon, simply click the arrow next to the current icon and click the desired icon. You can locate a specific icon using the Search icon field – located at the top. If you do not select another icon, the system assigns the default icon to the process. | Painel |
|---|
| In a Travel Approval process, for example, the icon could be the airplane .
|
Instructions Instructions to help the users of the process to understand it better, such as the purpose of this process, what they can request from this process, who can use this process, among others. The Information tab of the request displays these instructions. | Dica |
|---|
| When preparing the instructions for a process, it is common to need to search for information from other documents or websites. The platform has the concept of hyperlink, which allows you to include an instruction document and also Internet addresses through external documents, both stored in the Documents feature, avoiding information replication and facilitating navigation. To do this, simply use the format [WD:codigodoc], replacing codigodoc with the numeric code of the document. |
Tags Labels assigned to the process to facilitate future searches. Tags function as keywords and allow for a more informal and personal way to label the process. You can find a process through browsing or by search, which considers the tags to locate it. Category The category to which the process belongs and in which it is displayed in the Start requests feature. Categories and subcategories are useful to organize processes and facilitate their location, by grouping them. To include a subcategory, simply enter the category, a period (.), and the subcategory. | Painel |
|---|
| HR.Benefits: means HR category and Benefits subcategory.
|
Complement requests Who can add comments and attachments to ongoing requests even when they are not under their responsibility, thus ensuring that all communication is recorded in the request history instead of being done through other means. The available options are: - Responsible and requester: when selected, it determines that only the requester – at the time of opening the request – and the person responsible for the stage in which the request is located, can add comments and attachments.
- Responsible, requester, and managers: when selected, it determines that only the requester and the process managers – at any time – and the person responsible for the stage in which the request is located, can add comments and attachments.
Participants and managers: when selected, it determines that all those involved in the request at some point and the process managers, can add comments and attachments at any time.
| Painel |
|---|
| → Person A, who was responsible for a certain stage of the request, transferred it to person B. → Even though person A is no longer responsible for any stage of the request, they can still include comments and attachments at any time, as they were a participant in the process at a certain point.
|
Any user: when selected, it determines that anyone with an active registration can add comments and attachments to the request at any time.
| Informações |
|---|
| This option is only valid for public processes. To define a process as public, it is necessary to activate the Make public option in the Security tab. |
Track additions Who should receive notifications when you add a comment or an attachment is added to the request. This field is not enabled when the option selected in Complement requests is Responsible and requester. The available options are: - Notify responsible: when checked, it determines that the responsible parties for the stages of the process will be notified when someone adds a comment or an attachment is added to the request.
- Notify requester: when checked, it determines that the requester – the one who opened the request – will be notified when someone adds a comment or an attachment is added to the request.
- Notify manager: when checked, it determines that the process managers will be notified when someone adds a comment or an attachment is added to the request.
| Nota |
|---|
| Regardless of the checked options, the notification is not sent to the person who performed the action does not receive the notification. | Painel |
|---|
| One of the process managers added a comment to the request. Even if the Notify manager option is checked, he will not receive the notification, since the action was performed by himself.
|
|
| Informações |
|---|
| Notifications You can be sent send notifications in the Notification center or via email, depending on how you have configured the sending options were configured in the your personal profile, as well as which options are available for use in the company, which may have been configured globally – for all companies – or by company. |
Attachment volume Location where you can store the attachments added to the process requests will be stored. Only . It displays only volumes of type Default and Workflow Attachment are displayed. Volume management is done . You can manage the volume in the Volumes feature of the WCMADMIN user control panel. Working hours Working hours that will be related you can associate to the process and considered use in the execution of its stagessteps. The calculations of final deadlines and delays use the working hours selected for the process are used in the calculations of final deadlines and delays for stages for steps that do not have their own configured working hours. The working hours that exist in the Working hours feature are displayed Working hours feature displays the existing working hours for selection. | Painel |
|---|
| | Estado |
|---|
| subtle | true |
|---|
| title | EXAMPLE OF DEADLINE AND DELAY CALCULATION FOR STAGESSTEPS |
|---|
|
→ The working hours selected for the process are configured as: Monday to Friday from 8:00 AM to 6:00 PM. → The time to complete a stage step that does not have its own working hours is 1 hour. → The request reached this stage step at 5:30 PM on a Tuesday. → Therefore, the final deadline for completing the stage step will be Wednesday at 8:30 AM. After 8:30 AM, the stage step will be considered delayed.
|
Expiration deadline Maximum time, in hours, within which you must complete the request must be completed to not be considered consider it expired. The entry must be in the format 000:00. Upon reaching the maximum time, the system issues a notification is issued to all involved informing that the request has expired. When configured, the system calculates the time is calculated by taking into account the standard working hours registered on the platform. This deadline cannot be less than the notice period. Notice period Time, in hours, before the request's expiration deadline of the request in which , when the system sends a notification will be sent informing that the request is about to expire. The input must be in the format 000:00. When configured, the time is calculated considering system calculates the time using the standard working hours registered in on the platform. This period cannot be greater than exceed the expiration deadline. | Painel |
|---|
| | Estado |
|---|
| |
|---|
| subtle | true |
|---|
| title | EXAMPLE OF USING EXPIRATION AND NOTICE PERIODS |
|---|
|
→ The expiration period of a process is configured as: 5 hours. → The notice period is configured as: 10 minutes. → A Someone opens a request for the process was opened at 1:00 PM. That is, they must close it must be closed by 6:00 PM. If it is not closedthey do not close it, after 6:00 PM it is considered expired. → However, at 5:50 PM, the system sends a notification about the expiration of the request will be sent to those involved, informing that it is about to expire. The frequency of this notification during these 10 minutes – from 5:50 PM to 6:00 PM – is what was configured in th the Task scheduler, which can be every minute, for example. → Upon reaching 5 hours open, that is, at 6:00 PM, the system sends a single notification will be sent informing that the request has expired and its status changes to Expired. |
|