Linha Microsiga Protheus - Inglês

Páginas filhas
  • DT_BPM_Consultive_and_Contracts

BPM_Consultive_and_Contracts

Requirement Characteristics

Product Line:

Microsiga Protheus®

Segment:

Legal

Module:'

SIGAJURI

Routine:

Routine

Technical Name

JURA095

Legal Matters

Routine(s) involved

Technical name

JURA014

Configuration Report / Legal Matter Type

JURA134

Contract Type

Start Registers:

Configuration of Process Research (JURA163).

Parameters:

MV_ECMUSER, MV_ECMPSW, MV_ECMEMP,MV_ECMURL,MV_JWFCONS

Requirement (ISSUE):PCREQ-5756

Country(ies):

All

Database:

All

Tables Used:

  • NSZ – Legal Matters;
  • NTA – Follow-up;
  • NQS – Follow-up Type;
  • NY0 – Contract Types;
  • NQY – Report configuration;

Operational System(s):

Windows®

Versions/Release:

12.1.7

Description

The implementation aims at enabling the contracts, queries/reports are started and controlled by FLUIG.

These queries and contracts are automatically registered in SIGAJURI.

One of the main fields of SIGAJURI is the use responsible by the query or contract. For these items to be properly distributed, Widgets enabling the configuration of distribution of queries and reports and configuration of distribution of contracts were created so you can define the employees in charge of SIGAJURI.

When creating a request through Fluig, a request is sent to the responsible party, so a process and a Follow-up are created in SIGAJURI.

When executing and changing the status of the request in Tasks Central in Fluig, the changes reflects in SIGAJURI, changing the Follow-up status.

After this, the request answer is sent to requester.

Accessing the Tasks Central, the requester also changes the request status. With the approval, the change reflects in SIGAJURI closing the process.

Within the contracts workflow, there is a stage of generation of minutes of automatic method on the part of SIGAJURI. So this resource properly works, the requirements below must be met:

1- Installation of Microsoft Office in the servers where the AppServer of Protheus is executed.

2- A SmartClient must be configured in server pointing to the proper environment and the proper connection as well.

3- A key called SMARTCLIENTPATH must be added to file AppServer.ini in the environment used, with the path of the executable of this Smartclient that was configured. Ex:

{P12]

SMARTCLIENTPATH=C:\TOTVS 2.0\p12\protheus12\bin\smartclient\SMARTCLIENT.exe

Procedure for Widget Configuration

Configuration of Contract Distribution

  1. Access FLUIG and then the page Legal settings.
  2. Configure the Contract distribution widget.
  3. Select a Legal matter and then a Contract type.  
  4. Select a Responsible user and the Distribution priority.
  5. Select the Return term.
  6. Once it is done, click Save.

 

Configuration of Queries/Reports Distribution

 1. Access FLUIG and then the page Legal settings.


  1. Access FLUIG and then Legal Settings.
  2. Configure widget of Queries/Reports Distribution.
  3. Select a Legal Subject then a Type of request.
  4. Select a Responsible user then the Distribution priority.
  5. Select the Return term.
  6. Once it is done, click Save.




PARAMETERS CONFIGURATION 

List of parameters

Name

Description

MV_ECMUSER

User with administration privileges on ECM.  (Ex [email protected])

MV_ECMPSW

Enter the password of the user with administration privileges on ECM.                                 

MV_ECMEMP

Company code for integration with ECM. (Ex 100)

MV_ECMURL

Enter the URL of integration with ECM. (Ex http://fluig.com.br:8080/webdesk)

MV_JWFCONS

Parameter that saves the workflow ID of inclusion of Queries/Opinions of activities created on FLUIG.

 

Procedure for Usage

 

  1. Access the Fluig environment and then the Task Central.
  2. Click start a new request.
  3. Select the SIGAJURI process, then Queries/Opinions or Contract request.
  4. Complete the request fields.
  5. Click Transact. In this moment a process is created on SIGAJURI and a Follow-up for the responsible.
  6. The responsible receives a pending task notification in its Task central.
  7. After the execution, the responsible clicks in Transact, the reply is submitted to the requestor, and the Follow-up status is changed to completed.
  8. The requestor accesses the Fluig environment and then the Task central.
  9. Checks the reply and clicks Transaction and the process is completed on SIGAJURI.