Research studies often require users to sign multiple consent documents during onboarding. Currently SpeziOnboarding can only be used to store one signed consent document, as the store method defined by the OnboardingConstraint receives a PDFDocument which does not include any identifier that could be used to distinguish between different consent documents being used within the same onboarding flow and store them with separate file names.
Solution
An identifier should be passed either to the store method as an argument, or within the PDFDocument's attributes such that multiple documents signed within the same onboarding flow can be distinguished and stored appropriately.
Additional context
No response
Code of Conduct
[X] I agree to follow this project's Code of Conduct and Contributing Guidelines
Problem
Research studies often require users to sign multiple consent documents during onboarding. Currently SpeziOnboarding can only be used to store one signed consent document, as the
storemethod defined by the OnboardingConstraint receives aPDFDocumentwhich does not include any identifier that could be used to distinguish between different consent documents being used within the same onboarding flow and store them with separate file names.Solution
An identifier should be passed either to the
storemethod as an argument, or within thePDFDocument's attributes such that multiple documents signed within the same onboarding flow can be distinguished and stored appropriately.Additional context
No response
Code of Conduct