Standardization of products in PO UI (BackOffice)

All captions or statuses used in a Browse must follow the guidelines below:

• Alignment to the left of the table;
• Preferably use the "labels" format;
• Avoid long captions/statuses
  • Use a tooltip to detail the status if needed.
• Fixed label size considering the longest text.

The columns of a browse must follow the same format and name as Protheus.

• Use field titles from the SX3 dictionary
• Order using field list from SX3

It has been set that, for the Advanced Filter option, the slide pattern must be used as proposed below:

For the behavior of the Browse filter in PO UI, it has been set that it must occur automatically, i.e., when the user does not enter anything into the search field for an interval over 3 seconds, a new search must be performed to the Back-End automatically. This search is interrupted if the user continues typing and is performed again if a new interval without typing occurs. Below is an example of the automatic search behavior, without the need to enter the entire code and trigger the search button:

• The buttons of a browser that set the initial actions are positioned to the left, followed by a filter with the advanced search option.

• A Browser that does not have buttons in its initial definitions, but has the search and advanced search options, is aligned with the title.
• The buttons positioned in the footer must be aligned to the right, and, in the case there are many options, use a dropdown with related actions, but do not put all screen actions in a single dropdown, otherwise, the screen's dynamism is lost. 

References:

• • https://po-ui.io/documentation/po-page-list
  • https://po-ui.io/documentation/po-dropdown

For routines with a greater need for colors or tone variations, you may use the colors standardized in the GetColorChart method of the CoreDash class according to the class details. If a greater number of colors is needed, this must be previously agreed upon, and the new colors must be added to the color chart below for use in the entire BackOffice.

Although each project has its particularities, we reserve some caption colors that should be used whenever it is necessary to represent the status assigned to it. Other statuses that were not defined in this standardization will have their colors assigned by the product individually, considering their needs.

The statuses defined are:

• "Disabled" and "Finished"  - Red (color-10)
• "Enabled" and "Open"     - Green (color-07)

It has been set in a meeting that screens containing the row action column must position it to the left, as in the example:

LGPD - Field Overshadowing

It has been set that the field overshadowing pattern for LGPD will be the display of a TAG with the RESTRICTED word.

Component: po-tag, color-07, p-inverse=true

Example of use:

Login using Protheus:

The language presented in the routines must be the same one selected in the login made on SmartClient according to the image below:

Login using Mingle:

When using the PO UI routines through the browser using the Mingle login, the language selected at the login time must also be displayed, even if the browser language is different:

NOTE: The pre-selected language on Mingle's Login screen must be following the language set on the browser if an equivalent translated language exists. If no translation for the browser language exists, the default language must be Portuguese, but if it is manually changed, the language selected by the User will be used.

The display of numeric and/or monetary fields must follow the same standard used in Protheus ERP applications, that is, following the definitions used in the configuration of the respective environments using the PICTFORMAT key. When it is set to DEFAULT, the display format must be ',' (comma) as a decimal separator and '.' (dot) as a thousand separator. When set to AMERICAN, the display format must be '.' (dot) as decimal separator and ',' (comma) as thousands separator, even if, in the data dictionary of the corresponding field, picture (X3_PICTURE) is set to '@E'.

NOTE: To check the content of the AppServer keys within the APIs, use the function GetSrvProfString.

• When accessing the application, the company and branch registered as default in TOTVS Mingle must be used.
• Selection or Change of Branches must occur only after the user logs in to the application;
• The Branch Swap option should be a toolbar option and follow the model below:

Purpose: On this page, register the official documentation and some tips for implementing the pipeline-poui.

Complete DevOps team documentation on pipeline-poui

https://code.engpro.totvs.com.br/engpro-devops/pipeline-poui

Shipment of .app

• Shipping the .app file: THF Shipment(.APP)
• Shipment of .app file by the Compilation Spool: Process of sending THF(.App) files using the compilation Spool
  
  

Example of generating a new stable version in gitea

Positioned in your remote repository, in the branch where your new version will be based, execute the following commands (use the git terminal of your choice):

Accessing the repository in gitea, in the Versions tab, we will have a new tag with the previous version status:

Before changing the version to the stable status, it is important to check if all the drone steps have been successfully executed:

To change the status of the version to Stable, just click edit in the version title:

On the screen that appears, deselect the "Mark as Pre-Release” option:

After this last step, the version will be in Stable status and ready to be compiled in D-1 if your webhook (see documentation) is already configured:

The standard for API documentation is OpenAPI v3.

To speed up documentation, we have the engineering tool with a graphical interface on the link:  OpenAPI-GUI v3

Another tool is the OpenAPI extension of VSCode. In it, we can write the yml file and view it using the Swagger UI.

Definition...

Example:

Check below the documentation FAQs for BackOffice Products developed in PO UI with a general target audience, that is, intended for Developers, Technical Support, and also for Customers:

FAQ - Dashboard BackOffice

FAQ - Sales Management Portal

FAQ - Track Costs (Note: at the end of the page)

Below is the link to access the documentation of a FAQ for the Technical Support team to support Customer tickets:

PO UI - Support Document

Definition...

Example: