1. Contract-Based Payment Availability
Added a new App Setting to control whether payments in the Shopping Cart and Payment Portal can only be made after the associated contract has been accepted.
What changed:
-
Introduced a new App Setting, WebAppRequireContractForPayment:
- When set to Yes, the payment option remains disabled until the associated contract status is Accepted.
-
Once the contract is accepted, the payment option is automatically enabled.
-
When set to No, the payment option remains available regardless of the contract status.
-
Existing payment functionality remains unchanged once payment is enabled.
Impact:
- Allows organizations to enforce contract acceptance before collecting payments.
- Prevents customers from submitting payments before contractual approval is complete.
-
Provides flexible configuration through an App Setting without affecting existing implementations by default.
With the appsetting set to Yes, before accepting the contract:
With the appsetting set to Yes, after accepting the contract:
