@SLB, It looks like that is coming up with “none” as well… so, I am checking the servers to make sure the info I was given is correct… but, I think it will work… thank you, for the contribution!
That is always going to be a clunky workflow.
Your server owner is asking you to do something, you’re asking us how to do it, we’re asking for clarifications of things you don’t know, you’re having to go back and ask the server owners…there is too much lost in translation.
You really need to be able to look at their setup, directly, or you’re going to spend way too much time going back and forth on this.
But - we have a solution! The WebUI Query App is tailor-made for this. You can test things out in an interface like QnA, targeting their test server, and iterate over that to figure out what’s needed.
On your WebUI page, open Apps → Query
On the right side, open the ‘Devices Targeted’ button, filter & find one of the test servers.
Then you can build your relevance a step at a time, send the query, and see what the results look like.
Like, start off with pathnames of files of folders "/", that way you can figure out if the filename they’re giving you is even right.
Here I created a test of what you described:
root@ubusrv1:~# hostname
ubusrv1
root@ubusrv1:~# ls /local/info/ubusrv1/installed.version
/local/info/ubusrv1/installed.version
root@ubusrv1:~# cat /local/info/ubusrv1/installed.version
#some text
#Sun Mar 16 11:02:28 EDT 2025
installed.version=8.x.x.x.x
Now I can use Query to navigate through that, a piece at a time. After selecting my server ‘ubusrv1’ as the target, I step through running each of these queries; the answer informs my next query:
computer name
--> ubusrv1
pathnames of folders of folders "/"
--> "Device","Results"
--> "ubusrv1","/bin"
--> "ubusrv1","/boot"
--> "ubusrv1","/cdrom"
--> "ubusrv1","/dev"
--> "ubusrv1","/etc"
--> "ubusrv1","/home"
--> "ubusrv1","/lib"
--> "ubusrv1","/lib32"
--> "ubusrv1","/lib64"
--> "ubusrv1","/libx32"
--> "ubusrv1","/local"
--> "ubusrv1","/loki"
--> "ubusrv1","/lost+found"
--> "ubusrv1","/media"
--> "ubusrv1","/mnt"
--> "ubusrv1","/opt"
--> "ubusrv1","/proc"
--> "ubusrv1","/root"
--> "ubusrv1","/run"
--> "ubusrv1","/sbin"
--> "ubusrv1","/snap"
--> "ubusrv1","/srv"
--> "ubusrv1","/sys"
--> "ubusrv1","/tmp"
--> "ubusrv1","/usr"
--> "ubusrv1","/var"
#so, there *is* a folder '/local'
pathnames of folders of folders "/local"
--> /local/info
pathnames of folders of folders "/local/info"
--> /local/info/ubusrv1
# I expect the 'installed.version' file to be there, so let's check for it:
pathnames of files of folders "/local/info/ubusrv1"
--> /local/info/ubusrv1/installed.version
# great, the file is there. What is in it?
lines of files "/local/info/ubusrv1/installed.version"
--> Device Results
--> ubusrv1 #some text
--> ubusrv1 #Sun Mar 16 11:02:28 EDT 2025
--> ubusrv1 installed.version=8.x.x.x.x
# Now that we know we can read the file, let's go ahead and craft the path dynamically - we know the file pathname contains the computername so let's build it that way
lines of files ("/local/info/" & computer name & "/installed.version")
--> exact same result, the file lines are still there
#Now retrieve just the part after 'installed.version=' from the lines of the file
following texts of firsts "installed.version=" of lines of files ("/local/info/" & computer name & "/installed.version")
--> 8.x.x.x.x
So, that’s what you need in your Property relevance: following texts of firsts "installed.version=" of lines of files ("/local/info/" & computer name & "/installed.version")
You need to replace the ‘/local/info’ path with whatever the real path is in your environment.
This relevance works, I can see it live in the Query app…if it doesn’t work for you, then something’s not correct in the way you’ve described the file content, or the path to us. But, now that you see the steps I went through to find that path and content in Query, at least you should be able to reproduce that and figure out what of our assumptions was incorrect.
Hope this helps!
2 Likes
Now using @JasonWalker relevance, you can drop into a property.
Make the changes to the path as Jason stated and then name the property to whatever you want it to be.
setting "MyLittleProperty"="{following texts of firsts "installed.version=" of lines of files ("/local/info/" & computer name & "/installed.version")}" on "{parameter "action issue date" of action}" for client
1 Like
We don’t always get to chose how things go, but thank you, @JasonWalker! That’s a lot of good info… I will validate and let you know…
Thanks, @D.Dean, I will def try that as well…