StackJack 0.1.0.10873+1936364
StackJack 0.1.0.10873+1936364
You can now connect Employment Hero with your own API application. This release also fixes several SentinelOne, CIPP and PRTG tool problems, explains clearly which connectors can't be added to an automation's credential form, and speeds up several pages and tool calls.
New features
- Employment Hero: connect with your own API application. You now create an API application in your Employment Hero Developer Portal. That is usually in the menu under your profile name, though some accounts show it under Settings. Enter the application's Client ID and Client Secret on the Employment Hero card on the Connectors page, then click Connect. The card shows your region's Redirect URI with a Copy button, and the setup guide includes a checklist of the scopes to tick.
Improvements
- Employment Hero: changing only the Client Secret keeps you signed in. If you replace the secret for the same application and click Save, you no longer need to sign in again. A different Client ID still requires a new sign-in.
- Employment Hero: clearer sign-in error. When the sign-in fails after you approve access, the message now asks you to check that the Client Secret belongs to the Client ID on the card. Previously it only referred you to support.
- Automation credential form explains unsupported connectors. Employment Hero, QuickBooks Online, Moovila Perfect Project, Jira Service Management and Reddit Ads can't be added to an automation's own credentials. The form no longer offers them and explains why instead:
- These connectors are connected once for the whole organization on the Connectors page.
- An automation run by the account owner or a co-owner uses that connection.
- Before this change, trying to add one either failed with a server error or, for Reddit Ads, saved a credential that could never work. That bad credential could lead to auto-disable emails about it.
- PRTG: clearer guidance for the wrong server address. If the connector points at PRTG's classic web interface instead of the PRTG Application Server, the error now says so and suggests the Application Server address (port 1616 by default). This error no longer offers a support ticket draft as if it were a credential problem.
Optimizations
- Dashboard: Monthly usage by connector is calculated much more efficiently. Dashboard loads that were slow for busy organizations are now faster.
- Connectors page:
- The page reads its data once instead of twice on each load.
- Saving a connector now refreshes only that connector's data.
- Tool calls: Each tool call makes fewer and overlapping database lookups, which reduces response time.
- Automation memory: Browsing an automation's memories and memory versions takes fewer lookups.
Bug fixes
- SentinelOne:
s1_export_mitigation_reportfailed for every report. It now returns the CSV report exactly as SentinelOne provides it. Large reports are returned as a download link, the same way as other large results. - CIPP:
cipp_message_tracedetail mode always failed. - The tool now accepts a
messageTraceIdargument, which is the ID returned by a message trace search. - If detail mode is requested without an ID, the tool explains how to get one.
- An ID supplied through
additionalFieldsJsonis also accepted. - PRTG: A healthy API key could be automatically disabled after a few validation checks when the connector pointed at the classic web interface. That situation is now treated as an address problem and never counts against the credential.
- Connectors: After a credential was saved and validated successfully, a temporary problem refreshing the page could still show "Failed to save credentials". A successful save is now reported as successful.
- Employment Hero: Clicking Connect while the form was still loading could, in rare cases, act on a different connector's form after you had switched to it. Connect now does nothing if the form has changed since you clicked.
UI & UX changes
- Team page: Each member's usage count is now for the current calendar month (UTC) and is labeled "this month". Previously it was an all-time total.
- Automation credential picker: If every connector in a workspace is unavailable for automation credentials, the picker now shows the reason for each one. Previously it asked you to subscribe to a connector first.
Known issues
- An automation may have a credential added through the automation form for Employment Hero, QuickBooks Online, Moovila Perfect Project, Jira Service Management or Reddit Ads before this release. While that credential is active, the automation's calls to that connector fail. Revoke the older credential so the automation uses the organization's shared connection from the Connectors page.
Fixed customer-reported issues
- The Employment Hero connector could not be connected because no application was configured for it (
01M4EY6P66AAW9N3TXVX0ZPBJ8). You now connect using your own Employment Hero API application by entering its Client ID and Client Secret on the Connectors card.