Hi all,
Since we currently only have one element with that protocol, the service template gives no element choice during apply and automatically adds the only one it can find (…to all services).
Known issue (while it’s technically not incorrect), workaround is creating a second element.
So I created a stopped copy of the only element.
Do you guys have a different workaround for this ?
Thanks
Hi Daniel,
Good question — let’s see if others in the community have alternative approaches, but you might be able to handle this by introducing a filtering mechanism in the service template.
Pretty much you want to use input data combined with a Name Mask to control where the element is applied:
- Add an input data entry to the service template. For this example, I'm going to call it Element Name. Make sure to select the option "Allow 'N/A' to indicate empty value".
-
In the Child Elements section, edit the configuration of the element and configure a Name Mask that references this input data.
- Save and Close the service template. It will show an error as the services need to specify the newly added input data.
- Right click on the service template in the surveyor and select "Export Configuration". This will create a CSV file that contains all the current services created with that template.
- Edit the CSV so you populate the element name of those services you want the element to be added to. Other elements should have as name "N/A" so it is not taken into account.
- Right click again the service template in the surveyor > Apply > Import configuration from CSV..., and select the file you edited on step 5.
After this is done, any new service will ask for the Input Data of Element Name and the previously created services will include the element only when the input data is specified.