Changes for page Form Builder

Last modified by Sachin Patil on 2024/08/30 07:28

From 13.1 to 14.1 From 18.1 to 19.1

From version 14.1

edited by rijo
on 2022/09/26 21:13

Change comment: Added "Progressive" to Dynamic Lookup

To version 18.1

edited by Admin
on 2023/04/04 17:44

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (2 modified, 0 added, 0 removed)
Objects (1 modified, 0 added, 0 removed)
- Confluence.Code.ConfluencePageClass[0]

Details

Page properties

Author

@@ -1,1 +1,1 @@
--XWiki.rijo
++XWiki.Admin

Content

@@ -38,19 +38,32 @@
  \\
--1. Required: Give your Form a title. You will have an option to use this title when designing the form in Phase D. If you want to use a different title when designing the form you may do so by using a custom “text section” content block when designing the form.[[image:attach:FB Title.png||height="250"]]
--1. Give your Form a description. You will have an option to use this title when designing the form in Phase D. If you want to use a different title when designing the form you may do so by using a custom “text” content block when designing the form.
--1. Required: Assign a source code to a Form. To add or change existing source codes, go to the source code manager in the inventory tab of the navigation bar at the top. If you do not have a source code for this form then use a generic source code.
--1. If choosing popup as the 'Form Type', for best viewing experiences, please ensure that the minimum width and height used are 350-400.
--1. OPTIONAL: If you want to direct users to a specific page after submitting the form, then place the url into the "Thank you page URL" field.
--1. Select a submission option ~*~*~*~*~*~*~*~*~*~**
--1. Show only relevant products ~*~*~*~*~*~*~*~**
--1. Enter the text/message to be displayed if an email already exists.
--1. Body markers that may be used in the text are as follows:
++**Required:** First, give your Form a title. You will have an option to use this title when designing the form in Phase D. If you want to use a different title when designing the form you may do so by using a custom “text section” content block when designing the form.[[image:attach:FB Title.png||height="250"]]
++
++Give your Form a description. You will have an option to use this title when designing the form in Phase D. If you want to use a different title when designing the form you may do so by using a custom “text” content block when designing the form.
++
++**Required: **Assign a source code to a Form. To add or change existing source codes, go to the source code manager in the inventory tab of the navigation bar at the top. If you do not have a source code for this form then use a generic source code.
++
++If choosing popup as the 'Form Type', for best viewing experiences, please ensure that the minimum width and height used are 350-400.
++
++OPTIONAL: If you want to direct users to a specific page after submitting the form, then place the url into the "Thank you page URL" field.
++
++Select a submission option. Submission Option is a feature that allows ONEcount to require a user to subscribe to a product or package in order to submit the form. There are three settings:
++
++[[image:attach:selection-required.png||height="216"]]
++
++The first option allows the user to submit the form without subscribing to a product, but a message is displayed telling the user that they did not subscribe to a product before hitting submit. The second option allows the user to submit the form without any warning. The third option is effective in cases where the forms are pre-populated, and users might be tempted to hit "Submit" without subscribing to anything. This option issues a warning and forces the user to return to the form and subscribe to a product.
++
++Show only relevant products ~*~*~*~*~*~*~*~**
++
++Enter the text/message to be displayed if an email already exists.
++
++Body markers that may be used in the text are as follows:
  %%TEXT%% – will link to Sign in page%%
  ~#~#TEXT - will be linked to Password Reset page~#~#
--1. STATUS: Activate the Form for user access or disable the form.
++STATUS: Activate the Form for user access or disable the form.
++
  \\
  \\
@@ -237,10 +237,34 @@
  (% style="margin-left: 80.0px;" %)
  b. Please [[click here>>attach:formbuilder-R-PaintBrush-Aug23.mp4]] to view a video showing how a button's background color was changed.
++(% style="margin-left: 80.0px;" %)
  \\
