Third Party Management Integration

1. Own theJava Open JDK 11 installed;
2. Make sure that the "JAVA_HOME_SAM" environment variable has been added with the value of the directory where Open JDK 11 was installed. For example: C:\jdk-11.0.2\ ;
3. Have RabbitMQ installed and configured. For information on how to do this, access the documentation onRabbitMQ.

4. Configure the on-premises environment on the senior X Platform

5. On the senior X Platform, access Technology > Settings > By Tenant, with the tenant administrator user;
6. Enter the following fields:
   • RabbitMQ on-premises HTTP URL. Example: http://[Servidor_Rabbit_On_Premises]:15672;
   • RabbitMQ on-premises user;
   • RabbitMQ on-premises user password ;RabbitMQ on-premises AMQP URL. Example: amqp://[Servidor_Rabbit_On_Premises]:5672.

7. Still on the senior X Platform, access Technology > Administration > Tenant Management > Services/Components, with the tenant administrator user;
8. click inTo update is at Apply to the environment.
9. Test the connection using the test option available on the screen. If the connection is not adequate, review thehybrid environment installation prerequisites and the settings presented in step 6.

To install the Integrator, consult the Integrator documentation.Integrator.

1. After installation, follow all the steps described in the Configure the Integrator item in the software documentation.Integrator.
2. In the RabbitMQ On Premises Information panel, fill in the fieldsUser,Password It isAddress;

Important

If Rabbit is using port 5672 (AMQP), it will only work with the host in the fieldAddress. Example: localhost.

However, if you are using port 5671 (AMQPS), you must inform theAddress o host:port. Example: localhost:5671.

2. click inTo save.

In the documentation forIntegrator We provide an explanation of how it works through initial loading and handling of pending issues.

For the proper functioning of Third Party Management, the initial charge must be carried outall the items listed in the Collaborators, Third Party Management, Devices and Organizational Structure sections, and in addition the Physical Location and Photo items in the Miscellaneous section. However, if there is integration with Ronda Senior and the user wants to use thedefault settings, you must perform the following steps in order:

• Carry out the initial loading of the Senior Round, marking all items except those for Third Party Management;
• Access the senior X Platform and registerdefault contract settings;
• Finally, carry out the initial loading of the Third Party Management items.

Check that registered companies have a valid and non-duplicated CNPJ. Otherwise, these companies, the contracts and third parties associated with them will not be integrated.

Also check that contract histories are properly associated with contracts, as the initial load will only bring histories associated with contracts. Changes to non-contract histories will not be integrated. Additionally, contract histories integrated with Ronda senior X should not be edited in Ronda Senior. A rule must be configured to block these edits, as detailed in the sectionConfigure edit blocking rule in Ronda Senior.

Timing

Here we list the data that is and is not synchronized between systems during integration.

OfSenior Round for the Senior round:

• From company registrations: Other Company, Last Name, CNPJ, CEI, E-mail, Telephone, Fax and all address fields;
• From contract records: Start date and end date;
• Third party records: History of current and future third parties whose company and contract are linked to Ronda senior X (the information must be equivalent between the systems).

To consult the Senior Ronda histories that go to Senior Ronda

OfSenior round to the Senior Round:

• Regarding company and contract registrations: Nothing that is registered in Ronda senior X is sent to Ronda Senior;
• Third parties: a new third party is generated in Ronda Senior. Your CPF and the Other Company are normally sent between the systems. The branch, location, schedule and badge are entered in the BPM. The admission date and period in the Senior Ronda are based on the start date of the contract and the period of contract in the Senior Ronda X, respectively. Ultimately, the situation is based on the end date in Senior Round X.

Other registrations made in Ronda senior X, such as inclusion of ordinances, types of visits and procedures, are not synchronized with Ronda Senior.

As explained in sectionInitial load and pending issues for using Third Party Management, Ronda Senior's integrated contract histories cannot be edited in this system. To block this edition, a rule must be created in the Ronda Senior Rules Editor, using the following code, and added to the Contract Histories screen (FR038HCT).

Define Number xIntegrated;

Set Alpha xMsg;

 Set Number xNumEmp;

 Set Number xTipCol;

 Define Number xNumCad;

 Set Date xDatAlt;

xNumEmp = R038HCT.NumEmp;

 xTipCol = R038HCT.TipCol;

 xNumCad = R038HCT.NumCad;

 xDatAlt = R038HCT.DatAlt; 

 Set Cursor Cur_SAM_LINKS;

Cur_SAM_LINKS.SQL "SELECT UUID FROM SAM_LINKS \

 WHERE TIPOIDSAM = 45 \

 AND INT1 = :xNumEmp \

 AND INT2 = :xTipCol \

 AND INT3 = :xNumCad \

 AND DATE1 = :xDatAlt"; 

 Cur_SAM_LINKS.OpenCursor();

If (Cur_SAM_LINKS. Achou)

Start

 xIntegrated = 1;

End

if not

 Start

 xIntegrated = 0;

 End;

 Cur_SAM_LINKS.CloseCursor(); 

 if (xIntegrated = 1) {

 xMsg = "This contract history cannot be changed or deleted,\

 as it is already integrated with Ronda senior X - Third party management.";

 Message(Error, xMsg);

}

Perform the following steps:

• Access the Resources > Implementations > Rules Editor screen;
• Create the new rule using the code above. Save and compile the rule;
• To associate the rule with the Contract History screen, open it in People > Collaborators > Histories > Contracts;
• Right-click and choose the Rules by Event option;
• Associate the rule with the Before Change and Before Delete events.

With this, the system will check whether the contract history is related to the Third Party Management of Ronda senior X, preventing the change or deletion of the record if this is the case.

1. Open the Senior X Platform menu > BPM >Law Suit;
2. Click on the itemForm and then on the buttonConsistency Rules;
3. In the window that opens, define the fieldWhen as "Submit the form";
4. In the fieldValidate, add a rule similar to the code below to validate the roles

${role_name} == 'Employee' || ${role_name} == 'Third' || ${role_name} == 'Partner' || ${role_name} == 'Visitor' || ${role_name} == 'Patient Companion' || ${role_name} == 'Student' || ${role_name} == 'Student Responsible' || ${role_name} == 'Patient';

5. In the fieldAction, select the "Consist" option;
6. Define aMessage for the custom rule. Suggestion: "The selected role must be associated with a Ronda XT device permission."

For more information about consistency rules for forms, see the itemCreate a new rule from theECM Form documentation.

1. Open the menu Technology > Administration > Authorization >Paper Management;
2. Select the role created for Contract Data Reviewer;
3. Access the Filters tab and, in the Domain/Service list, locate the item "sam/application";
4. Click this item to show the action buttons;
5. Click on the buttonNew;
6. The filter configuration fields will be shown. In the fieldPaper, enter the name of one of the roles you want to filter;
7. Repeat steps 6 and 7 for each of the roles that must be filtered, until all are defined;
8. Click on the buttonTo save.