Histórico da Página

Índice
maxLevel 4

01. OVERVIEW

Set of features for the client to manage financial activities in an agile way with a modern interface.

02.  CONFIGURATION

REST ADVPL

• Add sections to the appserver.ini according to this example.

Further information on this configuration, access the page Application Server - REST ADVPL.

[HTTPV11] 
Enable=1 
Sockets=HTTPREST 
 
[HTTPREST] 
Port=8084
URIs=URIHTML
SECURITY=1
 
[URIHTML]
URL=/html-protheus/rest
PrepareIn=All
Instances=2,2
CORSEnable=1
AllowOrigin=*

[ONSTART]
jobs=HTTPJOB
RefreshRate=30 

[HTTPJOB]
MAIN=HTTP_START
ENVIRONMENT=environment 

HTTP Section

• Add sections to the appserver.ini according to this example.
• Extract project built in the directory set in the HTTP section.
• Edit the appConfig.json file, serverBackend edited according to IP and REST - ADVPL Port set, according to the example below.

Further information on this configuration, access the page Application Server - Seção HTTP.

[HTTP]
enable=1
port=8080
path=D:\TOTVS\Protheus_Data\web\portal-cliente
defaultpage=index.html

{
  "name": "Portal do Cliente",
  "version": "12.1.27-0.1.0",
  "serverBackend": "http://localhost:8084/",
  "restEntryPoint": "",
  "versionAPI": "",
  "productLine": "Protheus"
}

Mingle

Mingle is the platform available as service to support TOTVS applications. It resolves three main customers' needs, Authentication, API Gateway and Metrics. It does this without the products having to expose their APIs directly, allowing applications to consume them in a controllable way. For further information access the TDN page.

For the Customer Portal access, request a single ALIAS according to these steps:

Access link Mingle, click "Request Alias", and fill it out according to the image below:

Image Added

Where:

• E-mail: e-mail address linked to the Mingle registration.
• Select App: select "Customer Portal".
• Select backend: enter the backend public address, according to the configurations previously set.
• Server Name: identification of the server in the Mingle.
• Register/Edit companies and branches: enter company and base branch code for the backend (see example below).
• Register authentication accreditation: enter Protheus password and login the authentication base user in the Mingle (see example below).

Image AddedImage Added

Wait the return via e-mail with the ALIAS created and other information.

These parameters must be updated with data received by the Mingle team:

• MV_MINGTOK: Access Token for requests to Mingle.
• MV_MINGIUS: User Login used in the Authentication Accreditation.

03. REGISTRATIONS

WEB SERVICES

...

PORTAL USERS

...

04. FEATURES

Login

...

Home

...

Invoices

...

Bills

...

...

Data Selection

New feature to select branch and customer for the customer portal session. This resource affects data displayed in the portal, respecting the branches and customers selected.
After logging into the system, click on the user profile button, located at the top right of any screen, and select the "Data Selection" option.

Image Added

Image Added

User is redirected to the step by step of "Data Selection" to see theses steps: Branches, Customers and Confirmation.

Branches

In this step, the user can select one or more branches used in the portal.

Enter at least one branch.

After selecting the branches, click button Next to proceed with the next step.

Image Added

Image Added

Image Added

Customers

In this case, select the customers of the branches. You can select one or more customers.

Enter at least one customer.

After selecting the customer, click button Next to proceed to the next step.

Image Added

Image Added

Image Added

Confirmation

Last step of the process, in which the user view all the values selected in the previous steps, customers and branches. The records displayed are summarized by the customers selected with the customer's branches. To display branches, click customer record.

To finalize the process, click the Confirm button.

When confirming, the user will be redirected to the previous screen of the "Data Selection" request, that is, the screen the user was before clicking "Data Selection".

Image Added

Image Added

Image Added

Image Added

<!-- esconder o menu --> 


<style>
div.theme-default .ia-splitter #main {
    margin-left: 0px;
}
.ia-fixed-sidebar, .ia-splitter-left {
    display: none;
}
#main {
    padding-left: 10px;
    padding-right: 10px;
    overflow-x: hidden;
}

.aui-header-primary .aui-nav,  .aui-page-panel {
    margin-left: 0px !important;
}
.aui-header-primary .aui-nav {
    margin-left: 0px !important;
}
</style>

CONTENT

1. Overview
2. Exemple of use
3. XXX Screen
   1. OtherActions / Related Actions
      
4. XXX Screen
   1. Main Fields and Parameters
      
5. Tables

01. OVERVIEW

02. EXEMPLE OF USE

03. XXXX SCREEN

Other Actions / Related Actions

...

04.  XXXX SCREEN

Main Fields and Parameters

...

...