Seeking an solution for report context updation using UI

Yes this can be achieved using contextUsers parameter in queryProcessAnalytics. Please check the below link.
forum.appian.com/.../System_Functions.html

Hi sidhant, contextUsers field is an usersArray how can we update report context(i.e,process Models) of report by that?

can you please explain in more what you actually meant!

are you using the portal report in the actual portal interface, or are you using the a!queryProcessAnalytics() function to display data in a tempo report?

Apologies for the typo. What I intended to write is that you can use contextProcessModels parameter in queryProcessAnalytics. Whichever process models you specify in the contextProcessModels parameter those are provided to the report as its context and you get the output accordingly. Similarly you can use the other parameters like contextGroups, contextProcessIds and contextUsers to specify the report context for that instance of querying.

@conorc - That's a god question. My solution will be useful only if spandanat is using a!queryProcessAnalytics() function to display data in a tempo report.

@concorc,@sidhanth- hey I am talking about updating portal report context (instead doing it from designer I want an other way)... ignore if your talking about same..
@sidhantb, we cannot use the process models which are not defined in portal report context but defined in a!queryProcessAnalytics contextProcessModels parameter! that doesn't give expected results...

and I want a way to update the context of portal report itself ...

There is no way to update the context on the portal report in a supported way. Portal reports are stored as .arf file in the Document Management System. If you can regenerate this file (update with a newer version ) with the context process models correctly set, then it would work. Having said that, this is a hack. If you make a mistake, then the entire report will fail.

@sathya, slightly unrelated question - We know that the /designer interface will be deprecated/removed in a future major release of Appian. So, will the ability to create portal reports be also deprecated/removed?

You have the option to create portal reports from /design interface as of today. Why should the deprecation of /designer cause any issues?

Ok, got it.
I was aware that we can create portal reports from /design. But, I thought that since portal itself will be deprecated/removed incrementally as newer versions of Appian come in - the ability to create portal reports may also go, since deprecation/removal of portal for me meant that we would not be able to access portal interface at all.
Portal reports provide a good mechanism to pull the in-memory data from process instances/process models/tasks and many times we depend on those.
Hence I was curious to know about this.
Thanks for clarifying.