StackJack 0.1.0.10685+fd87e31
StackJack 0.1.0.10685+fd87e31
This release adds many new HaloPSA tools, including tools to create, update and delete agent records. Halo tools that need a newer HaloPSA build now give clearer errors on older instances. ImmyBot ad-hoc metascripts now return their output.
New features
- HaloPSA agent records: New tools let your AI agents create, update and delete Halo agent records. You can now set an agent's cost price, cost-tracking periods, charge rate and travel rate. The update tool tells the agent to read the current record first. These are destructive admin tools available on the Pro plan.
- More HaloPSA coverage (all supported HaloPSA versions):
- Read your Halo instance settings and clear the instance cache.
- Check agent online status, agent check-ins and timeslots, and delete individual notifications.
- Read asset meter readings and asset-type fields.
- Review outgoing delivery attempts, incoming webhook attempts, notification logs and single sign-on attempts.
- Read HaloPSA release notes for your instance.
- More HaloPSA coverage (HaloPSA 2.250.53 or later):
- Crayon and Juniper Mist integration details.
- Distributor invoices, custom button actions and custom integration method values.
- Change history rows for orders, quotes and supplier orders.
- Pipeline stages, AI matching groups, asset diagram details, deprecated-field information and recurring invoice lines.
- To-do sequence reads and deletes, chat and chat message deletes, and Stripe payment method deletes.
- Clearing the QuickBooks cache, switching the ConnectWise RMM integration, and processing incoming event queries.
- Each of these tools says in its description that it needs HaloPSA 2.250.53.
Improvements
- New HaloPSA filter options:
- The Halo users and email address book tools can now include each user's Active Directory manager.
- The FAQ list tools can now filter by third-party ID.
- Older Halo versions ignore these options, so they are safe to use on any instance.
- Clearer behavior for tools that need a newer HaloPSA version:
- Tools that need a newer HaloPSA build are refused up front if your instance is older. This now includes six existing tools: the PII detection tools, periodic history, expense review and client prepay expiry.
- If StackJack can't determine your Halo version and one of these tools fails, the error says which HaloPSA version the tool needs and suggests checking your instance with the Halo system info tool.
- Clearer Halo tool descriptions: Some Halo list tools now say when the underlying route may not support paging. Tools whose behavior hasn't been verified against a live instance now say so.
Bug fixes
- HaloPSA version detection:
- StackJack now reads the correct version field from your Halo instance, so an unrelated version number is no longer mistaken for your HaloPSA build.
- The detected version is now tracked separately for each Halo installation. If you run more than one installation on the same host, one installation's version no longer blocks tools on another.
- Misleading Halo error advice: When StackJack knows your Halo version and a call returns "not found", the error no longer suggests a version problem. The issue is with the requested record, and the error now reflects that.
- ImmyBot ad-hoc metascripts: Running an ad-hoc metascript now returns the script's plain-text output. Previously the script ran on the target but its output was discarded and the tool reported a failure. The tool description also now names the required script body and how to target a computer or tenant.
Fixed customer-reported issues
- ImmyBot ad-hoc metascript runs lost the script's text output and reported an error even though the script had run (
01M59VA12VJXA1G2ZK85F07GG6). The tool now returns the script's output text as-is.