You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Index

 

Speaking of configuring processes ...

This window allows you to define all the properties available for a process, relate a form to it, model its diagram setting activities and flows, export it, and also release it for use.

 

LEARN MORE

Expand/hide additional information.

Basic path

 

01. After clicking Save and edit in the process inclusion window, click Properties, located on the left sidebar of the window.

02. In the General tab, enter the required information.

Required information:

Description
Description of the process. You can edit the description previously entered for the process.

Instructions
Instructions to help users to understand the process. When preparing the instructions of an activity or process, it is common to need to search for information from other files or websites. Fluig’s concept is based on hyperlinks, which allow you to add access to both fluig documents and Internet addresses via external documents, avoiding replication of information and making it easier to browse. To do this, add the tag [WD:999999], replacing 999999 by the code of the document on fluig.

Tags
Labels assigned to the process for easy searching later. Tags act as keywords and allow the process to be tagged in a more personal and informal manner. You can find the process by browsing or searching. Enter with or without the character “#” to enable auto complete of the tags in the tags field. The autocomplete retrieves a drop-down list of the five most used tags based on the characters typed after the character "#". To add a tag via autocomplete, simply select it and press Enter. To add a new tag, simply enter it and press Space.

Active
If it is checked, the process is active on the platform. In this case, the latest released version of the process will be available for use in Start requests. If not, the process is not displayed in this area.

Public
If it is checked, any fluig user can query the requests of that process. If not, only the users that participated in the process or users with Administrator status can query the requests of that process.

Category
Category to which to relate the process. That field is optional and is used to group processes into categories. Thus, in Start requests, the processes are grouped into folders and sub-folders that represent their categories and subcategories, making it easy for users to locate them. To add a subcategory, you only need to enter the category, a dot and the subcategory. For example: category HR and subcategory Benefits: RH.Benefits.

Add add-ons to requests
When it is enabled, you can include add-ons in the form of comments or attachments in requests of this process. When the feature is enabled, the corresponding button is identified with Yes. The add-ons in requests allow a user to add comments or attachments to an open request, whether they are responsible or not for the current task, in order to avoid communication by other means that will not be recorded in the history of the process.

Volume
Volume where to store files such as attachments, added to the requests of the process. Only Default and Workflow attachment volumes are displayed for selection.

Manager
Mechanism used for assigning a manager to the process. It only displays the types of assignment mechanism that can be used to define the process manager, who, in turn, will be defined based on the chosen mechanism. The process manager has the power of representing any of the users involved in the flow. When the process manager does some movement type in other user's name, a piece of information about this is added to the process movement history. This process manager can also receive activity follow-up notifications. Available options are:

  • Assignment by association: when it is selected, process managers are the users returned from the combination of group, role and/or specific user;
  • Assignment by group: when it is selected, the process managers are all the users who belong to a group;
  • Assignment by role: when it is selected, the process managers are all the users who belong to a role;
  • Assignment by user: when it is selected, the process manager is a specific user.

Working Hours
Working hours registered on the platform to which the process will be related. Working hours are used to calculate deadlines and delays in process activities. For example, if the working hours were configured as being from Monday to Friday, from 8:00 a.m. to 6:00 p.m., and there is an activity that lasts for 1 hour that was created at 5:30 p.m. on a Tuesday, its conclusion deadline will be on Wednesday at 8:30 a.m., due to the Working Hours. The selected working hours will be used for all process activities in question, except the activities that have their working hours configured.

03. If the use of add-ons is enabled, click Configure – located in Add add-ons to requests – to define the users who can add them to requests.

04. In the General tab of the displayed window, define which users can include add-ons to open requests.

Available options are:

Requester, people responsible for the activity and manager
When it is selected, the user who opened the request, the people responsible for the activities, and the process manager can interact in the process via add-ons.

All process participants and manager
When it is selected, all users who have once participated in the process can interact via add-ons. For example: user A, who is responsible for a particular task, has transferred it to user B. Even if user A is no longer responsible for any tasks in the process, they can still include add-ons, because they have once participated in that process.

All users (for public processes only)
When it is selected, any fluig user can interact in the process through add-ons. This option is only enabled if it is a public process.

05. Click the Follow-up tab and define the users who should receive notifications when an add-on is added to the request.

Available options are:

Notifies person in charge
When it is checked, the people in charge of the process activities are notified;

Notifies requester
When it is checked, the requester, that is, the user who opened the request, is notified.

Notifies manager
When it is checked, the process manager is notified

06. Click the Follow-up tab and define the users who should receive notifications when an add-on is added to the request.

07. Click Configure to configure the manager assignment mechanism selected for the process.

For information on assignment mechanism settings, see Assignment mechanism settings.

08. Click the Form tab to relate an existing form posted in document browsing to the process.

09. Define the required information to relate a form to the process.

Form
Form to be related to the process. Forms are used so users can enter or query data in a simple and structured way while process requests are in progress. Existing forms are displayed in document browsing. To create a specific form for that process, configure it from the Form option, located on the left sidebar the window. In this case, do not select any forms from that field.

Single form record
When it is checked, it is always the latest version of the form that is considered for the process. That is, when creating a new version of a form that is being used in a process that has requests in progress, that new version is displayed to the participants of the request.

Inherit security form records
If it is checked, the existing permissions on the form in document browsing are assigned to the process participants. If not, they receive modification permission on the form so they can perform the task under their responsibility.

10. Click the Version tab and define the required information.

Description
Description of the process version.

Updates attachment
If it is checked, all the request attachments updated and versioned on fluig are automatically updated to the latest version in the request. If not, the attachment version, as it was added to the request, remains the same.

Confirm password
When it is checked, all process activities performed by users will require confirmation of the user's password. The password confirmation feature is used for making sure that a particular user performed a process activity.

 

 

 

 

 

  • No labels