Known functional gaps when using Business Process Manager work items with Case in-baskets

Cause

1. The All Assigned Work in-basket displays work items associated with Content Platform Engine workflow and does not display Business Process Manager work items.  
2. In-basket filtering is only applied to work items associated with Content Platform Engine workflows and are not applied to Business Process Manager work items. 
3. The in-basket is unable to display the activity properties for Business Process Manager work items.
4. The in-basket displays undefined columns 'Subject' for 'Step Name' and 'Received date' for 'Time Created' at run time when the columns are removed on the in-basket at design time.
5. The views for how work items are displayed is different with P8 work items and Business Process Manager work items.
   Case, in displaying P8 work items has the concept of roles and personal in-baskets, while process portal did not.
   In Process portal, when a user views their work, they can see
   a) The work assigned to a team, unclaimed
   b) The work assigned to a team, claimed
   c) There are customizable filters and searches on the view, which can determine if a user can see the claimed items or not, but by default, a user that belongs to the same team can also see the claimed work items.
   
   With the in-basket view in Case, it tries to model the existing in-basket view with the experience of process portal.
   The role or team in-basket will show the Business Process Manager work items that are associated directly with that team.
   For the same role or team, the personal in-basket will try to only display work items that have been claimed.
   
   For a different role or team, when the user accesses the personal in-basket, they will see unclaimed work items for the teams that the user belongs to.
   
   For example:
   Role or Team - RoleA
   Members - UserA, UserB
   
   Role or Team - RoleB
   Members - UserB, UserC
   
   Simple workflow (Step1 [RoleA] > Step2 [RoleB])
   
   At Step1, when UserB accesses the in-baskets, and looks at the RoleB role or team inbasket, they will not see any work items.
   When UserB switches to the personal in-basket, they see the work item for simple workflow at Step1.  This is because UserB belongs to RoleA team.
   This is how Process Portal would have shown the work items.
6. If a user defined property column on an in-basket is sortable, clicking on the header column to sort Business Process Manager process work items doesn't sort the rows when there are more work items than page size (default 50).  Sorting of system columns do work, but rows are not sorted for user defined property columns.  This is a limitation of what can be sorted with Business Process Manager or Business Automation Workflow processes.  The same behavior exists with Process Portal, where user defined property columns can't be selected to be displayed.