Changes for page Form Builder

Last modified by Sachin Patil on 2024/08/30 07:28
From version 21.1
edited by Admin
on 2023/08/14 17:46
Change comment: There is no comment for this version
To version 14.1
edited by rijo
on 2022/09/26 22:13
Change comment: Added "Progressive" to Dynamic Lookup

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -Form Builder
1 +Copy of New Form Builder
Parent
... ... @@ -1,1 +1,0 @@
1 -ONEcount Customer Documentation
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Admin
1 +XWiki.rijo
Content
... ... @@ -1,14 +1,21 @@
1 1  
2 -The Form Builder tool allows you to create, edit, delete, and manage forms and pop-ups in a WYSIWYG way. Creating a form is as simple as defining basic form information, choosing which questions/fields will be included on the form, selecting which products and/or packages you want included in the form, and then designing the look and feel. You can also add a thank-you e-mail and message to your form.  When a user completes and submits a form, all of the demographic and transaction information from the form is saved in the ONEcount database, and any transactions that are captured by the form are immediately stored in the ONEcount database.
2 +The Forms tool allows you to create, edit, delete, and manage forms and questions. Creating a form is as simple as defining basic form information, choosing which questions/fields will be included on the form, selecting which products and/or packages, designing the look and feel, and dragging in questions and other elements onto the Form’s webpage using an easy to use WYSIWYG editor. When a user completes and submits a form, all of the demographic and transaction information from the form is saved in the ONEcount database.
3 3  
4 -What is unique about the ONEcount Form Builder is that questions, products and packages are not defined in the form, but elsewhere in the ONEcount system. This allows your organization to have some level of control over the information and data collected by the forms, while allowing any qualified user to build and edit forms. The presentation layer–the form–is separated from the data layer, meaning your web designer can't change field options or the business logic behind your products and packages.
4 +\\
5 5  
6 -**Questions are shared among ALL forms, so any changes made to question type, text, responses, alias, report header (See Question Builder - Create and Manage Questions for more detail) will change ALL forms, not just the form you are working on. Deleting a question will remove that question from ALL forms as well. **
6 +\\
7 7  
8 -**Changes made to form information, form layout, order of questions, and optional validations are form-specific and will NOT universally change forms; these changes will be applied only to the form you are working on.**
8 +When a user completes and submits a form, all of the information gathered from the form is entered into the ONEcount database. Plan forms carefully to ensure that you include questions and possible responses that will provide you with all the data you wish to collect from subscribers/purchasers.
9 9  
10 10  \\
11 11  
12 +\\
13 +
14 +**Questions are shared among ALL forms, so any changes made to question type, text, responses, alias, report header (See Question Builder - Create and Manage Questions for more detail) will change ALL forms, not just the form you are working on. Deleting a question will remove that question from ALL forms as well. **
15 +**Changes made to form information, form layout, order of questions, and optional validations will NOT universally change forms – these changes will be applied only to the form you are working on.**
16 +
17 +\\
18 +
12 12  Form-related tasks include:
13 13  
14 14  * creating database fields/questions available for placement in online forms; (See __[[Questions - Create and Manage Questions>>url:http://docs.onecount.net:8090/display/OD/Questions+-+Create+and+Manage+Questions||shape="rect"]]__ for more detail.)
... ... @@ -19,63 +19,46 @@
19 19  
20 20  \\
21 21  
22 -The first task listed above – creating questions is accomplished by clicking the Demographics tab under SETUP on the left-hand men. The next two tasks – creating new forms and managing existing forms – are carried out using the Form Builder tool under SETUP Creating source codes is handled under __[[Source Codes>>url:http://docs.onecount.net:8090/display/OD/Source+Codes+-+How+to+Create+and+Manage+Source+Codes||shape="rect"]]__ and creating branded forms is handled under __[[Brands>>url:http://docs.onecount.net:8090/display/OD/Brand+-+How+to+Create+and+Manage+Brands||shape="rect"]]__. All of these tools are found under SETUP
29 +The first task listed above – creating questions is accomplished using the Question Builder tool. The next two tasks – creating new forms and managing existing forms – are carried out using the Form Builder tool under INVENTORY. Creating source codes is handled under __[[Source Codes>>url:http://docs.onecount.net:8090/display/OD/Source+Codes+-+How+to+Create+and+Manage+Source+Codes||shape="rect"]]__ and creating branded forms is handled under __[[Brands>>url:http://docs.onecount.net:8090/display/OD/Brand+-+How+to+Create+and+Manage+Brands||shape="rect"]]__. All of these tools are found under INVENTORY.
23 23  
24 24  [[image:attach:Form-builder-nav.png||height="250"]]
25 25  
26 26  \\
27 27  
28 -**STEP 1: Defining the Form**
35 +__PHASE A: Defining the Form__
29 29  
30 -The first screen you'll see in the Form Builder is where you define the basics of the form. For this panel, the only required options are a Title and a Source Code. You will then get to pick between two different presentations: a "Form" presentation, which is a web-page, and a pop-up, which appears over the page that the user is looking at. The Form format is typically used for landing pages, gating, data collection and subscriptions since it can not be closed. A pop-up can be used for data collection and subscriptions, but since it can be closed by clicking the X in the upper right corner, it's not effective for gating.
37 +__[[image:attach:FormDefinitionAug22.png||height="250"]]__
31 31  
32 -__[[image:attach:FormDefinitionAug22.png||width="800"]]__
33 -
34 -//A Form landing page above.//
35 -
36 -__[[image:attach:form-builder-pop-up.png||width="800"]]__
37 -
38 -//A pop-up landing page above.//
39 -
40 40  \\
41 41  
42 -You may 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.
41 +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"]]
42 +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.
43 +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.
44 +1. If choosing popup as the 'Form Type', for best viewing experiences, please ensure that the minimum width and height used are 350-400.
45 +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.
46 +1. Select a submission option ~*~*~*~*~*~*~*~*~*~**
47 +1. Show only relevant products ~*~*~*~*~*~*~*~**
48 +1. Enter the text/message to be displayed if an email already exists.
49 +1. Body markers that may be used in the text are as follows:
50 +%%TEXT%% – will link to Sign in page%%
51 +~#~#TEXT - will be linked to Password Reset page~#~#
52 +1. STATUS: Activate the Form for user access or disable the form.
43 43  
44 -**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.
45 -
46 -If choosing popup as the 'Form Type', for best viewing experiences, please ensure that the minimum width and height used are 350-400. You have several options for a pop-up, including:
47 -
48 -* **Width and Height:** choose dimensions that work well for desktop and mobile
49 -* **Horizontal Position:** where it appears horizontally on the user's screen
50 -* **Vertical Position:** Where the pop-up appears vertically on the page. This is relative to the entire web page. Be careful if your site has long pages or uses infinite scroll, because the pop-up may render "below" the user's screen causing some confusion.
51 -* **Slide Positon:** This describes what part of the screen the pop-up will appear from (ie., enter stage-left)
52 -* **Pop-Up Delay:** This allows you to program a slight delay into the pop-up so that it doesn't appear immediately on the screen.
53 -
54 -If you want to direct users to a specific page after the form is submitted, you can place the url into the "Thank you page URL" field.
55 -
56 -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. An example of where this might be used is when you e-mail a link to a subscription form for requalification of a controlled circulation product. Very often users will see their information pre-populated in the form, but won't check the box subscribing (or renewing) them to the product. This option allows you to either force the user to to subscribe to a product in order to submit the form, remind the user that he or she has not subscribed but allow them to continue anyway, or just accept the day with no warning and no subscription requirement.
57 -
58 58  \\
59 59  
60 -[[image:attach:selection-required.png||height="216"]]
61 -
62 62  \\
63 63  
64 -\\
58 +PHASE B: Adding Demographic Questions.
65 65  
66 -Step 2: Define your demographic questions.
67 -
68 68  [[image:attach:AddingDemoQuesAuf22.png||height="400"]]
69 69  
70 70  \\
71 71  
72 -1. Start by adding your first demographic questionin the Demo column. All ONEcount questions that are in your question inventory will appear in the dropdown menu list.  You may also type the question name or number into the dropdown box to find a question to add.
73 -1. VALIDATIONS: If needed, select validation(s) to require a specific format for responses to this question. Allowed validations are: alphanumeric, date, email, email-match, or required field. Be careful with alphanumeric because it does not include any punctuation, meaning you could not enter (305) 555-1212. For the email validation, ONEcount only checks that the e-mail address matches an appropriate format; it does not validate that the e-mail address really exists. Email match presents two e-mail boxes to the user and requires that both entries match. This is a way to reduce data entry errors from people entering the wrong e-mail addresses in your forms. Multiple validations can be added to each question.
74 -1. AUTO POPULATE: You may choose to have fields auto populated for identified users by setting the auto populate switch to yes. This is the default. If your publication is audited and the rules of your audit require the user to enter a field manually, you can turn Auto Populate off for that specific field.
64 +1. Start by adding your first demographic question. In the first dropdown box all ONEcount questions that are in your question inventory will appear in the dropdown menu list.  You may also type the question name or number into the dropdown box to find a question to add.
65 +1. VALIDATIONS: If needed, select validation(s) to require a specific format for responses to this question. Validations include alphanumeric, date, email, or is a required field. In email match (email address matches the email in the “email” question/field), or is a number. Multiple validations can be added to each question.
66 +1. AUTO POPULATE: You may choose to have fields auto populated for identified users by setting the auto populate switch to yes.
75 75  1. To add additional questions, click the “Add” button in the top right hand corner.
76 76  1. To remove a question click the “X” at the end of the respective row.
77 -1. You can not edit a row once it had been created; if you find an error, you must delete it
78 -1. The order of the questions on this page is not important.
79 79  
80 80  \\
81 81  
... ... @@ -247,44 +247,10 @@
247 247  (% style="margin-left: 80.0px;" %)
248 248  b. Please [[click here>>attach:formbuilder-R-PaintBrush-Aug23.mp4]] to view a video showing how a button's background color was changed.
249 249  
250 -(% style="margin-left: 80.0px;" %)
251 251  \\
252 252  
253 -(% style="margin-left: 80.0px;" %)
254 -\\
242 +TEMPLATES MENU
255 255  
256 -===
257 - ===
258 -
259 -{{id name="click-thru-button"/}}
260 -
261 -===
262 - ===
263 -
264 -{{id name="click-thru-button"/}}
265 -
266 -=== Click-Thru Button ===
267 -
268 -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.
269 -
270 -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.
271 -
272 -[[image:attach:submit-button-tool.png||thumbnail="true" height="250"]]
273 -
274 -\\
275 -
276 -Now click on the button, and click on the gear icon above the tool bar.
277 -
278 -[[image:attach:click-thru-button.png||height="250"]]
279 -
280 -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.
281 -
282 -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.
283 -
284 -\\
285 -
286 -=== TEMPLATES MENU ===
287 -
288 288  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.
289 289  
290 290  [[image:attach:TEMPLATES menu Aug22.png||thumbnail="true" height="250"]]
... ... @@ -531,16 +531,10 @@
531 531  
532 532  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.
533 533  
534 -= ADVANCED FORM TECHNIQUES: =
490 +**Code for altering responses based on select type demographics:**
535 535  
536 -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.
537 -
538 538  \\
539 539  
540 -**Example 1: Code for altering responses based on select type demographics:**
541 -
542 -\\
543 -
544 544  **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.
545 545  
546 546  \\
... ... @@ -612,59 +612,6 @@
612 612  * removeInitial is assigned only once at the beginning of the script.
613 613  * All the code must be included in form extra script area.
614 614  
615 -**Example 2: Code for removing an option from the form**
616 -
617 -\\
618 -
619 -**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. 
620 -
621 -\\
622 -
623 -**Example Sample Code:**
624 -
625 -(% class="p1" %)
626 -var removeId = document.getElementsByClassName("labelId");
627 -
628 -(% class="p1" %)
629 -for(var i = 0; i < removeId.length; i++){
630 -
631 -(% class="p1" %)
632 -if(removeId[i].innerText(% class="apple-converted-space" %)  (%%)== "RemoveMePlaceHolder"){
633 -
634 -(% class="p1" %)
635 -removeId[i].parentNode.style.display="none";
636 -
637 -(% class="p1" %)
638 -}
639 -
640 -(% class="p1" %)
641 -}~/~/end of for loop
642 -
643 -\\
644 -
645 -**Steps:**
646 -
647 -* Initialize a variable to grab all the instances of the id from the form you want hidden. 
648 -** var removeId = document.getElementsByClassName("labelId"); //(notice the semi-color)//
649 -** removeId: name of variable (//you can choose a name of your choice, but remember to be consistent with the use through the code//)
650 -** labelId: replace this with the id of the field you want checked/removed
651 -** getElementsByClassName: property of javascript that allows you to get elements by the class name property
652 -* Traverse through the array of the gathered instances (of removeId), and check for the corresponding text by comparing the innerText property to  "RemoveMePlaceHolder"
653 -** removeId[i].innerText(% class="apple-converted-space" %)  (%%)== "RemoveMePlaceHolder" (//check for matches//)
654 -** RemoveMePlaceHolder: replace this with the text you want hidden
655 -* If a match is found, then grab its parentNode
656 -** removeId[i].parentNode
657 -** [i] is the index of the array where the match was found, during traversal
658 -* Change the style of the parentNode to display it as none.  This keeps the field hidden in your forms.
659 -** removeId[i].parentNode.style.display="none"; (//notice the semi-color//)
660 -
661 -\\
662 -
663 -**Note:**
664 -
665 -* All the code must be included in the form Extra Script field.
666 -* The code is to be inserted in the forms in which the value need not been shown or hidden
667 -
668 668  = DYNAMIC/PROGRESSIVE LOOK-UP: =
669 669  
670 670  This is a feature provided by ONECount.
AddingDemoQuesAuf22.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -848.8 KB
Content
DefaultTY-Aug22.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -267.3 KB
Content
Drag-n-DropTemplate.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -776.1 KB
Content
Editori-main-menu copy.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -679.6 KB
Content
Editori-main-menu.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -433.0 KB
Content
EmailConfirmationTab.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -138.1 KB
Content
FB Grid Template.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -11.5 KB
Content
FB Title.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -9.6 KB
Content
Form-builder-nav.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -35.1 KB
Content
Form-builder-page one.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -97.1 KB
Content
FormDefinitionAug22.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -804.8 KB
Content
FormDefn-TYURLAug23.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -199.8 KB
Content
Inventory Screen Shot.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -37.2 KB
Content
Screen Shot 2022-08-23 at 2.23.31 PM.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -5.4 KB
Content
Screen Shot 2022-08-23 at 2.24.42 PM.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -8.0 KB
Content
Screen Shot 2022-08-23 at 2.25.10 PM.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -6.4 KB
Content
Screen Shot 2022-08-23 at 2.28.56 PM.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -4.8 KB
Content
Screen Shot 2022-08-23 at 4.52.47 PM.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -9.3 KB
Content
Sign in:Lookup page.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -397.0 KB
Content
TEMPLATES menu Aug22.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -579.3 KB
Content
TYClosePanelAug23.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -766.5 KB
Content
TYDeleteIconAug23.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -488.6 KB
Content
TYPageDesign-Aug22.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -601.7 KB
Content
VerifyBox-LookupOption1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -217.2 KB
Content
VerifyEmailExists-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -320.5 KB
Content
VerifyEmailExists-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -260.0 KB
Content
click-thru-button.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -260.6 KB
Content
editor-object-settings.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -418.6 KB
Content
form-builder-EmailConfirmationTabAug23.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -259.5 KB
Content
form-builder-demos.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -74.2 KB
Content
form-builder-pop-up.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -49.1 KB
Content
form-builder-products-Aug22.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -613.2 KB
Content
form-builder-products.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -101.9 KB
Content
formBuilder-TYSelectDelete-Rayaan-OC2201.mp4
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -21.6 MB
Content
formbuilder-AddImage-R-Aug23.mp4
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -47.5 MB
Content
formbuilder-R-GearsURL-Aug23.mp4
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -14.1 MB
Content
formbuilder-R-PaintBrush-Aug23.mp4
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -2.6 MB
Content
formbuilder-R-YTVideo-Aug23.mp4
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -27.6 MB
Content
formbuilder-add-captchaAug23.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -195.5 KB
Content
formbuilder-completed-formAug23.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -287.0 KB
Content
formbuilder-drag-a-grid-onto-canvas.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -181.2 KB
Content
formbuilder-drag-fields-from-toolbar-onto-canvasAug23.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -222.5 KB
Content
formbuilder-edit-object-propertiesAug23.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -1.0 MB
Content
formbuilder-three-column-demosAug23.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -875.3 KB
Content
image2020-10-9_14-10-26.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -35.2 KB
Content
image2020-10-9_14-8-52.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -227.6 KB
Content
image2020-10-9_14-9-30.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -64.3 KB
Content
image2020-10-9_14-9-51.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -43.8 KB
Content
object-tools.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -437.5 KB
Content
selection-required.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -23.5 KB
Content
submit-button-tool.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.XWikiGuest
Size
... ... @@ -1,1 +1,0 @@
1 -36.9 KB
Content
Confluence.Code.ConfluencePageClass[0]
id
... ... @@ -1,1 +1,1 @@
1 -77496361
1 +77496549
url
... ... @@ -1,1 +1,1 @@
1 -https://info.onecount.net//wiki/spaces/OD/pages/77496361/Form Builder
1 +https://info.onecount.net//wiki/spaces/OD/pages/77496549/Copy of New Form Builder