The pattern to use depends on the business case. You have two solutions: User registration pattern, or a public facing portal with an insert only form.
For something that needs to be represented in the system as a person I would take the solution of a user registration pattern. you can activate it in the application settings (within the client settings):
You can then setup additional forms and user permissions that will initialize that user upon registration.
For something that needs to be represented as an object I would take the solution of a public facing module. For example a suggestion box. You just add a module to your application and set its access level to 0. Then you do the same for your form. Then in your menu just create an entry of type insertion form after your menu item. Again, remember to set all these access levels as 0.
About This Community
|Asked: 3/15/19, 7:13 AM|
|Seen: 454 times|
|Last updated: 10/1/19, 9:34 AM|