# Workstation 8.3 changelogs - 2026

**URL:** <https://forum.inductiveautomation.com/t/workstation-8-3-changelogs-2026/116827>\
**Category:** Ignition Early Access\
**Created:** [August 19, 2026, 6:58am UTC](https://forum.inductiveautomation.com/t/workstation-8-3-changelogs-2026/116827 "2026-08-19T06:58:24Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![r.lebohec](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/r.lebohec/32/3704_2.png) [@r.lebohec](https://forum.inductiveautomation.com/u/r.lebohec)\
**Post date:** [August 19, 2026, 6:58am UTC](https://forum.inductiveautomation.com/t/workstation-8-3-changelogs-2026/116827/1 "2026-08-19T06:58:24Z")

</div>

I no longer see any workstation updates coming through, such as the Chromium kernel or else. Are these updates automatically included with the “Upgraded the Java Runtime Environment (JRE)” updates in Java - Azul section , or have there simply been no workstation updates for quite some time?

---

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [August 19, 2026, 4:11pm UTC](https://forum.inductiveautomation.com/t/workstation-8-3-changelogs-2026/116827/2 "2026-08-19T16:11:29Z")

</div>

Workstation's JxBrowser version is upgraded at the same time as the rest of the platform; it's JxBrowser 8.16.0 as of Ignition 8.3.4. Other dependencies are also periodically updated as needed. There hasn't been much feature work on Workstation in 8.3, but there's already some changes in the upcoming 2027 release.

---

<div class="post-metadata">

**Author:** ![r.lebohec](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/r.lebohec/32/3704_2.png) [@r.lebohec](https://forum.inductiveautomation.com/u/r.lebohec)\
**Post date:** [August 20, 2026, 6:17am UTC](https://forum.inductiveautomation.com/t/workstation-8-3-changelogs-2026/116827/3 "2026-08-20T06:17:15Z")

</div>

Thanks.

We don’t use it very often, but this is very useful for positioning perspective pages during a session on a multi-monitor workstation.

Maybe it will solve the issue of sound: **“NotAllowedError: play() failed because the user didn’t interact with the document first.”**

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [August 20, 2026, 12:10pm UTC](https://forum.inductiveautomation.com/t/workstation-8-3-changelogs-2026/116827/4 "2026-08-20T12:10:27Z")

</div>

> [@r.lebohec](#):
>
> NotAllowedError

That is browser security. I'll be shocked if you can get around it server-side.

---

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [August 20, 2026, 4:23pm UTC](https://forum.inductiveautomation.com/t/workstation-8-3-changelogs-2026/116827/5 "2026-08-20T16:23:29Z")

</div>

Try adding `-Dignition.chromium.switch.autoplay-policy=no-user-gesture-required` to your workstation application arguments.

---

<div class="post-metadata">

**Author:** ![tgarrison](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/tgarrison/32/80965_2.png) [@tgarrison](https://forum.inductiveautomation.com/u/tgarrison)\
**Post date:** [August 20, 2026, 5:50pm UTC](https://forum.inductiveautomation.com/t/workstation-8-3-changelogs-2026/116827/6 "2026-08-20T17:50:21Z")

</div>

Had that issue with a sound I needed to be playable automatically. Can't have it enabled to start with. So I created a custom prop "Enable" and have a view startup script set that to True. Then when that goes true, the audio gets it's enable set by an expression. Seems to do the trick.