This is useful when you have a large organisation using webforms extensively and needing more than the current limit of database fields in the main database. By being able to use RT fields within webforms it allows us to gather additional form information in an RT database and not populate the main DB with unnecessary data as well as having access to more fields when needed.
How will this idea be used?
When needing to use webforms extensively within the organisation across multiple business units for different events, we are able to store form data outside the main database which gives us more flexibility around fields. Currently we have reached max capacity of database fields within the main DB which is restricting us from using webforms to its fullest potential. It also makes sense that event type data that we capture via webforms shouldn't necessarily be sitting within the parent database. This should be able to be stored within relational tables. |
|
What is your industry? | Banking |
What is the idea priority? | High |