--TEMPLATES MENU
++(% style="margin-left: 80.0px;" %)
++\\
++=== Click-Thru Button ===
++
++Often users will want to create a pop-up or landing page that has a button that clicks through to another site or page. The specific use-case could be clicking to a partner site to download a digital edition, clicking to a non-ONEcount form, or clicking off-site to a thid-party application.
++
++To create a click-thru button, click in the cell or grid where you want the button to appear, and from the tool-bar on the right, select Form Options, and then Submit. ONEcount will place a button on your form.
++
++[[image:attach:submit-button-tool.png||thumbnail="true" height="250"]]
++
++\\
++
++Now click on the button, and click on the gear icon above the tool bar.
++
++[[image:attach:click-thru-button.png||height="250"]]
++
++Click on the Action Pull-down and select Clickthrough. In the box for Label, add whatever text you would like to appear on the button. In the URL box, put the full URL where you would like the user to be sent when they click on the button. Please note that this URL will open in a new window, leaving the pop-up on the screen. The user will need to close the pop-up.
++
++A future version of ONEcount will track these click-throughs as "completions" in both the form and segment analytics, giving you insights into how many people are clicking through to the URL.
++
++\\
++
++=== TEMPLATES MENU ===
++
  The Templates menu contains a set of four pre-designed set of templates you can choose from.  Clicking on the Templates option, (found on the right-hand panel) displays the template set.
  [[image:attach:TEMPLATES menu Aug22.png||thumbnail="true" height="250"]]
@@ -487,10 +487,16 @@
  One use for these boxes is to add Javascript code to your form that will change the questions and/or question responses based on a user’s response to a question on the form.
--**Code for altering responses based on select type demographics:**
++= ADVANCED FORM TECHNIQUES: =
++With Extra Scripts/Extra Styles, you can add features to your form or popup to enhance its look-and-feel as well as operations.  Following are examples of how this can be achieved.
++
  \\
++**Example 1: Code for altering responses based on select type demographics:**
++
++\\
++
  **Example:** If a form contains a question which ask whether the user is a doctor or a patient. If the user selects doctor the demographic fields which are related to doctor will appear (type of specialty, NPI #, medical degree achieved, etc.). Otherwise, demographic fields for a patient will appear on the form. This modifications helps to show user only those demographic fields which are related to their previous answers.
  \\
@@ -562,6 +562,59 @@
  * removeInitial is assigned only once at the beginning of the script.
  * All the code must be included in form extra script area.
++**Example 2: Code for removing an option from the form**
++
++\\
++
++**Example:** A form contains a collection of questions.  The client decides that a question/option needs to be done away with, but without disturbing the rest of the form. You want to have it removed or hidden.   You can make this field invisible without changing anything else about the form, using the Extra Script option.  Without re-designing the form, we are able to remove the unwanted option by using the sample code below.
++
++\\
++
++**Example Sample Code:**
++
++(% class="p1" %)
++var removeId = document.getElementsByClassName("labelId");
++
++(% class="p1" %)
++for(var i = 0; i < removeId.length; i++){
++
++(% class="p1" %)
++if(removeId[i].innerText(% class="apple-converted-space" %)  (%%)== "RemoveMePlaceHolder"){
++
++(% class="p1" %)
++removeId[i].parentNode.style.display="none";
++
++(% class="p1" %)
++}
++
++(% class="p1" %)
++}~/~/end of for loop
++
++\\
++
++**Steps:**
++
++* Initialize a variable to grab all the instances of the id from the form you want hidden.
++** var removeId = document.getElementsByClassName("labelId"); //(notice the semi-color)//
++** removeId: name of variable (//you can choose a name of your choice, but remember to be consistent with the use through the code//)
++** labelId: replace this with the id of the field you want checked/removed
++** getElementsByClassName: property of javascript that allows you to get elements by the class name property
++* Traverse through the array of the gathered instances (of removeId), and check for the corresponding text by comparing the innerText property to  "RemoveMePlaceHolder"
++** removeId[i].innerText(% class="apple-converted-space" %)  (%%)== "RemoveMePlaceHolder" (//check for matches//)
++** RemoveMePlaceHolder: replace this with the text you want hidden
++* If a match is found, then grab its parentNode
++** removeId[i].parentNode
++** [i] is the index of the array where the match was found, during traversal
++* Change the style of the parentNode to display it as none.  This keeps the field hidden in your forms.
++** removeId[i].parentNode.style.display="none"; (//notice the semi-color//)
++
++\\
++
++**Note:**
++
++* All the code must be included in the form Extra Script field.
++* The code is to be inserted in the forms in which the value need not been shown or hidden
++
  = DYNAMIC/PROGRESSIVE LOOK-UP: =
  This is a feature provided by ONECount.

Confluence.Code.ConfluencePageClass[0]

id

@@ -1,1 +1,1 @@
--77496549
++77496880

url

@@ -1,1 +1,1 @@
--https://info.onecount.net//wiki/spaces/OD/pages/77496549/Copy of New Form Builder
++https://info.onecount.net//wiki/spaces/OD/pages/77496880/Copy of New Form Builder