• In the document browsing action menu, click the New Folder option;

Figure 1.3 - Path to create a new folder.

• After filling in the Folder data, click Confirm to add.

• After finding the folder where the document will be added, click the New Document option, in the document browsing action menu.

Figure 1.6 - Path to create a new document

Figura 1.8 - Progresso da Publicação de Documentos

• 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

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 TOTVS Fluig Platform, 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 environment, where you usually do backups that ensure information security. 

Figure 1.7 - Add a document

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.

• 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.

• Valid until: Enter the date that determines the end of the document validity.

• 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.

• 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 the platform.

• Update Controlled Copy properties?: When selected, it determines that platform should update the document information in its properties.

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.

• Click and hold the desired document directly in the operating system and drag it to TOTVS Fluig Platform.
• The document can be dragged directly to a folder or to a document upload area (New Document option).

Figure 1.10 - Dragging a document directly to a folder.

• When you drop the document, it is posted with the default properties or with the properties inherited from the folder.
• If it is dragged to the upload area, the post will remain in the same format used in the New Document option.

Figure 1.11 – Document posted directly through drag and drop.

• Select the folder where the external document will be posted.
• Click on More option and then New External Document.

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

 When you finish filling out the data, click "Confirm" located on the page footer.

• Select the folder where the document that will be mirrored is.
• Check the desired document.
• Click the More option and then on  Mirror.

• 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.

• In a previously registered Fluig project, in the forms folder, right click and choose the New -> Form Definition option.

• In the form definition creation screen, just fill out the desired name and click Finish.

Figure 2.2 – Form definition creation screen.

• When you finish, a package that refers to the form is created in the forms folder and the form editor is available for editing.

Figure 2.3 – Creating form definition.

• 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.

• In document browsing, find the folder to which the Form Definition was exported. Then click the folder that indicated the Form Definition.

• Then access the More option in the Actions menu and click New Form.

Figure 2.9 – Creating the Form.

• In the form screen, fill out the form description, which will be the post name. Then provide the fields to be filled out in the form.

Figure 2.10 – Creating the Form.

• • After populating the fields correctly, click Confirm to post the form.

Figure 2.11 – Creating the Form.

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 should enter the code and the description for the process, then click the Save and Edit button.

Figure 3.4 – Configuration of new Workflow process.

• Then you will be able to view the process configuration screen and the modeling area.

  

  Figure 3.5 – Configuration of new Workflow process.

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.

Figure 3.6 – Configuration of new Workflow process.

• After configuring the Workflow process, select the "Form" option in the side menu

Figure 1.1 - Workflow process configuration screen

• Enter the required information, such as name, description, and target folder, then select the desired template.

Figure 1.2 - Form Settings

• Enter the desired fields and edit their properties.

  

• Enter rules for the form, as required.

  
  

• Order the Analytics fields

• Save the form, the Workflow process, and release a new version. Ready! The form is ready to be used in the process.

Figure 1.6 - Form saved successfully

• 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.

• 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.

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.

• Then you will be able to view the process configuration screen and the modeling area.

  

  Figure 3.27 – Configuration of new Workflow process.

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.

• 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.

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.

• To end, click on the Release Version button in the modeling screen to release the Workflow process created (figure 3.33).