Hi, I want to build a service template that is able to assign an input data field to a parameter. I can do it by saving the data into a property in the 'generated services' tab and retrieve the property value from the service's code internally.
The above method works but we are trying to avoid using properties for reliability reasons so I was wondering if this can be also achievable from the service template or code itself without using the properties section.
Could you please advise if this is possible? Thanks in advance.
Paul
Hi Paul,
This is indeed a tricky one, I'm wondering if it's not possible to store the data in a separate element or get the data from another way besides at the point of creating the services with the service template?
So i agree here that the property solution is not ideal, i would discuss this further with your technical contact person how to move forward depending on your context/solution but for now I can't really give you any pointers either on how to achieve this within a service template.
PS: make also sure you have the "make this property available for alarm filtering" unchecked if you do not need and only use this property as a kind of parameter reference.
If this option is checked, it will store the property for every alarm/service in the database, which can cause a significant amount of extra DB storage, delay getting the alarms,...
Some more info how to configure/check this: