Hello Dojo,
Is it possible to create custom properties through automation without having an alarm beforehand?
If so, how can this be done?
Also, is it possible to expose those properties on the Alarm Console through automation?
Thank you!
Hi Ana,
There is currently no documented wrapper method available to programmatically create new properties. However, it is possible to achieve this using direct SLNet calls. If you’d like, we can go through the approach together offline.
Regarding the second part of your question:
As with property creation, there are no built‑in DMA methods for this. Using SLNet as an alternative could again be a workable solution.
A few important notes:
- The visibility of (custom) properties in the Alarm Console is a user‑based setting.
- This means that even if you apply changes through code, these will not result in a global configuration update for all users.
I validated this through the following manual test steps:
- Enabled visibility of the Ticket ID property in the Alarm Console.
- Created a ticket → property updated correctly. ✅
- Signed out of Cube and back in with the same admin user → property was still visible. ✅
- Created a new local user “Thijs”.
- Signed in as Thijs → property was not shown by default. ❌
Admin user view: (property visible)
Thijs user view: (property not visible)
If helpful, I can walk you through the SLNet approach or discuss alternative workflows.
Answer by José gives you the insights for the SLNET call on how to create the property via code. Note that SLNET calls are not always backwards compatible in the core software. Use them carefully!