Help and Version Information

Overview

From the dashboard, open Help to reach Shift-Left API Platform Help. Use Back to Dashboard when you are done.

This screen is the single place to read application and component versions, environment, update check URLs, update status, and short guidance for auto-updates and support.

Application information

At the top of the page, Application information summarizes the client you are running:

Share these values with support when you open a ticket so issues can be matched to a known build.

Component versions

Below that, Component versions appears as separate cards. Typical components:

Engine and Agent builds can differ from Studio; always note all card values when comparing with release notes or support guidance.

Shift-Left Studio auto-update information

This block (highlighted in the UI) explains how Studio checks for updates:

• Update check URL — endpoint the app uses to discover the latest Studio release (for example a latest.txt file on cloud storage).
• Update status — whether a check has run and what it found (for example Not checked until you or the app performs a check).
• Current version — Studio version the updater is tracking.

How auto-update works (as shown on the page):

• The app can check for updates when it starts.
• If a newer version is available, you get a notification.
• Updates may download in the background.
• You can install immediately or later, depending on the prompt.

Use Check for updates now to run a manual check without waiting for the next automatic cycle.

Shift-Left Engine update information

A separate section covers Engine updates:

• Update check URL — engine release manifest (often distinct from the Studio URL).
• Update status — last engine check result.

How Shift-Left Engine updates work (as shown on the page):

• The engine may check automatically every 24 hours.
• You see a notification when an update is available.
• Local engines can often be updated with the installer directly.
• Remote engines usually need an update on the server (administrator action).

Check for updates now applies to the engine check where your deployment supports it.

Note: Exact URLs, check intervals, and who may trigger installs depend on your organization’s deployment and policies. If sections are missing or read-only, your build may centralize updates another way.

Support and troubleshooting

The bottom of the page usually includes:

• Technical support — contact your system administrator or internal support channel.
• Build information — keep version, build number, environment, and component lines handy for tickets.
• Auto-update issues — verify internet access and firewall rules if checks fail or downloads do not complete.

What to capture for support

• Application version, build number, build date, environment
• Shift-Left Engine version, build, server name
• Shift-Left Studio and Shift-Left Agent version and build
• Update status for Studio and Engine (and approximate time of last check)
• Timestamp when the problem occurred and any error message or ID shown in the product

Related articles

• Release notes
• Debug Logging
• Platform overview