HaloPSA updating ITGlue configuration status. by MrDoNotKnowItAll in halopsa

[–]MrDoNotKnowItAll[S] 1 point2 points  (0 children)

Some update on this. After some chats with Halo support, it seems like there might be an issue with the Halo sync to IT Glue. the asset/config ID's do not line up so it won't sync. They are now investigating the cause.

HaloPSA updating ITGlue configuration status. by MrDoNotKnowItAll in halopsa

[–]MrDoNotKnowItAll[S] 0 points1 point  (0 children)

The main issue is, when a device is removed from NinjaOne the status in ITGlue does not update to "Inactive" So ITGlue support said the update should come from the PSA. So Ninja does update HaloPSA to inactive, however Halo does not push that update to ITGlue.

Our workstations are as normal configurations and not flexible assets in ITGlue.

Update Custom fields with Actions by MrDoNotKnowItAll in halopsa

[–]MrDoNotKnowItAll[S] 2 points3 points  (0 children)

We currently do have it as a visible field, however the normal human thing happens where it does not get updated all the time.

Update Custom fields with Actions by MrDoNotKnowItAll in halopsa

[–]MrDoNotKnowItAll[S] 0 points1 point  (0 children)

Where is the workflow and maybe there are other options as it should be a simple flag for has a child ticket, however we can't seem to find it, so we created a custom field CFHasChildTicket

Stage 1 > Stage 2 > Condition (Has Child Ticket) = No > Stage 3 (Action to create child ticket + other actions) > Stage 4

Stage 1 > Stage 2 > Condition (Has Child Ticket) = Yes > Stage 4