Ignition 8.3.0 Beta Is Now Available!

Ignition 8.3 Early Access
1

Ignition 8.3.0 Beta is now available for download! It includes features like new Perspective drawing tools, a reimagined Gateway, the Event Streams Module, the Historian Module Suite, an offline mode for Perspective, Secrets Management, and a lot more. You can access it on our downloads page, and can reference the User Guide for What’s New for an overview of the new features.

Here are some quick guidelines to help you navigate the beta testing and feedback process:

Use the Beta in a Back-Up of a Real-World Project

The Ignition 8.3.0 Beta release should be used in development and testing environments only, it is not advised to use the beta in production environments.

Review Known Issues Before Providing Feedback

You can view known issues and out-of-scope features in the Prerelease Known Issues section of the 8.3 User Guide

Please review this prior to providing your beta feedback to check whether an issue you want to bring up is already being addressed.

Don’t Contact Support About the Beta, Use This Forum Category Instead

If you have any questions or concerns about the beta, you can use this forum Category to reach out to our team. This will keep primary Support channels open to assist you with active issues on released versions of Ignition. If you do contact Support you will be directed to this forum topic.

Let Us Know What’s Working Well And What’s Not

We’d greatly appreciate your feedback, both on what you’re loving in the beta, and any problems or frustrations you may encounter.

Happy exploring!

Resources:
8.3 Early Access Deployables
8.3 Early Access SDK Dependencies
Upgrade Guide

27 Likes
4

Glad to know about Ignition 8.3 beta. i have a question, will it have any relaxation on 10 million data points /35 days storage limits with ignition edge ?

5

I'm an integrator, and I highly doubt they'll relax that limit. There's a reason edge is cheaper. If you need more records, then you just have to upgrade to standard and the limitation is gone.

2 Likes
6

No, the Edge Historian contains the same storage restrictions as it did previously.

7

Not gonna lie, seeing this made me excited ^^

image
image979×141 5.79 KB

The only bad part is that now we are gonna have 7.9, 8.1 and 8.3 documentation :face_with_spiral_eyes:

5 Likes
8

It's great to have 8.3 out. I love how you restructured the gateway config page. It's going to take some getting used to but I think it's objectively better than before.

oops. I see where you want feedback :slight_smile:

3 Likes
9

Nah, drop v7.9. It is completely end-of-life now. Continuing to run it is a really bad idea.

8 Likes
10

I meant when looking for information on internet, it's going to apper from all the version hahah

2 Likes
11

2 posts were split to a new topic: Launch client jar invalid

12

8.3 has support for touch screen mode in perspective ? we have build project in perspective and unable to get OSK for login on touch HMI

13

Using windows on the touchscreen? Good luck.
Ignition has no effect on the OSK, they don't control it. OSK is an operating system function that is triggered by the browser when you focus on a text or numeric input item.
I would suggest dumping windows and going for a linux based system for all your HMI touchscreen perspective installations.

1 Like
14

Or best bet is to not use perspective for touchscreen HMIs. Vision is better suited to this.

2 Likes
15

True, yet very ironic.

2 Likes
16

Thanks for your feedback. Sorry Actually i mean to ask if 8.3 has inbuilt touch keyboard option like vision project we can enable it from project property.

17

Thanks.

18

No, and they likely never will. That function is provided by the OS.

19

Hi everyone,

I've been working with Ignition 8.3.0 beta and wanted to share some challenges I've encountered when integrating Git workflows with the new file system-based project structure.

As you know, Ignition 8.3 stores project resources as JSON files, which is a great step toward better source control integration. However, I've noticed that the Designer does not reliably reflect changes made directly to the file system, especially when switching Git branches.

Here are some specific issues:

  • The Designer appears to cache the project in memory, and changes made on disk (e.g., via Git checkout) are not picked up, even after closing and reopening the Designer.

  • Actions like "Update Project" (Ctrl+Shift+U), reopening the project, or even restarting the Designer do not reload the file system state.

  • The only reliable workaround seems to be restarting the Gateway, which is far from ideal in a development workflow.

  • There's no clear way to force the Designer to reload the project from disk, which makes multi-branch workflows very difficult to manage.

This behavior makes it hard to collaborate using Git, and undermines the benefits of having a file-based project structure. I understand this might be a limitation of the current beta/stable release, but I wanted to ask:

  • Is there a recommended way to force the Designer to reload from disk?

  • Are there plans to improve this behavior in future releases?

  • Has anyone found a reliable workaround for syncing Designer with file system changes?

Would love to hear your thoughts or any tips from others dealing with similar issues.

Thanks!

1 Like
20

After any external modifications to the gateway filesystem, you need to trigger a project scan, either via gateway API or by clicking that button in the Web UI.

1 Like
21

I haven’t even tried any source control with the 8.3 beta, but I’d hope there will be a button added to the designer that would allow forcing a rescan of project files without having to hit the gateway web page or API to do so. (Or maybe just make the “Update Project” menu item also force a rescan of the files on the gateway, as to not add another option that could be confusing.