{option.description}
+| Custom Request Name | +Custom Request Data | +Status | ++ Actions + | + + + {data.map((it, idx) => ( +
|---|---|---|---|
|
+
+
+ setToView(it)}>
+
+ |
+
+ {JSON.stringify(it.customerData.data, null, 2)}
+ |
+
+ |
+
+ {getActionButtons(it)}
+ |
+
+ The name of the requirement will only be visible to you on the dashboard + on the requirement list, as well as on the custom information request + list. The user won't see this name. Make sure to make it distinguishable + and short. +
++ On screen 1 you will request the user if he agrees on providing this + information, or if he wishes to terminate the transaction instead. +
++ If the user agrees, on screen 2 is where the user will enter the custom + information. +
++ A custom information request allows you to have an extra option to ask + specific information about your customers when adding a trigger that + isn't an option on the default requirements list. +
++ Note that adding a custom information request isn't the same as adding + triggers. You will still need to add a trigger with the new requirement + to get this information from your customers. +
+ +