Skip to main content

StackJack 0.1.0.16348+df6472c

StackJack 0.1.0.16348+df6472c

This release adds Autotask tools for dispatching service calls and makes Microsoft-Decision-1.1 the default decision engine in the EU region. It also makes team invitations more accurate for people who sign in with Microsoft and fixes the Yeastar backup tools.

New features

  • Autotask service call dispatch: AI agents can now assign resources to service call tickets and service call tasks, remove those assignments, and list the resources on a service call ticket. Assigning a resource puts the service call on that technician's dispatch calendar, so service calls created through StackJack no longer have to be finished by hand in Autotask. Listing is available on the Free plan. Creating and removing assignments require Pro.

Improvements

  • Default decision engine in the EU region: If your organization is in the EU region and has not chosen a decision engine, decisions now run on Microsoft-Decision-1.1 by default. In the US region the default is still TypeSafe Jev. If you have chosen an engine, that choice still applies.
  • Consent applies only to the engine that needs it: Where your region requires consent for fast decisions, only TypeSafe Jev needs it. Microsoft-Decision-1.1 does not.
  • Automations without consent: Before, an automation in a consent region was refused entirely if your organization had not given consent. Now each step and smart filter is checked on its own. Steps that run on TypeSafe Jev are skipped, and steps that run on Microsoft-Decision-1.1 still run.
  • AI Governance consent follows your engine:
  • An EU-region organization using Microsoft-Decision-1.1 no longer needs the AI Governance opt-in.
  • Organizations using TypeSafe Jev, or with EU or UK staff outside the EU region, need it as before.
  • The consent wording now names Microsoft-Decision-1.1 alongside TypeSafe AI.
  • Clearer AI Governance reporting:
  • The exposure report now names the AI service that app details were actually sent to.
  • The governance templates' sub-processor list and AI judgment summary name the provider of your organization's decision engine.
  • Invitations for people who sign in with Microsoft: These invitees now get an invite that tells them to choose "Sign in with Microsoft". They no longer get a password-reset email or instructions to set a password first.
  • Add to team email: The email sent when you add someone to your team now describes the steps they will actually follow. Before, it included password-reset steps that did not apply.
  • Accepted invites no longer appear as pending: When someone joins your organization by any route, their outstanding invite is now marked accepted, so your pending invite count is accurate. Closing an invite this way never changes the member's tools or roles.
  • Autotask tool descriptions: The tools that create secondary resources and service call resources now correctly say they return the new assignment's ID. They also name the list tool that reads the full assignment.

Optimizations

  • The Team page now does less work on each load, so it loads faster for organizations with many invites.

Bug fixes

  • The Yeastar tools for downloading a backup and checking backup status failed on every call. Both now work with real backup file names.
  • An invitation sent to the address listed as your organization's billing contact was wrongly shown as "already a member". It now shows as pending.
  • If StackJack cannot determine how an invitee signs in, it no longer sends a password-setup email by default. It sends nothing and tells you, so you can resend shortly.
  • When roles could not be assigned during Send Invite, the message said "Invitation sent" even if no email went out. The message now says so when no email was sent.
  • Resend Setup Email for unlinked users: For someone who signs in with Microsoft but has no invite or membership in your organization, this action sent an email inviting them to join. It now sends nothing and suggests using Add to Team or sending an invite.
  • Members awaiting approval: A member awaiting approval could have their invite closed after signing in with an unverified email, which meant they could never be approved by their later verified sign-in. That invite is now kept until their verified sign-in.

UI & UX changes

  • Team page:
  • An invite that will approve a member who is awaiting approval is now labeled "Awaiting approval", with a note on how to approve them now. Before, the page told you to revoke it.
  • The invite delivery hint now matches how the person signs in. Microsoft sign-in invites no longer prompt you to resend a password email that is never sent.
  • Decision engine card:
  • Explains the difference between TypeSafe Jev and Microsoft-Decision-1.1 and where each is hosted.
  • States when consent is needed and warns if your engine needs consent you have not given.
  • Choosing an engine, or giving consent on Settings, updates the card and the Fast decisions consent section without a page reload.
  • Fast decisions consent control:
  • Stays available while consent is recorded, so you can always withdraw it.
  • Its text now describes exactly what the consent covers for your current engine.
  • Client organization opt-in: The confirmation now says which judgments the opt-in covers for your decision engine.