Bug 42988: Default holds_get_captured to yes for new SIP accounts
The account editor preselects "No" for "Holds get captured" when creating a new SIP account, but the SIP checkin default is to capture holds. This patch makes the editor default the option to "Yes" so a new account behaves the same as one that never set the option. Test Plan: 1) Apply this patch 2) yarn js:build 3) Restart all the things! 4) Create a new account in the SIP2 administration module 5) Note "Holds get captured" defaults to "Yes"! Signed-off-by: David Nind <david@davidnind.com> Signed-off-by: Emily Lamancusa <emily.lamancusa@montgomerycountymd.gov> Signed-off-by: Lucas Gass <lucas@bywatersolutions.com>
This commit is contained in:
parent
5f4fc10df5
commit
e60880e1ff
|
|
@ -336,6 +336,7 @@ export default {
|
|||
toolTip: __(
|
||||
"If enabled, items are automatically assigned to holds at SIP check-in; The alerts messages will continue to show, however, to allow items to be put to one side and then captured by a subsequent staff check-in."
|
||||
),
|
||||
defaultValue: true,
|
||||
},
|
||||
{
|
||||
name: "inhouse_item_types",
|
||||
|
|
|
|||
Loading…
Reference in New Issue