The project dashboard is an essential element for managing the WINDEV projects. The project dashboard gives an overall view of the progress of a project.

The dashboard includes several elements (widgets) that give an overall view of the project status.

In this section, we will present the operations that can be performed on the dashboard elements as well as the management of automatic tests and the optimization of queries.


	Answer	If you did not create the windows in the previous lessons, you can follow this lesson by opening a corrected project: in WINDEV's home page (Ctrl + <), click "Tutorial" and select "Full application (with windows)". A full corrected application project is also available: in WINDEV's home page (Ctrl + <), click "Tutorial" and select "Full application (Answer)"

To view the project dashboard (if necessary), go to the "Project" pane, "Project" group and click .

The dashboard

The project dashboard includes several Widgets. Each Widget displays various information about the project.

For example, the "Performances" Widget is used to start the performance profiler or to open the last performance report.

The "Static audit and Compilation" Widget is used to quickly see whether the project contains compilation errors. You have the ability to enable (or not) a Widget, to add one or to delete one at any time.

Automatic tests

One of the most interesting features of the dashboard is to give information about the tests that have been run on the application.

Several tests have already been run while developing our application.

The automatic tests are a category of specific tests. The automatic tests are used to automatically perform some operations on your windows. These tests are recorded as WLanguage scenarios and they can be easily modified in the code editor. Once recorded, the automatic test can be re-run as many times as necessary, to test for example the impact of a modification made to a window, a procedure, ...

Let's give it a try! We are going to create an automatic test on the edit window that was created at the beginning of this lesson.


	Remark	The automatic tests can be run on the windows, procedures, classes.

To create an automatic test on a window, all you have to do is run the test of the window:
1. Open the "WIN_Menu" window in the editor.
2. On the "Automatic tests" pane, in the "Tests" group, expand "New" and select "Record a new scenario".
3. In the window that is displayed, click "Start recording".
4. The test of the window is run.
5. Click the "Finding orders" tab pane.
6. Choose the "Credit card" payment mode.
7. Click "Find".
8. Close the window via "Menu .. Exit" and confirm the end of application.
  Remark
  This option may not be available if you did not follow the entire tutorial. In this case, click the "x" to close the window.
9. The recording of the automatic test has ended.
10. The test editor proposes to save a description for the automatic test we just created. Enter the name of the automatic test: "Test for finding orders". Validate.
11. The test editor displays the WLanguage code of the test that has just been recorded:
  The test is currently available and has not been run ( next to the name of the test in the editor).
12. The test can be run at any time:
  - Select the test name in the test editor.
  - In the popup menu (right click), select "Run".
13. The test is automatically run and the test editor displays the result in the "Test results" pane (the test was successfully run in our case).
14. Save the test if necessary ( or Ctrl + S)
  Remark
  The WLanguage functions used to run automatic tests are the EmulateXXX functions.

We are now going to perform a modification in our window and to run the test again. The modification affects the "Find" Button control. We are going to gray it.
1. Display the "WIN_Menu" window if necessary.
2. In the editor, click the "Finding orders" tab pane and select the "Find" Button control.
3. Open the control description ("Description" in the popup menu).
4. In the "UI" tab, select "Grayed".
5. Validate the control description window.
6. Save the window.
7. Go back to the test editor (click the corresponding button in the open documents bar).
8. Run the test again.
9. The test appears again in the test editor. The "Compilation errors" tab pane reports several test errors.
10. Redisplay the "WIN_Menu" window in the editor.
11. Open the description of the "Find" Button control ("Description" in the popup menu).
12. In the "UI" tab, select "Enabled".
13. Validate the control description window.
14. Go back to the test editor (click the corresponding button in the open documents bar).
15. Run the test again. The test is now successfully run.

Another feature of the test editor is the ability to modify or add WLanguage code in the test scenarios. We are going to add code lines to check whether the Table control contains at least one record.
1. Display the test editor if necessary (for example, double-click "TEST_Menu" in the "Tests" folder of the "Project explorer" pane).
2. Add the following code before the line "EmulateMenu("_Menu","OPT_Exit")":
  // If the Table control contains no record
  IF WIN_Menu.TABLE_QRY_FindOrders..Count = 0 THEN
  // An error must be signaled
  TestWriteResult(twrError, ...
  "The Table control is empty after search")
  END
