Hi! We are making a module which add Ignition Perspective components (react components). For this we need some common settings, this could be badge handling, style type, etc. So I have made a project property view in the designer: [image] But I haven’t found a good way to store the data and to g…

I'd create a small, Perspective-authenticated servlet that your client would call when loading. Client starts, loads your BrowserResource. Your BrowserResource queries your endpoint and is given the settings for the current project. Store the settings globally in the client, and use as needed in y…

That sounds smart. Like setting window.mymodule.style = "flat" and accessing that from the component? Would that work in the designer?

[image] torstein: Like setting window.mymodule.style = "flat" and accessing that from the component? Exactly. [image] torstein: Would that work in the designer? Yup, nothing special is needed in the designer. This is how I handle it in Embr: libraries/javascript/perspective-…

Ben also asked for the ability to provide session props in a module, which is something we should do, but no timeline on when: [image] [IGN-15726]Adding module-specific session properties Module Development Is there any supported way of adding to the built in S…

@paul-griffith for us we would like to have a project setting (which is the same for all sessions). I think I only need a guidance on how to store a setting from the "Project Properties" view in the designer (as shown above) and how to retrieve that setting in an Gateway endpoint.

Yeah - to me, the "natural" way to do that that end users would have a good time with (if they need to bind to it or otherwise read it easily) would be a read-only session property that your module is in charge of providing. Ben's workaround(s) are probably the best solution in the short term - he'…

[image] paul-griffith: workaround(s) 100%, the way I suggested is just a work around. At the moment the only thing easy about extending Perspective is adding components. Beyond that, it gets hacky pretty quickly. [image] paul-griffith: read-only session property I’d like to see the a…

I think I solved the project setting issue. But it feels very hacky String projectName = component.getSession().getProjectName(); Optional<RuntimeResourceCollection> resourceCollection = gatewayContext.getProjectManager().find(projectName); Optional<Resource> resource = reso…

[image] torstein: mapping between project name and collection name changes A resource collection and a project are synonymous; they can't ever get out of sync. 'Resource collection' is just our invented nomenclature because we needed something to describe the root of the hierarchy that conta…

Thank you for the guidance! :folded_hands: [image] paul-griffith: I would recommend moving away from ResourceUtil.decodeOrNull in new code. I'd recommend you adjust your editor/workspace to serialize using GSON/JSON and perform the inverse operation against the stored resource data. Better for …

[IGN-15726]Project settings in Perspective 8.3 for components

Module Development

paul-griffith April 24, 2026, 4:20pm 5

Ben also asked for the ability to provide session props in a module, which is something we should do, but no timeline on when: