Date: Thu, 28 Mar 2024 13:54:52 -0400 (EDT) Message-ID: <839603160.28520.1711648492266@lyrasis1-roc-mp1> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_28519_1862981637.1711648492265" ------=_Part_28519_1862981637.1711648492265 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
Title (Goal) | Detect and re-assign stalled workflow tasks |
---|---|
Primary Actor | Administrator |
Scope | Workflow |
Level | |
Story (A paragraph or two describing what happen= s) | When a reviewer has taken a workflow task fro= m the pool and then leaves the institution, the workflow task can be left i= n a stalled state. Currently, this is typically detected only when the subm= itter complains that the item has not been approved yet. When the reviewer = is not a member of the Administrators group, this can be remedied using the= "log in as eperson" functionality; however this doesn't work for reviewers= who are admins. The configurable workflow's different task/role allocation= mechanism may or may not help with this issue. It's also currently very di= fficult to even detect items that are in such a state. It should be p= ossible (perhaps for certain roles only) to find items that are "stuck", fo= r a yet-to-be-determined definition of "stuck". For example, how would DSpa= ce know that a user is no longer at the institution. |