3. Save the test ( or Ctrl + S)
4. Click the icon. The test is successfully run. Indeed, the Table control contains at least one record.

The test editor proposes several features that will not be presented in this tutorial:

the ability to use a set of test values.
the definition of input and output parameters for the test.
the ability to create a test library to run the test of an executable on a computer other than the development computer for example.

See Overview of automatic tests for more details about the automatic tests.

Close the editor of automatic tests.

DICAS 3008 - WINDEV TUTORIAL 31 - Adicionar e Modificar Janelas ANCORAS - PARTE D
DICAS 3009 - WINDEV TUTORIAL 32-Adicionar e Modificar Janelas - Exibicao registro - PARTE E

DICAS 3010 - WINDEV TUTORIAL 33-Adicionar e Modificar Janelas - Modifica Imagen - PARTE F

DICAS 3011 - WINDEV TUTORIAL 34 - Adicionar e Modificar Janelas - Validacao - PARTE G

DICAS 3012 - WINDEV TUTORIAL 35 - Adicionar e Modificar Janelas - CRIACAO - PARTE H

DICAS 3013 - WINDEV TUTORIAL 36 - Adicionar e Modificar Janelas - Teste - PARTE I

DICAS 3014 - WINDEV TUTORIAL 37 - Pesquisa Simples - Apresentacao - PARTE A

DICAS 3015 - WINDEV TUTORIAL 38 - Pesquisa Simples - Usando Controle Tab- PARTE B

DICAS_3016_WINDEV_TUTORIAL_39_Pesquisa_Simples_Configurando_Pesquisa_PARTE_C

DICAS 3017 - WINDEV TUTORIAL 40 - Pesquisa Simples - Pesquisa Identica- PARTE D

DICAS 3018 - WINDEV TUTORIAL 41 - Pesquisa Simples - Pesquisa Generica - PARTE E

DICAS 3019 - WINDEV TUTORIAL 42 - Pesquisa Simples - Navegacao pelos Arquivos - PARTE F

DICAS 3020 - WINDEV TUTORIAL 43 - Pesquisa Multicriterio - Apresentacao - Parte A

DICAS 3021 - WINDEV TUTORIAL 44 - Pesquisa Multicriterio - Criacao Consulta - Parte B

DICAS 3022 - WINDEV TUTORIAL 45 - Pesquisa Multicriterio - Uso Parametro - Parte C

DICAS 3023 - WINDEV TUTORIAL 46 - Pesquisa Multicriterio - Criando Interface - Parte D

DICAS 3024 - WINDEV TUTORIAL 47 - Pesquisa Multicriterio - Primeiro Parametro - Parte E

DICAS 3025 - WINDEV TUTORIAL 48 - Pesquisa Multicriterio - Segundo Parametro - Parte F

DICAS 3026 - WINDEV TUTORIAL 49 - Pesquisa Multicriterio - Parametro Data - Parte G

DICAS 3027 - WINDEV TUTORIAL 50 - IMPRIMIR_TABELA

DICAS 3028 - WINDEV TUTORIAL 51 - IMPRIMIR PEDIDO-CRIACAO RELATORIO - PARTE A

DICAS 3029 - WINDEV TUTORIAL 52 - IMPRIMIR PEDIDO - CRIAR O RELATORIO BASE QUERY - PARTE B

DICAS 3030 - WINDEV TUTORIAL 53 - IMPRIMIR PEDIDO - ALTERACOES RELATORIO - PARTE C

DICAS 3031 - WINDEV TUTORIAL 54 - IMPRIMIR PEDIDO - MENU RELATORIO - PARTE D

DICAS 3032 - WINDEV TUTORIAL 55 - RELATORIO LISTA CLIENTE - PARTE A

DICAS 3033 - WINDEV TUTORIAL 56 - RELATORIO CLIENTE - Imprimir - PARTE B

DICAS 3034 - WINDEV TUTORIAL 57 - ESTATISTICAS GRAFICO PIVOT - QUERY ANO - PARTE A

