replied on February 15, 2023
Couple ideas:
I have one form process that after the initial form is submitted, it runs a workflow that checks a database of existing forms, and if the record is found, it updates a form field with some warning text. Then the form process assigns it back to the initiator as a new task. The form field with the warning text is set in Field Rules to only be shown when there is text in the field. And that particular task only has an outflow to an end event. So it acts as a confirmation of rejection, but prevents the form from processing.
I have another process. On this one I set-up a simple View on the LFForms database to show some details of instances of this process. On the form, it does a lookup of the view for any matching account numbers. So it fills in some fields showing prior submissions for that account. Field rules are set to show some messages about prior submissions when the lookup returned anything. In this case, I do let them submit again, as sometimes it is needed, but the warning is good about letting them know something is already in progress and they need to verify that before starting the new one.
Both of these have served me rather well.