You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem or unsupported use case? Please describe.
Currently, contracts are displayed to organization members for signature even if no payment method has been entered by the learner.
This can lead to confusion for organizations and result in unnecessary costs related to LexPersona credits.
Describe the solution you'd like
Contracts shouldn't be displayed for signature to organizations until learners have entered a valid payment method.
Describe alternatives you've considered
One option considered was to display in the Learners view the status of those who have not yet entered a payment method. However, currently, these learners do not appear in that view (only enrolled ones are displayed), which could also create confusion for organization members.
Feature Request
Is your feature request related to a problem or unsupported use case? Please describe.
Currently, contracts are displayed to organization members for signature even if no payment method has been entered by the learner.
This can lead to confusion for organizations and result in unnecessary costs related to LexPersona credits.
Describe the solution you'd like
Contracts shouldn't be displayed for signature to organizations until learners have entered a valid payment method.
Describe alternatives you've considered
One option considered was to display in the Learners view the status of those who have not yet entered a payment method. However, currently, these learners do not appear in that view (only enrolled ones are displayed), which could also create confusion for organization members.
Another option was to display the order status in the the Contract view, but this could blur the purpose of this view and would still generate unnecessary costs related to contract signatures.
The text was updated successfully, but these errors were encountered: