We are using a portion of the TCP Web Client URL API to access work items from an external portal. This is TCP version 10.0.1.
We have presently only created a single shared work queue for the Inbox.
To access work items from the Inbox, we use WorkItemAction passing in Property1=<WorkItem>, Property2=<WorkQueue>, and the user access token. This works well for the most part.
Incidentally this shared Inbox work queue is called Indexing, and the proxy user is IndexingWQ. Not sure if this is a standard practice or if this makes sense. Any best practices for configuring a proxy user for a shared queue?
We would now like to similarly access work items from the Sent queue from the external portal. Other than creating a shared Sent work queue, are there other configuration tasks that need to be considered for items to show in this queue?
We presently use the WorkItemAction action method for our external Inbox functionality, and it works well. I am trying to understand under which use cases one would prefer to use OpenWorkItemAction, which appears to require no knowledge of the work queue, and the proxy user is an optional paramter.
Cheers, Jared