Product releases in this quarter
...
| Info |
|---|
ProntoPayments 2023 Q4 release notes are located in the ProntoPayments v2 section |
Web Integration Toolkit (WIT)
1.76 (1/11/2023)
URL: /packaging/installPackage.apexp?p0=04t5g0000011fAA
...
ASPaymentMethod CSS Styling Enhancement
If the Payment Method in the campaign is set to only one option (ie. Credit Card) for both recurring and once-off donations
The payment option buttons will disappear
The spacing will be changed or have a normal space gap
Additional Aura Component Design Attributes For PaymentDetails
The AsFlowFooterButton component is updated where:
If the user hits a validation, the PaymentDetailsValidation will be set to TRUE
If the component disabled the button (Give Now) as the user hits a validation, the HasValidation will be set to TRUE
Give Now Button Visibility on Screen Flow
The AsFlowFooterButton component is updated where:
If isHideGiveNowButton is TRUE,
Give Now button will be hidden
If isHideGiveNowButton is FALSE,
Give Now button will be display
...
Configuration Notes
Additional Aura Component Design Attributes For PaymentDetails.docx
The goal of this documentation is to guide the client in customising the WIT CheckOut Page. This involves configuring it to employ the standard Salesforce button instead of the Give Now button within the screen flow.
To enable the use of the standard Salesforce button, we have introduced specific attributes to the AsFlowFooterButton component:
PaymentDetailsValidation: This attribute is used for payment validation
HasValidation: It's employed for comprehensive validation
Hide Give Now Button: This attribute allows you to conceal the Give Now button.
To make the Give Now button disappear and utilize the standard Salesforce button, simply set the Hide Give Now Button attribute to "True."
...
To display the Give Now button, set the Hide Give Now Button attribute to "False."
...
To execute a payment using the standard Salesforce button while retaining the validation, the client has the option to select from these two alternatives:
Utilise HasValidation attribute to apply validation to the entire CheckOut Page.
Enable Manually assign variables in AsFlowFooterButton component
...
Create a new Boolean variable to pass the HasValidation value in AsFlowFooterButton component
...
Get Decision element to check if the validation occurs during filling up the donor or payment details before clicking the button
If the validation is True, it would go back to the form and the error message displayed
...
Using Set Component Visibility for displaying error message
...
Before:
...
After:
...
If the validation is False, the payment has successfully processed
...
Before:
...
After:
...
Use PaymentDetailsValidation only when ASPaymentMethod is being used entirely as the Payment Details validation.
...
When configuring PaymentDetailsValidation attribute, follow the same procedures as before:
...
Before:
...
After:
...
Invalid Donor Details were already included in the WIT CheckOut Page. Its purpose was to validate the Donor Details only.
...
Like PaymentDetailsValidation, when configuring Invalid Donor Details attribute, follow the same procedures as before.