I'm working on a registration flow that I'm having difficulty with. I've got a self asserted profile to collect some data, and it's got validation profile that calls a REST endpoint. The REST endpoint passes back, among other things, a claim indicating if there's an error (boolean) and if there is, an error type (string). I've been back and forth with possible solutions, but I haven't been able to figure out how to do what amounts to a case statement - that is, if the error is "Not Found", load content from {notfoundurl} (via a technical profile's ContentDefinitionReferenceId) and display to the user; if the error is "Partial Match", load content from {partialmatchurl} and display to the user, and if everything seems to be in order, allow the user to enter a username and password to register. Is there an elegant solution to this?
0 Answers
Related