03-11-2021, 09:46 PM
(03-09-2021, 08:55 AM)maxcom Wrote: Hi Dan,Hey Max, If you look into the Custom Layouts, it can be a much better way to develop a custom form. You would even be able to just have your own checkbox widgets for multiselect. I mentioned in another post that there may be a need for more documentation as there is a ton of things that can be done via Custom Layouts. There is some documentation that covers a bunch of what it can do
thanks for your reply.
Actually I'm trying to customize the standard Edit Form that pops up when you add a new sobject of a particular sType. (Tactic 4.8)
I have a trigger that fires on insert which configures some sobject data just after its creation.
In this trigger, when I log what is inside the 'self.input' dictionary for the string data that should get the resulting multiselecion values, I only get the first value that was selected in the form.
I've also found something about the || string separator, but it doesn't seem to work on my side.
I'm relatively new to tactic widget customization, and I don't know if it is possible to customize/override the behavior of the submit button of the edit form to get around this issue...
Best,
Max
http://community.southpawtech.com/docs/d...ut-editor/
A few things have changed since this doc was created, For example, the behaviors are simpler in that you just assign to a class then choose the event. In the doc is shows having to declare this in the behavior tag. Also, a bunch of the Mako stuff is simpler. For example, you can generate a bunch of HTML in the python tab then your variable becomes available in the html via ${variable_name} syntax.
The doc does cover that the spt.get_input_values(el); function which will grab the data based on any element tags name attribute. You can also have this function grab from any input element by adding a name attribute and class="spt_input"