...
After following the steps of the Installation Guide (Windows and Linux), you need to access Fluig through a browser, entering: <HOST>:<PORT>/portal.
...
| Deck of Cards |
|---|
| effectDuration | 0.5 |
|---|
| id | Samples |
|---|
| effectType | fade |
|---|
|
| Card |
|---|
| - Após localizar a pasta onde o documento será adicionado, clique na opção Mais > Novo Documento (Avançado), no menu de ações da navegação de documentos.
Figura 1.9 - Caminho para criar um novo documento avançado
|
| Card |
|---|
| The document registration function is divided in five sections. In the first section, "Publishing Files", we will determine the filed that will be posted in the document. Whenever you want to send a file to Fluig, you need to: - Click the Choose files button (figure 1.7). This feature is very important because it transfers a file from your computer to Fluig environment, where you usually do backups that ensure information security.
Figure 1.7 - Add a document
|
| Card |
|---|
| In section “General Information” (figure 1.8), you will add information about the document. The elements of this section are described below:
Figure 1.8 – Add a document - General Information Tab. - Comment: Enter a comment that describes the content of the document that is being posted.
- Keyword: Enter keywords that make it easy to locate the document.
- Version/Review Description: Enter a description for the current document version/review.
- Version/Review: Enter the document start version/review number that is being posted.
- Unchangeable Version/Review: When selected, it determines the document version/review is unchangeable, not allowing changes to the document posted. In this case, the change is only possible with a new version/review.
- Document Expires?: When selected, it determines that the document being posted will expire on the date entered in the "Valid until" field.
| Nota |
|---|
| If this field is not selected, determining that the document must not expire, the date entered in the "Valid until" field is not considered. |
- Expiration Notification Period:Enter the advance period, in number of days, that should be considered for sending the document expiration notification. If 0 (zero) is entered, the value entered in General Parameters will be used.
- Valid from: Enter the date that determines the start of document validity.
| Nota |
|---|
| The documents will only be displayed for the users after the validity start date entered in this field, which allows the author to schedule a document view. The validity start date to be entered cannot be before the current date. |
- Valid until: Enter the date that determines the end of the document validity.
| Nota |
|---|
| The date entered in this field determines the document expiration date. If the "Document Expires?" field is not selected, the date entered in this "Valid until" field is not considered. |
- Document Type: Select, among the options available, the document type that is being posted
- Subject: Select among the options available the subject related to the document being entered.
- Icon Type: Select among the options available the icon that will be associated with the document.
- Author: Enter the document author name.
- Publisher: Provides the name of the logged in user that is posting the document.
- Language: Select the language associated to the document being posted. This language is used to index the content and document information. Indexed information is used in searches by content.
- Notify via email: When selected, it determines it should send an email about the document post.
| Nota |
|---|
| The email is sent to the users that have the subject determined for this document, as being of interest. If the subject determined for the document is a mandatory subject, it will not be possible to restrict the delivery of email; thus, all active users in Fluig will receive notification of the post. |
- Allow Download and Printing?: When selected, it defines that the users can download and print the file that contains the document.
- Use internal viewer?: Allows internally viewing a document in Fluig.
| Informações |
|---|
| To view a document internally, you need to generate a PDF document. This generation is done automatically by Fluig, using libraries available on the market. Depending on the features used in the document, the generated PDF cannot display all details of the original file. Verify the renderer that presents the best result by selecting one of the renderers available and posting the document. |
- Update Controlled Copy properties?: When selected, it determines that Fluig should update the document information in its properties.
|
| Card |
|---|
| In the "Related Documents" section, documents related to the document that is being posted will be entered. In the "Approval" section, one or more approvers are defined for the document in question. In the "Security" section, the document access policies are defined.
After filling in the document data, click Confirm to add. |
|
...
Drag and Drop
...
| Deck of Cards |
|---|
| effectDuration | 0.5 |
|---|
| id | Sample |
|---|
| effectType | fade |
|---|
|
| Card |
|---|
| - Select the folder where the external document will be posted.
- Click on More option and then New External Document.
| Nota |
|---|
| Some URLs might not be rendered due to a security matter, where the pages themselves block access via iFrames, preventing the use of these URLs in an external document. Check if the site you are trying to access has an "Embed" URL, which are URLs that are usually made available for use in iFrames. |
Figure 1.12 - Path to create a new External Document.
|
| Card |
|---|
| After selecting the External Document option, the screen for filling out the document data opens (figure 1.13). Most attributes on this screen have already been explained in document post, the main difference is in the URL field, which is filled out with the address for accessing the Web page.
Figure 1.13 – Registration screen for general information
|
| Card |
|---|
| When you finish filling out the data, click "Confirm" located on the page footer. | Informações |
|---|
| In order to have access to the posted document page, you need to be connected to the Internet. |
|
|
...
| Deck of Cards |
|---|
| effectDuration | 0.5 |
|---|
| id | Sample |
|---|
| effectType | fade |
|---|
|
| Card |
|---|
| - Select the folder where the document that will be mirrored is.
- Check the desired document.
- Click the More option and then on Mirror.
Figure 1.14 - Path to mirror a document.
|
| Card |
|---|
| - On the Select target folder screen, select the folder where the mirror document should be posted.
- Then click Confirm.
Figure 1.15 - Screen to post mirror document.
|
|
...
| Deck of Cards |
|---|
| effectDuration | 0.5 |
|---|
| id | Sample |
|---|
| effectType | fade |
|---|
|
| Card |
|---|
| - In a previously registered Fluig project, in the forms folder, right click and choose the New -> Form Definition option.
Figure 2.1 – Creating a Form Definition.
|
| Card |
|---|
|
Figure 2.2 – Form definition creation screen.
|
| Card |
|---|
|
Figure 2.3 – Creating form definition.
|
| Card |
|---|
| From the editor, all the HTML content is developed. In the example, a simple registration form was developed. After creating the desired form definition, just export it to the server.
Figure 2.3 – Creating form definition.
|
|
...
| Deck of Cards |
|---|
| effectDuration | 0.5 |
|---|
| id | Sample |
|---|
| effectType | fade |
|---|
|
| Card |
|---|
| - Right click the previously registered form and then Export.
Figure 2.4 – Exporting Form Definition.
|
| Card |
|---|
|
Figure 2.5 – Exporting Form Definition.
|
| Card |
|---|
| - In the example, we have filled out the server field and checked the New form definition flag.
- The form definition field is automatically populated when you select the file you want to export.
- In the example, we did not associate the form to a dataset, so the field is empty.
- We enter the target folder for document browsing, in which the form will be published (through code).
- In the example, we do not enter a descriptor field and then enter that we wish to store the information in Cards.
- We select Next to continue.
Figure 2.6 – Exporting Form Definition.
|
| Card |
|---|
| In the next screen, it is necessary to configure the form definition for a mobile version. If we want all the fields to be displayed in mobile devices, we keep them checked and click the finish button. The form definition will be sent to the server and the .html file for the mobile version will be made available in the forms folder of the Fluig project.
Figure 2.7 – Exporting Form Definition.
|
|
...
| Deck of Cards |
|---|
| effectDuration | 0.5 |
|---|
| id | Sample |
|---|
| effectType | fade |
|---|
|
| Card |
|---|
| - In Fluig document browsing, find the folder to which the Form Definition was exported. Then click the folder that indicated the Form Definition.
Figure 2.8 – Creating the Form.
|
| Card |
|---|
|
Figure 2.9 – Creating the Form.
|
| Card |
|---|
|
Figure 2.10 – Creating the Form.
|
| Card |
|---|
|
Figure 2.11 – Creating the Form.
|
|
...
It is a sequential set of activities (figure 3.1). It has the objective of making users, customers, suppliers and partners actively participate in the company by managing processes and workflows, designing and developing simple and complex processes supported by electronic forms and managed by parameterizable rules, interacting with other company systems and applications.
Figure 3.1 – Example of Workflow process.
Tasks
Tasks are specific activities controlled by Fluig. One or several (Consensus) users have the responsibility of executing them, all activity running management is proactive, with running and delay message delivery.
...
- In the modeling screen, click on the activity in the side menu and drag it to the stage.
Figure 3.7 – New Workflow Process activity.
In order to edit the activity properties, hover the mouse over the activity and click the respective icon. The activity property screen will be displayed.
...
In the following image, there is an example of automatic decision-making activity. A decision will be made, based on the information in the form.
Figure 3.8 – Example of an automatic decision-making activity.
Let's see the example:
We have the Purchase process and, in the "value" field, there is a rule.
...
In the activity flow Registration, It is necessary to pay attention to the fact that the output flows of a normal activity to an automatic activity do not allow return (figure 3.9a).
Figure 3.9a - Situation that does not allow return.
Whereas, output flows from an automatic activity to a normal activity allow return (figure 3.9b), and the return is performed directly to the activity that precedes the automatic decision-making.
Figure 3.9b - Situation that allows return.
For automatic activities, you can insert intelligent mechanisms (expressions) that, depending on the result obtained, determine for the activity, among the possibilities that we configured during process development time, what will be the flow to where such activity should be routed.
In an automatic activity, you can configure "n" expressions, however Fluig requires a priority order to be considered (figure 3.10). In this way, as soon as the first expression is met, the flow follows to the activity related to the expression in question and the other expressions are ignored.
Figure 3.10 – Definition of the order of an automatic Activity.
The expressions configured in an automatic activity should follow pre-established standards, making it possible, for example, to use the "getCardValue" function, which returns the value of a form field, and can even validate the value.
...
| Deck of Cards |
|---|
| effectDuration | 0.5 |
|---|
| id | Sample |
|---|
| effectType | fade |
|---|
|
| Card |
|---|
| - Create a new workflow process or edit an existing Workflow process.
- In the process modeling screen, click the automatic activity in the side menu and drag it to the stage (figure 3.11).
Figure 3.11 – Click on add Automatic Activity button.
|
| Card |
|---|
| In order to edit the activity properties, hover the mouse over it and click on the property icon. The activity property screen will be displayed.
The Automatic Activity Registration function is divided into two sections. In the first one, it is necessary to determine the activity general information and in the second one, the conditions (effectively the expressions) to be used. - In the General tab (figure 3.12), automatic activity information will be registered.
Figure 3.12 - Main Tab Screen.
|
| Card |
|---|
| In the "Conditions" tab, enter the conditions that will trigger an automatic behavior in the activity. To register, click the Add button. A pop-up opens (figure 3.13) where you must register the conditions, the target activity of this condition, and the assignment mechanism, this last one being optional.
Figure 3.13 - Automatic Activity Condition configuration screen.
The interesting thing is that these expressions can have the format of any logic expression that is used in JavaScript language. The return of these expressions must be a logic value. | Informações |
|---|
| To register the logical expressions in automatic activities in the Workflow processes in Fluig, you must first register the normal activities, as well as the automatic activities. The expression settings of an automatic activity must only be performed after the process activity flow registration. |
|
|
...
A particular company has the following defined processes:
1) Material Request
Figure 3.14 - Workflow Process Material Request.
2) Requisição Compra
Figure 3.15 - Workflow Process Purchase Request.
...
Thus, it hanged the material request process and treated the "Purchase Request" process as a subprocess of the "Material Request" process (figure 3.16).
Figure 3.16 - Workflow process with the subprocess
Thus, when the material requested is missing, the user can start the purchase request and then, when the material is received, fulfill the pending request.
...
| Deck of Cards |
|---|
| effectDuration | 0.5 |
|---|
| id | Sample |
|---|
| effectType | fade |
|---|
|
| Card |
|---|
| - Create a new workflow process or edit an existing Workflow process.
- In the process modeling screen, click on Subprocess in the side menu and drag it to the stage (figure 3.17).
Figure 3.17 –Click on Add Subprocess button
|
| Card |
|---|
| - In order to edit the subprocess properties, hover the mouse over it and click on the property icon. The subprocess property screen will be displayed.
- In the Subprocess option (figure 3.18), you must select, among the available options, which process should be considered as Subprocess of the process in question.
- The Transfers attachment option (figure 3.18), when enabled, can transfer the attachments from the original process request to the new Subprocess request.
- When finished, click on Confirm.
Figure 3.18 - Subprocess registration screen. |
|
Parallel activities.
In Workflow processes, it is common to find activities that should work in parallel. To fulfill this situation, Fluig process management provides mechanisms to enable the use of parallel activities.
...
Suppose that in the process below (figure 3.19), there are 3 parallel activities "Book Hotel", "Buy Ticket", and "Deposit Prepayment". When one of the three activities is complete, the process is stopped at Join until all other activities are complete, i.e. if the activity "Buy Ticket" finishes, it will only continue the flow until the "Trip Ok?" activity when the "Book Hotel" and "Deposit Prepayment" activities are also complete.
Figure 3.19 - Screen of Workflow process with Fork and Join.
Let's see how to register parallel activities in a workflow process:
...
| Deck of Cards |
|---|
| effectDuration | 0.5 |
|---|
| id | Sample |
|---|
| effectType | fade |
|---|
|
| Card |
|---|
| - Create a new workflow process or edit an existing Workflow process.
- In the process modeling screen, click on Fork in the side menu and drag it to the stage (figure 3.20).
Figure 3.20 – Click on the Fork button.
|
| Card |
|---|
| - In order to edit the properties of Fork, hover the mouse over it and click the property icon. The Fork property screen will be displayed.
- In the Fork property screen, you can only edit the name of the component.
- When finished, click on Confirm.
Figure 3.21 - Fork registration screen. |
| Card |
|---|
| - To create a Join, click on Join in the side menu and drag it to the stage (figure 3.22).
- In order to edit the properties of Join, hover the mouse over it and click the property icon. The Join property screen will be displayed.
- In the Join property screen, you can only edit the name of the component.
- When finished, click on Confirm.
Figure 3.22 – Click on the Join button. | Informações |
|---|
| A Fork must have output flows, while Join must have input flows. |
|
|
...
- Activ. Flow: Enter the text to be used to identify the source activity advance action for the target activity in the process flow. This text is displayed as action option to the user at the moment of the source activity execution.
- Automatic Flow: When checked, it determines that the activity will be moved automatically to the target activity when its deadline is overdue. For this to happen, it is necessary to configure a schedule of Automatic Flow type from the Task Scheduler feature.
- Allows Return: When checked, it determines that the target activity can perform a return action to the source activity.
- Activ. Return: Enter the text to be used to identify the target activity return action for the source activity in the process flow. This text is presented as an action option to the user at the moment of the target activity execution.
Figure 3.23 – Activity flow registration.
Creating a Link
When we are preparing an activity or a Workflow process instructions, it is often necessary to search for another file or site information.
...
We will build a simple Workflow (figure 3.24), which will be very useful for understanding Fluig ease of operation. The Workflow has the following activities: Start, Approval, and End.
.
Figure 3.24 – Example of Workflow Process.
| Deck of Cards |
|---|
| effectDuration | 0.5 |
|---|
| id | Sample |
|---|
| effectType | fade |
|---|
|
| Card |
|---|
| To add a Workflow process (according to the above example), click on the Configure Process option in the Processes icon in Fluig main menu.
Figure 3.25 - Path to create a new Workflow process
|
| Card |
|---|
| Then a screen opens with the processes that were already registered. In order to add a new process, just click Add in the action menu of the Configure Processes screen. In the Add New Process screen, you must enter the code and the description for the process, then click the Save and Edit button. In the example, we enter the 'process' code and the 'Approval' description.
Figure 3.26 – Configuration of new Workflow process.
|
| Card |
|---|
| At this moment, the next step is to configure the process properties. In order to do that, click on the Properties option in the left side menu. - General tab.
- Version tab.
- Attachment Security tab.
- Advanced tab.
- CAP tab
After completing the changes, click on Confirm to return to the process modeling stage.
Figure 3.28 – Configuration of new Workflow process.
|
| Card |
|---|
| - To create a start activity, click on Start in the side menu and drag it to the stage.
- In order to edit the properties, hover the mouse over the component and click the property icon. The respective component properties screen will appear.
- Repeat the action to add a common activity: click on Activity in the side menu and drag it to the stage. This activity must be named 'Approval'.
- Lastly, repeat the process for End activity.
Modeling, at first, must be as in the following image:
Figure 3.29 - Workflow process with activities created. |
| Card |
|---|
| After activities registration, you need to configure the flows between them: - To add the flow between the Start activity and the Approval, hover the mouse over the Start activity, click on the flow icon and drag to the target activity (Approval).
Figure 3.30 – Flow icon in the target activity. This step must be as in the following image:
Figure 3.31 – Flow from the Start activity to the Approval activity.
- Repeat this process for the Approval activity, where the target should be the End activity.
Figure 3.32 – Flow from the Approval activity to the End activity.
|
| Card |
|---|
| - To end, click on the Release Version button in the modeling screen to release the Workflow process created (figure 3.33).
Figure 3.33 – Release the Workflow process version. |
|
Quality
Fluig has features that support the Quality area in standard management, ensuring the ISO9000-2000 certification. These features enable and facilitate approval controls, access, validity, versions, revisions, and distribution of standards and procedures.
...
- In Fluig document browsing, select the folder for which you wish to generate the main list.
- In the actions menu, click More, and then click Main List.
Figure 4.2 – Generate Main List.
In the Main List Screen, choose the parameters for issuing the list.
Figure 4.3 – Main List Screen
- Click on Click List.
- A pop-up opens with the mains list issued and with the option to print.
...
In the Help option, available in Fluig Settings menu (located in the upper right corner), you can check the solution reference manual.
Figure 5.1 - Product Help.
Customization
In Fluig, it is possible to customize the default view.
...