Hello,
when using the Custom Form Builder there seem to be some bugs that do not affect the functionality, but are very annoying. Perhaps some of you can confirm.
I already created a support case for this.
Views
Replies
Total Likes
I thought it was just me on #1! I am also having a problem with the selection not being saved and it defaulting to project instead when I create a new custom form.
Views
Replies
Total Likes
hi, on your third point, when Legacy custom forms were created, these were shared system wide by default. When I transitioned to the new custom form builder, I noted that these were not shared system wide by default, so I submitted a bug report for this, to have them change it back to achieve parity with Legacy.
We're accustomed to folks being able to immediately see and fill out any custom form we create and the majority of our forms need to be filled out by everyone in the instance. It's rare indeed that we have a custom form that we need to select an audience to fill out.
see also:
"By default, when you create a new custom form and someone attaches it to an object, any user assigned to the object can view and fill out the form. This includes users with Request licenses and external users." (this is what system wide access is supposed to allow)
Views
Replies
Total Likes
Views
Likes
Replies