HaloPSA: Action Sync Details + Considerations

Due to the unique data structure found in HaloPSA, there are several considerations to be aware of as the following functionality is used:
 

Action Sync:

• Halo has one attribute (actions) that encompasses both notes and/or time entries.
• Moovila splits these attributes into two distinct areas--notes and time entries.
• The following will occur when an action is created in HaloPSA to accommodate this:
  • If an action with a note is created and there is no associated time, it will create a note in Moovila.
  • If an action is created without any notes and only time, only a time entry will be created in Moovila.
  • If an action is created with a note and time in Halo, it will create a note AND a time entry in Moovila, individually.
    • The note description will be what is listed in the overall note, and it will also be posted to the time entry note.
    • The note and time entry note at this point are joined. Changing the time entry note description will change the project and/or task note description as well.
• If an action outcome is deleted in Halo, both the time entry and note will be deleted in Moovila.
• If both time entry AND note that are tied together in Moovila are deleted, the associated action in Halo will be deleted.
• If time only is removed from the action outcome in Halo, the time entry will not be DELETED, but rather zeroed out and maintained in Moovila.

Default Action Outcomes:

• When notes are added within Moovila, the action outcome that will be set in Halo is based on the visibility selection in Moovila, plus the configuration values set on the "Action Outcomes" tab in the Halo integration hub. This is only a default action outcome if the category is not explicitly set.
   

Note Visibility:

• When notes are added in Moovila, the action visibility in Halo will follow the default "Hide from User" setting configured for the action outcome. This action outcome is either selected manually in Moovila (note category) or applied by default when the action is transferred to Halo (based on Action Outcome configuration in the Halo configuration).
• When notes are added from Halo, the visibility set on the note in Moovila is based on the default setting associated with the Halo Outcomes. For example, if the note action outcome in Halo is set as a default to NOT "Hide from User," the visibility in Moovila will be set to All Participants. If the "Private Note" action outcome in Halo is set as a default to "Hide from User," the visibility in Moovila will be set to "Internal Team Members."

Appointment Sync:

• There are various appointment types in HaloPSA that Moovila does not support, therefore those records will not be bi-directionally synced, but will appear in Moovila Smart Schedule as read-only (this will happen in a future release of Moovila). Those include:
  • Appointments marked as “Task” Event Types​
  • Appointments marked as “Private”​
  • Appointments marked as “Is Recurring”​
  •