Type: Bug Fix
Affects Version/s: None
KULRICE-10760 Analysis on reverting work for KULRICE-8153 and fixing another way KULRICE-6344 #dp doesn't work in progressiveRender KULRICE-9226 AttributeDefinition forceUpperCase Doesn't Work KULRICE-12203 Elements - Action - Validation Message needs to describe validation is “required field” KULRICE-2343 deleting attachments doesn't work (was: Notes and attachments deletion doesn't work on maintenance documents) KULRICE-7742 addLineLabel.render doesn't work in Uif-StackedCollectionSection KULRICE-7482 KRAD: Disclosure Collections not working in IE KULRICE-7855 NOTIFY_PENDING_ON_RETURN Policy (related to Recall from routing functionality) doesn't appear to be inherited KULRICE-10219 Metadata merging from Spring configuration does not appear to be working properly KULRICE-6460 Component refresh doesn't work after closing a lightbox
Description: Controls whether the nervous system will show the blanket approve button to a user who is authorized for blanket approval but is neither the initiator of the particular document nor the recipient of an active, pending, approve action request.
I interpret this to mean that if I'm a blanket approver for a particular document that I should be able to blanket approve that document whether I'm in the route or not.
So, set up the following - logged in as khuntley
Created role - Account Blanket Approver
Created perm - Blanket Approve Document - ACCT
Assigned user (mbaxter) and perm to role.
Created an Account as someone who can't blanket approve (day).
mbaxter user with new perm opened enroute Account - should see Blanket Approve - but doesn't.
Verified that the blanket approve button does show when mbaxter is initiating.
Are we interpreting the use of this parm correctly?