V3: What controls when the Edit option is available on the Data Browsing Toolbar?
Summary
In version 3 of Convergence for MDM, some customers would try to edit a fuzzy matched golden record and see the Edit button was available. Later then they moved to a different fuzzy matched golden record or they created a new workflow, the edit button was no longer available. What's the difference?
Problem
Why is a particular role not presented with the quick edit option when viewing golden data? It has read/write permissions on that entity.
Explanation
Even though a role is granted read/write and all checkboxes ticked on a particular entity, users in that role are not presented with the edit option (pencil icon) on the data browsing toolbar. Other entities with the same privilege grants in the same BOV have the edit option. Which other places could dictate why this is not available? I've checked everywhere I could find in the BOV properties, as well as the table and form views that are used in the BOV.
The specific example is an Item based BO which starts with the Item entity and transitions to other related (child) entites such as ItemTranslation (e.g. Item name in many languages) and ItemPriceGroup (e.g. many assignments to a price group based on effective date). This BO is referenced in an Item BOV inside of an application called Menu Management. The app requires a role called MenuUser which has the same privilege on all entities, but can only use the edit quick action option on the child entities. It should be noted that the Item entity does reference a parent entity (Concept in this case) and the MenuUser only has read privilege on that entity.
Solution
Ensure that the role also has read/write permissions on all other entities that are included in the business object view. If that is not appropriate, create a new business object view that does not contain the entities that the role should not be able to edit.
Related articles