Preferred way to build URL's in Alert Engine

I am trying to construct a URL to Alert History in Alert Engine. What is the preferred way to build URL’s in the Alert Engine code?

Best Answer

  • The Alert Engine doesn't build a lot of complex URLs; most are either static paths stored as LDAP properties or have no more than a few query arguments and just use placeholders for the argument values. If you have a lengthy and complex URL to build, such as one of the 1.5K-character links to Result History, use whatever means works well for you. For those, the engine does nothing; it sends a request to WebSite, which does the dirty work.

Answers

  • Is the CUB (Cobalt Url Builder) used, or should it be used to build Cobalt urls?
  • Alert Engine code is in the TFSWT server and is not part of any Cobalt Module. I did not find the Cobalt URL Builder in the project but am not sure if there are any specific reasons for not pulling in the infrastructure jars.