...
Índice | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|
|
LegalDesk is a system developed by the TOTVS JuriTIs franchise, with the purpose of offering a more modern and friendly interface for various operations executed by lawyers and partners in law offices.
Among these operations are: time sheet entries, expenses, table entries, creation of provisional cases, proforma invoice revisions, etc.
With the possibility of entries via LegalDesk and invoicing via SIGAPFS, it becomes necessary to integrate information between both systems. Thus, the aim of the syncing queue is to enable the process of sending information to LegalDesk, controlling the changes to registers and transactions in SIGAPFS and required for its operation.
Any addition, editing or deletion of the entries expected for integration in SIGAPFS are registered in the syncing queue. LegalDesk accesses the queue to query what to update in its database and is responsible for recording, in the same queue, what is already up-to-date.
Operations via LegalDesk, such as the creation of time sheets and expenses, are registered in SIGAPFS by LegalDesk itself.
Integration with LegalDesk is available from Microsiga Protheus 11.8 onward and, to use it you need to enable the REST server in the Protheus Application Server and to set parameter MV_JFSINC to 1 = Yes.
For further information regarding the operation of REST, query http://tdn.totvs.com/display/tec/REST .
Aviso | ||
---|---|---|
| ||
Risk Warning: be careful when using the configuration parameter with key Security=0, because causes the integrations (APIs) to not require authentication; consequently, anyone may query your environment's data without any authorization control. |
On the main page of the routine, find the following options:
Deck of Cards | |||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||||
|
Âncora | ||||
---|---|---|---|---|
|
...
Field | Description |
Code: | Sequential number of record identification. |
Model | Name of modified data model. In the example of services table type, it is JURA047. |
Key | Primary key for record identification in data model. In this case, as in most cases, the key is composed of branch + code. |
Operation | Operation code in which 3 is addition, 4 editing and 5 deletion. |
TImeStamp | Date and time of operation. |
Status | Status of record in which 1-Pending indicates the LegalDesk system has not yet integrated the record and 2-Finished indicates when the integration of the record is already done. Remember that LegalDesk is responsible for changing this status. |
LegalDesk Syncing Parameters (jura171)
Expenses (jura049)
TimeSheet-Transactions (jura144)
Table Entries (jura027)
Clients (jura148)
Cases (jura070)