Gaurav, I checked in with one of the main developers of Case and asked if your challenge was easy to solve. This was his answer:
"If being one client-side, a bunch of case and then content JS/REST APIs would need to be called to:
- first get the docs associated with a case (in the case's folder)
- find the doc(s) you are interested in from that result
- use content APIs to get the properties on those docs
- use that information to display something useful to the user in the case/task UI
Probably best solved with a custom widget that would do all the above when wired onto a page."
------------------------------
DAVID Jenness
------------------------------