HaloPSA: Setup + Integration Overview

Integration with HaloPSA allows project/ticket data to be brought into Moovila to take advantage of powerful project management functionality. Here's how to connect them:

1. Before HaloPSA can be integrated with Moovila there are several steps to be taken within Halo to set up permissions and structure for a successful integration. If you have not already done so, please follow the steps found in HaloPSA: Setting up HaloPSA's API Pre-Integration and return to this article when ready.
2. To begin the integration process, click on the More menu icon in Moovila's left navigation.
    
3. The More menu opens. Select the Integrations option.
   The Integrations dialogue opens. Click on the HaloPSA tile to get started.
    
4. The HaloPSA Integrations dialogue opens. In the Tenant Domain field, enter the domain (e.g. mysubdomain.halopsa.com) associated with your Halo instance. In the Client ID and Client Secret fields, enter the values that were generated in the pre-integration setup steps (those can be reviewed here). Those values can be found in Halo within Integrations > HaloPSA API > Applications > Details. Once those values have been entered, click Next to continue.
   
    
5. Once you have been successfully authenticated, the next step is the Permission Check. This is where Moovila reviews the configuration details that you set up for the API agent in the Pre-Integration steps to ensure that the correct permissions have been granted to allow data to flow smoothly between the two systems. If there are permission changes that need to happen, a list will be provided and you will be prompted to make them at this time. To review those permissions, please visit Setting up HaloPSA's API Pre-Integration. When it is indicated that "All required permissions are appropriately set on the HaloPSA API Agent," click the Next button to continue.
   
    
6. The Project Ticket Type setup is next. Select the ticket type that should be used when sending a project from Moovila to Halo. Only ticket types with a Use of "Project" and Project Hierarchy of "Project" in HaloPSA will be found in this list. Click Next to proceed.
   
    
7. The Project Status is the next to be mapped. HaloPSA has a central, ordered listing of all statuses that are used across all ticket types. For the ticket types that represent "projects," please set up a default mapping of the project statuses in Moovila to the project statuses in HaloPSA. To do this, click on the Edit Default Mapping link in the upper right of the screen.
   
   
   The Default Mapping of Project Statuses dialogue opens. Project Status Mapping is where each project status in HaloPSA is associated with a project status in Moovila. First indicate what a new status should default to in the other system. For example, a new status may be added to Halo, and it will be reflected as in the "Planning" status in Moovila. Move line by line, selecting the status that corresponds to the status in each system, or choose to leave the "Defer to Default" status setting. When all statuses have been mapped, click the Save button to return to the Project Status dialogue.
   
   In the Project Status dialogue continue through the listing of project tickets, choosing either to use the default mapping (which you've just established) by clicking the Use Default checkbox or click to Add Ticket Type Specific Mapping if needed. Click Next to proceed.
   
    
8. The Task Ticket Type dialogue opens. These will be used to identify which tickets represent project tasks in HaloPSA and will be available for import and sync into Moovila. Select the ticket type that should be set as the default when sending a new project task from Moovila to Halo. Only ticket types with a Use of "Project" and Project Hierarchy of "Project Task" in Halo will be found in this list. Click Next to proceed.
   
    
9. HaloPSA has a central, ordered listing of all statuses that are used across all ticket types. First we will set up a default mapping of the project task statuses in Moovila to the project task statuses in Halo. Click the Edit Default Mapping link in the upper right of the screen.
   
   
   The Default Mapping of Project Task Statuses dialogue opens. Project Task Status Mapping is where each task status in HaloPSA is associated with a task status in Moovila. First indicate what a new status should default to in the other system. For example, a new status may be added to Moovila, and it will be reflected as in the "New" status in Halo. Move line by line, selecting the status that corresponds to the status in each system, or choose to leave the "Defer to Default" status setting. Once all project task statuses have been mapped, click the Save button to proceed and return to the Project Task Status dialogue. 
   
   
   In the Project Task Status dialogue continue through the listing of project tickets, choosing either to use the default mapping (which you've just established) by clicking the Use Default checkbox or click the associated link to Add Ticket Type Specific Mapping if needed. Click Next to proceed.
   
    
10. The Action Outcomes dialogue opens, displaying the following two sections
    1. Default Halo Action Outcomes for Notes: When sending a new note from Moovila to HaloPSA, this setting applies an Action Outcome when the integration creates the object. Think about these settings in terms of visibility of these notes in Halo. In the first dropdown determine what Action Outcome is used when a note in Moovila with a visibility setting of "All Project Participants" is sent to Halo. In the second dropdown determine what Action Outcome is used when a note in Moovila with a visibility setting that is NOT "All Project Participants" is sent to Halo.
    2. Default Halo Appointment Type: When a new appointment is sent from Moovila to Halo, this determines which appointment type should be used by default when the object is created. Below this is an option to "Force Appointment Creation When Conflict Exists," which will allow appointments with an overlapping entries to be created. Overlap will be visible in Halo and can be adjusted accordingly. 
       
       
       Click Next to proceed.
        
11. The Teams dialogue opens. In this step you will determine which teams you would like to bring from HaloPSA into Moovila. Only teams configured for use within projects will be listed on this tab. All of the agents within the selected teams will be brought into Moovila either matching existing users via their email address, or as unconfirmed users if their email address could not be found on an existing Moovila user. This will allow these users to be assigned tasks within Moovila. Check the box for the team(s) you wish to sync and choose their leader from the Moovila Team Leader dropdown. Click on a star in the Default Team column to select the team that will be applied by default as projects are imported into Moovila (the team may always be changed).  Click Next to proceed.
    
12. The Enable dialogue opens. Click Enable and Close to proceed and complete the configuration.