Index
Índice |
---|
maxLevel | 5 |
---|
outline | true |
---|
indent | 8.1.1 |
---|
exclude | .*ndiceIndex |
---|
style | none |
---|
|
Purpose
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 |
---|
effectDuration | 0.5 |
---|
history | false |
---|
id | samples |
---|
effectType | fade |
---|
|
Card |
---|
default | true |
---|
id | 1 |
---|
label | REST Server Configuration |
---|
| To enable REST in Microsiga Protheus®, edit the appserver.ini configuration file with the following content. To avoid conflict, be mindful of the communication ports used: [HTTPV11] Enable=1 AddressFamily=1 Sockets=HTTPREST TimeOut=120 [HTTPREST] Port=8889 IPsBind= MaxQueue=10 URIs=HTTPURI SECURITY=0 [HTTPURI] URL=/ PrepareIn=99,01 OnStart=REST_START OnConnect=REST_CONNECT OnExit=REST_EXIT Instances=1,10 [ONSTART] jobs=HTTPJOB [HTTPJOB] MAIN=HTTP_START ENVIRONMENT=P12 You also need to add item MAXSTRINGSIZE=10 in [General] and of FWFRAME_TRACELOG=0 in the environment block. The configuration above follows the Protheus REST defaults; therefore, if the resource is already enabled in Protheus, you do not need to make any changes. You can use authentication HTTP Basic or Auth 1.0a. To do so, change item SECURITY [HTTPREST] to 1 or delete it. |
Card |
---|
default | true |
---|
id | 2 |
---|
label | Parametrização | Parameter Settings |
---|
| Click option +Initial Load and view the parameters settings screen, as follows: Information Confirm in Execute to continue after filling out the Questions or Cancel. Questions Fill out the fields as needed. Processes Log Processing. The screen displayed shows each record of the queue composed by the following fields: Fill out the information in accordance to the instructions in Main Fields Clique na opção +Carga Inicial e visualize a tela de parametrização sendo: Informações Confirme em Executar para prosseguir após preencher as Perguntas ou Cancelar. Perguntas Preencha os campos conforme a necessidade. Log de Processos; Processamento; A exibição da tela mostra cada registro da fila composto pelos seguintes campos: Preencha as informações de acordo com as orientações descritas em Principais Campos. |
Card |
---|
id | 3 |
---|
label | Outras Ações Other Actions / Pesquisar |
---|
| Permite a pesquisa de informações com a utilização de filtros que as ordenam, baseado no índice selecionado considerando, por exemplo, a filial+código. Image Removed
|
|
...
| It allows you to search the information by using filters to organize it based on the index selected, considering, for example, the branch+code. Image Added
|
|
Main Fields
Âncora |
---|
| principaiscampos |
---|
| principaiscampos |
---|
|
...
CampoDescrição | CódigoNúmero sequencial de identificação do registro | Modelo | Nome do modelo de dados modificado. No exemplo de tipo de tabela de serviços, trata-se do JURA047. |
Chave | Chave primária de identificação do registro no modelo de dados. Neste caso e na grande maioria a chave é composta pela filial + código. |
Operação | Código da operação onde, 3 é inclusão, 4 alteração e 5 exclusão. |
TImeStamp | Data e hora da manipulação. |
Status | Situação do registro onde 1-Pendente indica que o sistema LegalDesk ainda não integrou e 2-Concluído para quando já tiver sido feita a integração do registro. Lembrando que a mudança desta situação está sob responsabilidade do LegalDesk. |
Conteúdo Relacionado
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. |
Related Content
LegalDesk Syncing Parameters (jura171)
Expenses Parâmetros Sincronização Legal Desk (jura171)
Despesas (jura049)
TimeSheet-Movimentações Transactions (jura144)
Lançamento Tabelado Table Entries (jura027)
Clientes Clients (jura148)
Casos Cases (jura070)