Page 1 of 1

Signature Controller Limitations

Posted: April 21st, 2022, 3:25 pm
by JefferyD
Signature controllers only have access to the background image URL and the new base 64 encoded image. This makes it very difficult to map the edited image to a specific object. Currently, capturing signatures in multiple locations requires each location to have a dedicated controller. Even this can't always be done though as capturing signatures for each element in a list has no way to specify an index and a controller for each element is not possible.

Could a configurable parameter be added to pass some kind of context key through the controller so that it could be mapped back to an object in the model?

Re: Signature Controller Limitations

Posted: April 22nd, 2022, 9:47 am
by SteveCap
Task #10372 has been created.

Re: Signature Controller Limitations

Posted: March 23rd, 2023, 1:38 pm
by JustinVanRegenmorter
This change was added in a previous revision.