Distinguish not mapped and unmappable fields in Field mapping profile View screen

Purpose: To make clear on the field mapping profile "View details" screen which fields are not mapped because the user chose not to map them and which fields are not mapped because they are not mappable

As a staff person creating field mapping profiles
I want to be able to tell which fields in a field mapping profile's View screen have been left blank because I chose not to map them versus because I am not allowed to map them
So that I can quickly determine if I have missed any fields I should have mapped

Scenarios

1. Scenario 1
   • Given the field mapping profile "View details" section for Instance, Holdings, and Item record types
   • When a field is not mapped with any data, but can be mapped in the create/edit screen
   • Then display that field's lack of data with "-" in the view screen [this already works properly]
   • But when a field is not mapped with any data, and cannot be mapped in the create/edit screen (is greyed out in the create/edit screen)
   • Then display that field's lack of data with the prohibition character (circle with backslash in it, the opposite of the null sign). The Unicode code point for the prohibition sign is U+20E0, Combining Enclosing Circle Backslash ( ⃠ ). It is a combining character, which means that it appears on top of the character immediately before it. It also appears in the Webdings and Wingdings 2 fonts.
2. Scenario 2
   • Given the field mapping profile "View details" section for Instance, Holdings, and Item record types
   • When a multi-column list (MCL) field is not mapped with any data, but can be mapped in the create/edit screen
   • Then display that field's lack of data with "-" in an empty table the view screen [as is done in the Inventory app - see attached Inventory screenshot]. Currently it says "This list contains no items"
   • But when an MCL field is not mapped with any data, and cannot be mapped in the create/edit screen (is greyed out in the create/edit screen)
   • Then display that field's lack of data with the prohibition character (circle with backslash in it, the opposite of the null sign) in an empty table in the view screen. Currently it says "This list contains no items"
3. Scenario 3
   • Ensure automated testing coverage for this new code is 80% plus and confirm with screenshot

NOTES

• See attached screenshots for mockups
• Separate story (UIDATIMP-477) for creating a "value prohibited" accessible component