DICAS 3035 - WINDEV TUTORIAL 58 - ESTATISTICAS GRAFICO PIVOT - GRAFICO-PARTE B

DICAS 3036 - WINDEV TUTORIAL 59 - ESTATISTICAS - PIVOT - PVT - PARTE C

DICAS 3037 - WINDEV TUTORIAL 60 - ENVIAR EMAIL - ADICIONANDO CAMPOS - PARTE A

DICAS 3038 - WINDEV TUTORIAL 61 - ENVIAR EMAIL - CODIGO - PARTE B

DICAS 3039 - WINDEV TUTORIAL 62 - ENVIAR EMAIL - MELHORIAS - PARTE C

DICAS 3040- WINDEV TUTORIAL 63 - GROUPWARE - CONFIGURACAO - PARTE A

DICAS 3041- WINDEV TUTORIAL 64 - GROUPWARE - TESTE - PARTE B

DICAS 3042- WINDEV TUTORIAL 65 - COMPONENTES EXTERNOS - CRIANDO - PARTE A

DICAS 3043 - WINDEV TUTORIAL 66 - COMPONENTES EXTERNOS - USANDO - PARTE B

DICAS 3044 - WINDEV TUTORIAL 67 - CONSUMINDO SERVICO WEBSERVICE

DICAS 3045 - WINDEV TUTORIAL 68 - MONITORAR EVOLUCAO SEUS APLICATIVOS - TESTES

DICAS 3046 - WINDEV TUTORIAL 69 - DEPLOYING APPLICATION CRIANDO EXECUTAVEL PARTE A

DICAS 3044 - WINDEV TUTORIAL 67 - CONSUMINDO SERVICO WEBSERVICE

quiZkDpFqhw

Bom Dia/Boa Tarde/Boa Noite

Esse Ao Vivo vai estrear as 14:00 do dia 01/09/2020

DICAS 3044 - WINDEV TUTORIAL 67 - CONSUMINDO SERVICO WEBSERVICE

Tutoriel WINDEV : Leçon 4.12. Consommer un Webservice

https://windevdesenvolvimento.blogspot.com/2020/08/dicas-3044-windev-tutorial-67.html

ASSUNTOS

EXPLICANDO O QUE É WEBSERVICE

EXPLICANDO O EXEMPLO PRATICO

EXPLICANDO COMO FAZER A IMPORTACAO DO WEB SERVICO

IMPORTANDO O WEBSERVICE

MOSTRANDO O LOCAL ONDE FICA O WEBSERVICE

EXPLICANDO O QUE SIGNIFICA O QUE ELE TROUXE

CRIANDO O BOTAO PARA BUSCAR ESTOQUE

EXPLICANDO O CODIGO

EXECUTANDO O APLICATIVO

LINK DO WEBSERVICE

https://exemples.webdev.info/WSAUTOFORMATIONV2_WEB/awws/WSAutoformationV2.awws?wsdl

https://doc.windev.com/en-US/?1410087526&name=lesson_412_consuming_webservice

Video original da Franca

https://youtu.be/cQexMInRYbc

Playlist Windev TUTORIAL

https://www.youtube.com/playlist?list=PLwJwZaqiZW-lxU1XF0M0htb5S5f8pavuE

https://youtu.be/3DshsXJ8I2M

========================

//btn em estoque

// Displays the Webservice response

// Exibe a resposta do webservice

InfoBuild("Produto de %1 em Estoque : %2",COL_Reference,ProduitEnStock(COL_Reference))

ErpMatos - TgsSistemas

skype:amarildo.matos.informatica

email: amarildo.matos@gmail.com

whats: 51984197742

Youtube: Amarildo Matos

http://www.amarildomatos.com.br

https://groups.google.com/forum/#!forum/amarildowindev

www.windev.com

https://www.pcsoft.fr/webinaires.htm?p=forumpcs

https://forum.pcsoft.fr/fr-FR/pcsoft.br.windev/page/1.awp

https://www.windev.com/windev/WD-Express.htm

https://www.windev.com/windevmobile/WM-Express.htm

http://windevdesenvolvimento.blogspot.com.br/2017/07/menu-blog.html

Lesson 4.12. Consuming a Webservice

This lesson will teach you the following concepts

