Known functional gaps when using Business Automation Workflow process 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 Automation Workflow process work items.  
2. In-basket filtering is only applied to work items associated with Content Platform Engine workflows and are not applied to Business Automation Workflow process work items. 
3. The in-basket is unable to display the activity properties for Business Automation Workflow process work items.
4. When the columns are removed on the in-basket at design time, the in-basket displays undefined columns 'Subject' for 'Step Name' and 'Received date' for 'Time Created' at run time.
5. The view for how work items are displayed is different from P8 work items and Business Automation Workflow process work items. Case has the concept of roles and personal in-baskets when P8 work items are displayed, while Process Portal does not.
6. 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 whether a user can see the claimed items or not. By default, a user that belongs to the same team can also see the claimed work items.
   The in-basket view in Case, models the existing in-basket view with the experience of Process Portal.
   The Personal(Role) or team in-basket displays all the Business Automation Workflow process work items claimed by the user regardless of roles.
   For the same role or team, the Personal(Role) in-basket displays all tasks that are claimed.
   The behavior of the Personal(Role) and Personal(Common) in-baskets is the same as regards to displaying Business Automation Workflow process work items. The role or team in-basket shows the Business Automation Workflow process work items that are associated directly with that team.
   
   For a different role or team, when the user accesses the personal in-basket, they 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 (Step 1 [RoleA] > Step 2 [RoleB])
   
   To show how Process Portal displays work items.
   At Step 1, when UserB accesses the in-baskets, and looks at the RoleB role or team in-basket, they do not see any work items.
   When UserB switches to the personal in-basket, they see the work item for simple workflow at Step 1. This behavior is because UserB belongs to the RoleA team.
7. Click the header column to sort Business Automation Workflow process work items, if a user defined property column on an in-basket can be sorted. When there are more work items than page size (default 50), the rows are not sorted. You can sort system columns, but rows are not sorted for user defined property columns. This is a limitation of what can be sorted with Business Automation Workflow processes. The same behavior exists with Process Portal, where user defined property columns cannot be selected to be displayed.