As usual, everything is ConfiForms Form container, we have set custom t=
itle and custom label for main action button
Then we have 2 fields (ConfiForms Field Definition macros): name and me=
ssage. Name is of type "user" and Message is of type "textarea"
Then we have a ConfiForms Registration Control, which tells us how the =
form should be shown (we have selected it to be embedded to the page) and w=
e set custom messages and labels
Then we have 2 ConfiForms IFTTT macros, or handlers as we usually call =
it. The ordering is important! The first one sends notification and the sec=
ond one deletes the original ConfiForms record which was used ini=
tially to sent the notification
Below, you can see screenshots for Registration Control and screenshots =
for these 2 IFTTT handlers
Configuration for ConfiForms Registration Control
Configuration for ConfiForms IFTTT macro which sends notifications
Here we set a subject to be dynamic, and as "user" object is a "complex"=
object we can query some additional properties (See documentation for more=
details on properties of "complex" objects: Documentation)
Second IFTTT deletes the record (we set a dynamic filter, which will fil=
ter only one record)
The important bit (shown below, as it did not fit into the previous scre=
enshot) is the last parameter, called "Form name and pageId":
which set's the name of the form this filter (and action) should be appl=
ied on, as well as the location (pageId of the page where this form is conf=
igured)
In our case the form name is "f" and it is on the page with page Id =3D =
884778
The end result looks like this (notification and actually empty table):<=
/p>
This will not work for "Anonymous forms"! The reason is: a record stored=
does not have an owner and therefore could not be deleted by anyone than a=
form administrator