8.3 Beta Comments

As browsing and tinkering in the 8.3 beta, I've come up with a couple lists

(Additional Known Issues??) that I've discovered

  • Device Status currently doesn't exist
    • Is this intended to be at the top of the page for a summary and a fly-in pane on the right for details?
  • System performance trends not working?
  • Exporting Named Queries all show the same generic name in export list

Suggested Improvements/Features

  • Move scheduled backup settings to the backup/restore page (this seems like the natural place for this anyway)
    • If moved here, add the ability to show all existing scheduled backup GWBK files in the destination folder and allow doing a direct restore from the page to restore from the selected backup after confirmations/warnings - This would be especially helpful if working remotely over a slow connection and needing to restore the latest automatic backup for some reason without having to upload it across a slow network
  • Would it be possible to have a bottom "pane" or some other view to show the inheritance of projects visually in a tree form? (Would be extra nice if you could add projects under a parent from this view) Or even if the items were automatically sorted/ordered like this with insets from the parent to show inheritance more visually.
  • Add status for user sources to show enabled/disabled and maybe even count of users/roles if supported for the various sources
  • Multi-select for devices/databases should also allow bulk-disable/enable (Looks like this exists for modules already)
  • Make more actions visible for each line/entry for devices, databases, user sources, etc rather than everything buried under a menu. I understand less used or more destructive actions being under the menu, but edit, details, and enable/disable would be helpful to just be a single-click away. Especially since all require saving/confirmation to make the change. I think it would help with the overall UX. Especially since those 3 are going to be the most commonly used actions. For other things like user sources, manage users would also be helpful.
  • When duplicating any item, is it possible to automatically just fly out the edit pane after assigning a name since that's naturally what will happen probably 99% of the time (if not 100% of the time)
  • OPC-UA Client Diagnostics tag/node list needs to be wider and paginated for better performance with large tag counts - having 60k tags brings the browser to its knees
  • Would really like to see F2 rename images in the image management console
  • Launcher project/gateway organization - I would really like to see more organization/sorting capabilities in the launchers. While most end users won't have a need for it, integrators or technicians who deal with a lot of gateways could definitely benefit from it (I know I could export and import the list, but built-in sorting of some sort to move them around or organize them into folders sorted alphabetically would be amazing!) I could then make folders for each client for example.

Improvements I like

  • Liking the property filter for vision properties in place of the pre-selected filter for expert/basic/etc
  • I like the added backup configs for settings that apply to the backup server. I currently don't have a use case for this, but can see it being useful for specific scenarios.
  • Duplicating devices (and other configs) will definitely speed up adding similar devices, and hoping this works with the CirrusLink EFM drivers also.
  • Really liking the gateway and client scripts being in the tree view now instead of inside a popup window.
  • Like how things that were free text entry for like selecting the gateway scripting project, or gateway/designer roles are now selections to prevent making errors/typos
  • Alarm metrics are great! Is there one for the root "folder" of the tag provider also?
  • Multi-instance wizard looks way more powerful, but I haven't gotten a chance to test it out.
  • Like that in image management you can now copy the mounted path for using it in Perspective
  • The deep link and file association for launchers should help with distributing/sharing clients especially or even keeping my own bookmarks/shortcuts in my browser/file system to organize these better without even having to rely on the launcher as much. (Thinking of other engineers/programmers having to go to a customer site and just grabbing the .designer file and launching it to get access to the designer directly for example)
  • Memory tag persistence is something I hadn't heard mentioned before, but can also see this being useful for certain situations.

That's all for now as I haven't even begun to dig into scripting, etc. (Although I heard somewhere that all datasets are now iterable PyDatasets which is awesome and removes the need to convert between them all the time if I understand correctly.)

6 Likes

Note: I'm going to skip past some feedback because I'm not anywhere near the web UI team, though I think there's some very good ideas here that we may incorporate over time (i.e. 8.3.something).

This is within the designer?

This is a good idea.

A UI revamp for the launchers to improve their capability to support lots of configured setups is planned; because of the way the launchers work this isn't tied to any major Ignition version and should hopefully happen in that 8.3.x timeline.

Yes, that's correct - the system.dataset.toPyDataSet function is officially deprecated and any time you encounter a "bare" dataset it will act the same as a 'wrapped' PyDataset in prior Ignition versions (while still being fully compatible with the previous Dataset behavior).

Everyone internally appreciates this types of feedback. I am sure others will chime in where they see opportunity, but I wanted to address this specific question.

There will not be one for the root "folder" (a.k.a. Provider level metrics) in the near future. There are a couple of reasons for this:
1. Providers aren't inherently tags (unlike Tag Folders), so wiring this up would take quite a bit of effort that potentially adds performance risks
2. The new alarm metrics are leveraging functionality that has been largely proven in 8.x and works in a similar way to how the .jsonValues property works (although a little more exposed). We didn't want to risk changes that would affect more than just this area.
3. This is the start of ideas we have for improving alarms. There are other ideas in the works that might be more performant and carry less risk.

I have been corrected by the developer that this did get implemented with a syntax of:

[provider]/Alarm Metrics.<metric name>

While we had discussions about all of the above. I have been told that ultimately the solution implemented didn't carry as much risk as expected. That being said, I would be careful using this for providers with a substantial number of alarms. The performance hit with these metrics occurs when Alarm Transitions occur. Having a substantial number of alarms change state within the provider is something to pay attention to.

As far as making the option visible in the UI, which I am assuming would be the next logical question, it isn't a trivial effort.

2 Likes

Yeah, this is on an imported project, but when selecting a named query from the tree and trying to export, I get this.

2 Likes

I greatly appreciate the new alarm metrics functionality. It would have saved me a great deal of work if it had existed a year ago and I'm happy to see it will be there going forward as I encounter similar requirements on other projects.

5 Likes

I suspected that. As long as they are there for referencing, that is the main feature that I was hoping for that way from a dashboard standpoint, I can show both broken down areas/folders of alarm status/priorities, I can also have an overall status for the entire gateway/facility without making an expression tag to aggregate the sub-folders/areas myself.

Thanks - it's an easy fix; we'll get it taken care of.

The device status page information will be found in a "View Details" drawer for supported device types on the Connections > Devices > Connections page. This is currently going through the last round of QA.

There is an active ticket for this currently being worked on.

2 Likes