<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0">
<channel>
<title>Efficy Overflow Q&amp;A - Recent questions tagged forms</title>
<link>https://overflow.efficy.io/?qa=tag/forms</link>
<description>Powered by Question2Answer</description>
<item>
<title>Loading form depending on manager attached into an opportunity.</title>
<link>https://overflow.efficy.io/?qa=6253/loading-form-depending-manager-attached-into-opportunity</link>
<description>&lt;p&gt;I need to migrate a macro from 11.0 version to 12.0.&lt;br&gt;
Previously the key of the form was loaded by a loadServerJs + RunScript &lt;code&gt;ConsultSectionsForm.Oppo {[&amp;lt;%LoadServerJs(&quot;functiontags/userrole&quot;)%&amp;gt;&amp;lt;%RunScript(&quot;getConsultFormOppo&quot;)%&amp;gt;]}&lt;/code&gt; &lt;br&gt;
The script still working because if it call into an other macro the number is well call back with number.&lt;br&gt;
The problem is that the same call into a 12.0 version return an Efficy error.&lt;br&gt;
&lt;strong&gt;&lt;em&gt;TTagGetFormSections - Incorrect Value &quot;&amp;lt;%LoadServerJs(&quot;functiontags/userrole&quot;)%&amp;gt;&amp;lt;%RunScript(&quot;getConsultFormOppo&quot;)%&amp;gt;&quot; for Argument &quot;FORM&quot;&lt;/em&gt;&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;&lt;em&gt;Call GetFormSections(form=&amp;lt;%LoadServerJs(&quot;functiontags/userrole&quot;)%&amp;gt;&amp;lt;%RunScript(&quot;getConsultFormOppo&quot;)%&amp;gt;, consulthandle=10, fielddefs=FormFieldsConsult, start=0, end=0, noformbounds=T, nosectiontitle=T, class=main small-12 medium-5 columns)&lt;/em&gt;&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;does any one of you already migrated the kind of custom ? &lt;/p&gt;
</description>
<category>Errors</category>
<guid isPermaLink="true">https://overflow.efficy.io/?qa=6253/loading-form-depending-manager-attached-into-opportunity</guid>
<pubDate>Mon, 16 Aug 2021 15:47:00 +0000</pubDate>
</item>
<item>
<title>What is the best way to implement a dynamic form in consult mode depending on a status ?</title>
<link>https://overflow.efficy.io/?qa=6244/best-implement-dynamic-form-consult-mode-depending-status</link>
<description>&lt;p&gt;What is the best way to implement a dynamic form in consult mode depending on a status ? &lt;br&gt;
When you are into a project in some cases you have multiple steps or status in your production.&lt;/p&gt;

&lt;p&gt;One of the most simple way will be to create a big virtual field where all fields will be formatted depending on status or something evolving during the project life.&lt;br&gt;
But we lost the advantage to modify easily fields form the designer form page but it can be accepted by the customer.&lt;/p&gt;

&lt;p&gt;With the introduction of live edit mode into consult forms this alternative way is compromise because we lost this functionality except if you simulate it for each field into you FormFieldConsutlCustom file.&lt;/p&gt;

&lt;p&gt;Do you recommend any best way to create a dynamic form still compatible with new live edition ? &lt;/p&gt;

&lt;p&gt;Thank's &lt;br&gt;
Laurent Tuffraud&lt;/p&gt;
</description>
<category>Efficy design guidelines</category>
<guid isPermaLink="true">https://overflow.efficy.io/?qa=6244/best-implement-dynamic-form-consult-mode-depending-status</guid>
<pubDate>Mon, 02 Aug 2021 10:08:49 +0000</pubDate>
</item>
<item>
<title>WARNING : take care of comments in your Macros</title>
<link>https://overflow.efficy.io/?qa=3569/warning-take-care-of-comments-in-your-macros</link>
<description>&lt;p&gt;Hi,&lt;/p&gt;

&lt;p&gt;I don't know if it's a known problem so I open this &quot;question&quot; to report it&lt;/p&gt;

&lt;p&gt;'//' comments cause some issues in macros&lt;/p&gt;

&lt;p&gt;Exemples with new relation forms :&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Works great&lt;/strong&gt;&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;/* Docu Relations */
RelationSectionsForm.Docu.Comp, RelationSectionsForm.Comp.Docu {[11]}
RelationSectionsForm.Prof.Docu, RelationSectionsForm.Docu.Prof {[3]}


/* Prof Relations */
RelationSectionsForm.Prof.Oppo, RelationSectionsForm.Oppo.Prof {[6]}
RelationSectionsForm.Prof.Objv, RelationSectionsForm.Objv.Prof {[7]}
&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;&lt;strong&gt;Issues&lt;/strong&gt;&lt;br&gt;
Here the forms DOCU&lt;em&gt;COMP and OBJV&lt;/em&gt;PROF will open properly from consult grid, but not with the &quot;Modify relation&quot; button on the Edit view&lt;/p&gt;

&lt;pre&gt;&lt;code&gt;// Docu Relations
RelationSectionsForm.Docu.Comp, RelationSectionsForm.Comp.Docu {[11]}
RelationSectionsForm.Prof.Docu, RelationSectionsForm.Docu.Prof {[3]}


// Prof Relations
RelationSectionsForm.Prof.Oppo, RelationSectionsForm.Oppo.Prof {[6]}
RelationSectionsForm.Prof.Objv, RelationSectionsForm.Objv.Prof {[7]}
&lt;/code&gt;&lt;/pre&gt;

&lt;p&gt;&lt;img src=&quot;https://overflow.efficy.com/?qa=blob&amp;amp;qa_blobid=10229320754276512420&quot; alt=&quot;enter image description here&quot;&gt;&lt;/p&gt;
</description>
<category>Other</category>
<guid isPermaLink="true">https://overflow.efficy.io/?qa=3569/warning-take-care-of-comments-in-your-macros</guid>
<pubDate>Tue, 25 Sep 2018 11:37:05 +0000</pubDate>
</item>
<item>
<title>Consult layout - alignement fields without icon</title>
<link>https://overflow.efficy.io/?qa=1175/consult-layout-alignement-fields-without-icon</link>
<description>&lt;p&gt;When we have in the same section of a consult form fields with an icon and fields without, how can we get the field part on the same line ?&lt;/p&gt;

&lt;p&gt;For exemple :&lt;/p&gt;

&lt;p&gt;the phone field ( which has class i-Phone )&lt;br&gt;
and another field ( for exemple street ).&lt;/p&gt;

&lt;p&gt;When you put these 2 in the same section, the street field will start in the same horizontal place as the icon. But better would be that the fields itself are on the same horizontal place.&lt;/p&gt;

&lt;p&gt;Is there a &quot;fake&quot; class that just puts the empty space to achieve this ?&lt;/p&gt;
</description>
<category>Efficy/ Client side</category>
<guid isPermaLink="true">https://overflow.efficy.io/?qa=1175/consult-layout-alignement-fields-without-icon</guid>
<pubDate>Tue, 12 Jan 2016 14:57:11 +0000</pubDate>
</item>
</channel>
</rss>