Overview.
Importing and consuming a Webservice.


	Estimated time: 10 mn

Previous Lesson

Table of contents

Next Lesson

Overview

In most cases, a Web service is defined as an application that can be accessed via standard Internet protocols. More specifically, Web services allow several computers connected via Internet to interact.

Web services allow you to run procedures and processes on a remote Web server (.NET, SOAP or J2EE) from a client computer.

With WINDEV, these Web services can be used as client, via the SOAP protocol on HTTP (the standard Internet protocol for transferring HTML pages), with the SOAPxx, DotNetxx and J2EExx functions.

Regardless of the platform of the Web server (.NET, J2EE, ...), a Web service is accessible via the SOAP protocol.


	Remark	With WINDEV, you don't even have to be an expert in this field. A wizard takes care of ("almost") everything!

Practical example

A Webservice specific to this tutorial allows you to check the different operations that can be performed on a Webservice.

When integrated to the "WD Full Application" project, this Webservice is used to interrogate a supplier database to check whether a product is available in stock using its reference.

In a first time, the Webservice will be imported into the "WD Full Application" project then it will be used in the application to check the product availability from a Product form.

Importing a Webservice

Close the current project if necessary. The WINDEV home page is displayed.

In the home page, click "Tutorial" and select "Full application (Exercise)". The project is loaded.


	Answers	If you did not create the windows in the previous lessons, you can follow this lesson by opening a corrected project: in WINDEV's home page (Ctrl + <), click "Tutorial" and select "Full application (With windows)". A full corrected application project is also available: in WINDEV's home page (Ctrl + <), click "Tutorial" and select "Full application (Answer)"

Position (if necessary) on the "32-bit Windows executable" configuration: in the "Project explorer" pane, in the "Configurations" folder, double-click "Windows 32-bit executable".

To import a Webservice into the project:
1. On the "Project" pane, in the "Project" group, expand "Import" and select "A Webservice".
2. The import wizard starts. Go to the next step.
3. Specify the address into which the WSDL description of the Webservice must be imported:
  https://examples.webdev.info/WSTUTORIALV2_WEB/awws/WSTutorialV2.awws?wsdl
  
  Reminder: This Webservice is used to interrogate a supplier database to check the availability (stock) of a product from its reference.
4. Go to the next step. The Webservice is imported.
5. Validate the information window. The imported Webservice is in the "Imported Webservices" folder of the "Project explorer" tab pane.
6. In the "Project explorer" pane, expand the "Imported Webservices" folder.

Let's take a closer look at the information displayed in the "Project Explorer" pane:

The structure includes:

the Webservice name (WSTutorialV2 in this example),
the name of each function (ProductInStock in this example).

To find out how to call the Webservice, simply double-click the name of the function in the "Project explorer" pane. The code editor displays the function description, with the prototype for calling the function:

Consuming a Webservice

In our "WD Full Application" example, the call to the Webservice will be included in the tab used to see the list of products. A button "In stock?" is used to check whether the product displayed via the Webservice is available.

To use the Webservice:
1. Open the "WIN_Menu" window in the editor (double-click its name in the "Project explorer" pane, for example).
2. Add a Button control in the "List of products" tab pane:
  - On the "Creation" pane, in the "Usual controls" group, click .
  - Click below the "Modify " Button control in the window.
  - The control is automatically created.
3. Modify the characteristics of the control ("Description" from the popup menu). This control is named "BTN_InStock" and its caption is "In stock?".
4. Display the events associated with the control ("Code" from the popup menu).
5. Write the following WLanguage code in the "Click BTN_InStock" event:
  // Displays the Webservice response
  InfoBuild(...
  "Number of ""%1"" products in stock: %2", ...
  COL_Reference, ProductInStock(COL_Reference))
  Let's study this code:
  - The ProductInStock function of Webservice is called. This code uses the function prototype that was displayed beforehand in the code editor.
  - The response is formatted and displayed.
6. Close the code editor and save the window ( or Ctrl + S).

We are going to check the operating mode of Webservice:
1. Run the project test ( among the quick access buttons).
2. Click the "List of products" tab if necessary.
3. Select any product in the Table control and click "In stock?".
4. Validate the information window and close the application.