This guide is for Tenacy Global Pilots and Administrators in charge of integrating with your ITSM tools. The EasyVista connector simplifies synchronization between Tenacy's actions and recurring tasks and EasyVista tickets:
Actions or recurring tasks created in Tenacy are automatically generated as tickets in EasyVista, based on a predefined mapping.
Any status change on an EasyVista ticket is automatically reflected on the corresponding object in Tenacy.
⚠️ Actions or recurring task occurrences created before the connector was configured will not be synchronized with EasyVista.
Adding and configuring the connector
To add this connector, go to Catalog > Connectors > Easyvista > Add a connector.
Once the connector is added, start the configuration:
The following details are required for a correct configuration:
Authentication data: URL, Token.
Default language: when a ticket is created in EasyVista, its content is written in the language assigned to the Tenacy object's manager. If no single manager is designated, the language specified here is used instead. This matters if you describe your actions or recurring tasks in both English and French.
Synchronization type: specify whether you intend to create EasyVista tickets from actions or from recurring tasks. ⚠️ If both, separate connectors are required for each.
Register: a register is the Tenacy space where your actions or recurring tasks are organized into groups. Identify the register to synchronize from here. ⚠️ For multiple registers, separate connectors are required.
Subject mapping: map the correspondence between the chosen register's groups and EasyVista subjects. These subjects will be linked to EasyVista tickets generated from tasks or actions within those groups. Objects from unselected groups will not be synchronized.
Status mapping: define the equivalences between EasyVista and Tenacy statuses.
Additional field mapping (optional): add any additional fields you want to fill via the API (particularly mandatory fields in EasyVista) along with the fixed value to associate.
💡 The data synchronized by default from actions or recurring tasks is:
Subject
Title
Description
Creation date
Recipient
Requester
External ID
How the connector works
Here are several rules to know when using your connector:
If an action or recurring task is moved from the register configured in Tenacy to a non-configured register, the ticket remains in EasyVista but the link is removed. As a result, any future change to the action/recurring task will not be synchronized, even if the action/recurring task is moved back to its original register.
Deleting, cancelling, or completing actions/recurring tasks in Tenacy does not delete the corresponding ticket in EasyVista.
Any change to the name and description of the action/recurring task in Tenacy is also updated in the EasyVista tickets.
Recurring tasks
When a recurring task is created (control or operation task), if a completion is required for the current period (based on the task's start date), a ticket is generated in EasyVista and linked to that completion.
For each new period (and for each period type), a new ticket is created in EasyVista.
Every hour, completions linked to EasyVista tickets are checked. The EasyVista ticket's status is retrieved and synchronized with the Tenacy recurring task according to the status mapping.
When the status changes to DONE or NOT DONE, and if the recurring task's completion requires proof, the EasyVista URL is added as proof.
Actions
When an action is created, a ticket is generated in EasyVista and linked to that action.
Every hour, actions that are not closed (to be planned, planned, on hold, in progress) and linked to EasyVista tickets are checked. The EasyVista ticket's status is retrieved and:
If the status is mapped to a Tenacy status in the configuration module, the action's status in Tenacy is updated accordingly. If this update requires a start date and a target date that the action doesn't have yet, the start date is set to the EasyVista ticket's creation date and the target date is set to that date + 7 days.
When the status changes to completed, and if the action requires proof, the EasyVista URL is added as proof.
Running your first test
Once the connector is properly configured, test the integration by creating a new test action or recurring task in Tenacy.
This creation triggers the connector's execution.
To check that it worked correctly, go to ⚙️ > Connectors > click your Easyvista connector > then click the latest execution line to check whether it ran successfully.
💡 Feel free to contact Tenacy support if you have any questions about this.
Frequently asked questions
Can I synchronize both actions and recurring tasks with a single EasyVista connector?
No, a connector can only synchronize one type of object at a time. If you want to synchronize both, you need to create two separate EasyVista connectors.
What happens if I move an action to a register that isn't configured in the connector?
The existing EasyVista ticket isn't deleted, but its link with Tenacy is. No future changes to the action will be reflected in EasyVista, even if you move the action back to its original register.
Can the connector synchronize actions or tasks created before it was configured?
No. Only actions and recurring task occurrences created after the connector was set up are synchronized.
What happens if I delete, cancel, or complete an action in Tenacy?
The corresponding ticket in EasyVista is not automatically deleted or modified.