3 of 3 people found this helpful
it's probably a nsh job, so just grep for the property name in the storage/scripts directory on your file server.
Thank you B.R.
Other than manually, is BLCLI the only way to update a server property? Or can they be updated using another tool?
1 of 1 people found this helpful
I would say that there are 3 ways to update a property, but 2 of the ways are really using BLCLI.
One would be the client console - you've labeled this as "manual'. Anyone with the proper authorization (Server.ModifyProperties) can do this, although of course it wouldn't be recommended for lots of updates.
The second way would be scripted via BLCLI. We do this a lot with scheduled jobs! It also requires the same Server authorization.
The third way would be through Web services, but behind the scenes this is really BLCLI as well.
One addition to Bill's suggestion. If you import objects from another environment, you'll also need to grep for the property name in multiple levels of directories under storage/imported.
and that's assuming this is updated by a job. it could be updated by a script run from someone's workstation... you can at least narrow down who by looking at the audit trail and who exercised the ModifyProperties as scott noted.