• Launch Application Form Editor 
   
• Designer Tab 
  • Add Mapped Questions to Form
  • Add Unmapped Questions to Form
  • Add Questions to Panel for Related Constituent or Contact
    
    Question Properties
  • Question Properties - General
  • Question Properties - Mapping
  • Question Properties - Layout
  • Question Properties - Conditions
  • Question Properties - Data
  • Question Properties - Validation  
     
• Branching Logic
  • Build Logic from Tab
  • Build Logic From Question
  • Review Logic From Tab
     
• Preview Tab
   
• JSON Editor Tab
   
• Form Settings

  Launch Application Form Editor

 

As stated above, Simple Form Builder is the default for any new phases built after August 28, 2025.

To launch the Application Form Editor, navigate to a Phase record > Form Editor tab. For more information on creating Opportunities and Phases, please see the GOapply Administrator Guide - Building Opportunities.

 

Click the Launch Application Form Editor button:

The Transcript Form Editor and Recommendation Form Editor are related to Third Party Responses, a feature that captures external responses, namely letters of recommendation and transcripts. For more information on Third Party Responses, please see the GOapply Third Party Responses Administrator Guide.

  Simple Form Builder - Designer Tab

 

Within Simple Form Builder, you will see four tabs - Designer, Preview, Logic, and JSON Editor. 

The Designer Tab is where you will add questions and panels to the form.

 

On the left side of the screen, you will see questions available to add to the GOapply phase/form.

This includes two sections – Unmapped and Request. 

The Unmapped section includes questions that will not be mapped to any field/record in akoyaGO. Meaning, the GOapply user's responses will be captured in the PDF created upon submission, but the data will not be transferred to a corresponding field in akoyaGO. These questions cannot be manually mapped. Any data that you will need to reference in views, reports, etc., should be captured via a mapped question.

The Request section includes questions mapped to corresponding fields in the Request table in akoyaGO. This includes custom fields for your organization. These questions are pre-mapped to the related field in akoyaGO and inherit the field's properties when placed in the GOapply form. 

 

Contact and Constituent records that are related to the Request (such as Applicant, Payee, Primary Contact, etc.) can be added as panels to the GOapply phase/form. Panels are also pre-mapped to the related record  in akoyaGO. Detailed information about panels is included below in the Add Questions to Panel for Related Constituent or Contact section.

 

  iAdd Mapped Questions to the Form

To add questions to the form, drag and drop or click the question from the side navigation bar.   

• Drag-and-drop allows you to place the question wherever you want in the phase.
• Clicking the question will add it to the bottom of the page, and you can drag it to a different place using the arrow pointer.
   

For mapped questions added from the Request section, select the corresponding akoyaGO field name where the GOapply user's response should be saved (in akoyaGO).
For example, if I am inserting the question How much are you requesting?, I would most likely want the GOapply user's answer to map to the Requested Amount field in akoyaGO.

Scroll through available questions/fields in the Request section, or search in the top bar: 

 

  iAdd Unmapped Questions to the Form

For unmapped questions, you will choose what type of question you want to insert. 

• Checkbox: This question type is used for questions where the applicant can select multiple options. This is the only question type that allows multiple items to be checked. Only the selected options are recorded in the PDF.  Example: What Social Media Sites do you use?
• Dropdown: This question type is used for multiple-choice questions where the applicant can choose only one option. This question type can be used for questions with many options (such as lists of countries, states, etc.) because it requires the user to click into the question to select an option.  Example: Please select the group of people to benefit from this grant.
• Dynamic Matrix: A Dynamic Matrix is an extendable input field that enables respondents to provide multiple answers within a single question in table format. Below is an example of how one might use a dynamic matrix.

• Expression (read-only): This field is best utilized for calculating amounts. Set the expression in the General section of the question properties: 

Use curly brackets to access the question values. For example, if you wanted to add two field amounts, your formula would be {question19} + {question20}. For calculated fields that the applicant should not see, you can uncheck “Visible.” It will still calculate if hidden. 

• File Upload: upload file. Many details can be specified in the Properties tab, including the maximum file size, accepted file formats, and the preview area. File formats are restricted by a comma-separated list of file extensions, including periods, e.g., .jpg,.pdf,.png. For security, please specify the allowed file formats for uploading to the survey. Each field is limited to a single file.   Accepted file types are = txt, rtf, doc, docx, xls, xlsx, png, jpg, jpeg, gif, csv, ppt, pptx, pdf, mp4. Maximum file size = 20MB

              

 

*Please note that if the GOapply user uploads an Excel workbook with multiple sheets, only the first sheet will be added to the Submitted File. Larger files can be accepted, but only one sheet will be stitched to the Submitted File. The full workbook can be accessed in the Status Tracking Attachments or Documents section. We advise that Excel attachments submitted via GOapply contain only 1 sheet of data, and that instructions are added to the question to indicate this.  
 

• HTML: This is a rich text editor. Best practice is to type and format your text in the space provided. To make the text editor larger while you are editing, select the button to expand. It is not recommended that you copy and paste text from MS Word or any other text editor in this box, as it will cause issues with how your final PDF is rendered. 'Heading' font types are not supported.   
   
• Image: allows an image to be uploaded or linked into the application. This is not an image upload field for the applicant.
   
• Long Text: can be used for detailed, multi-line answers. If you want to allow the applicant to format their answers (bold, italicize, underline, etc.), choose the Rich Text Editor question type instead. Character count limits can be placed on Long Text question types. 
   
• Multi-Select Matrix:  a type of survey or form question that presents a grid or table structure where respondents can select multiple answers for each row or column combination. Below is an example of how one might use a multi-select matrix.

 

 

• Multiple Textboxes: The Multiple Textboxes question allows applicants to enter several short, related pieces of information within a single question. Instead of asking multiple separate questions, this format groups related responses together using labeled text fields, making the form easier to complete and review. It is best used when collecting structured, brief details—such as lists of instructors, budget line items, or event information—where each response belongs to the same overall question and does not require a long narrative answer.
   
  

• Rich Text Editor: Long form response. This question type is used for narrative, long answers, such as unmapped essay questions. A text box is presented to the applicant. The applicant can apply formatting with this option. There are no character limits on the input, so the applicant may enter any length of text. If your question requires a character count limit, utilize the Long Text question type instead.
   
• Signature: allows applicant input to be directly drawn on screen in a pre-set box or area. This is typically used to obtain a signature; however, it could be used to obtain any hand-drawn input. The box size can be changed by clicking the Properties tab. The pen and background colors can also be modified. The applicant's input is recorded in the PDF as JPEG, PNG, or SVG. This file format may be changed in the Properties tab. 
• Single-Line Input: single line text. Use for short answers such as dates, email addresses, numbers, phone numbers, texts, URLs, etc. There are no limits on the input, so applicants may enter any text, however long.
• Single-Select Matrix: This is useful when you need to ask respondents to rate statements on the same scale. A good matrix table question example is a Likert scale survey question (also known as a satisfaction scale). Below is an example of how one might use a single-select matrix.

  iAdd Questions within a Panel for Related Constituent or Contact Records

For questions that will map to lookup fields on the Request table in akoyaGO, you will insert a Panel. For example, if you are asking questions about the Request – Primary Contact or the Request – Applicant Constituent, you will group them together in a Panel.

The questions within a Panel will map to the record related to the Request (i.e., the Applicant’s constituent record, the Primary Contact’s contact record).

 

In Simple Form Builder, Panels are denoted by an open square.

 

*Please note that a panel mapped to Request - Applicant is not required, as the GOapply user identified the applicant constituent upon registration. We recommend taht information for this constituent is updated and maintained in the Organization Profile. However, if you want the applicant's information to appear on the PDF created upon submission, you may still choose to include an applicant panel within your phase.

 

Panels will come loaded with at least one field that is marked Is Lookup. This is the field akoyaGO will search to see if the related record already exists. If so, it will update the existing record instead of creating a new one.

For a Contact panel/lookup field, we recommend using Email Address, as this is the most unique identifier for an individual.

For a Constituent panel/lookup field, we recommend using EIN/Tax ID AND at least one other matching value, for example, Constituent Name or City, to help distinguish between unique constituents that share a Tax ID/EIN (such as schools within a school district, departments of the same organization, etc).

The lookup field(s) can be reviewed and changed from the Mapping section of the Question Properties for a question within a panel. More information on Mapping will be covered in the Question Properties - Mapping section below.

 

Once pulled into the form, the panel will have a +Add Question option. This is how you can add questions about the related record within a panel.

For example, below is a Primary Contact panel that was added from the toolbox. It comes preloaded with one question about the Primary Contact, their Email Address. This is the lookup field. 

Click +Add Question to add other questions about the Primary Contact; this is how to insert fields/questions from the related Contact record.

 

 

 

  iQuestion Properties - General

After you add a mapped or unmapped question or panel to the form, you will set/review General Properties for each question from the left side panel. 

 

• Question name: is internal-facing information. This is used to identify the question and becomes particularly important when developing any logic in this phase. More information on Branching Logic is included below. 
  For mapped questions, this will default to the field's schema name. For unmapped questions, we recommend setting the question name to something that makes it easy to identify. (For example, FutureGoals or ProposedOutcomes.) Question names must be unique; duplicate names will cause issues with mapped questions. The question name cannot include spaces or special characters. Keep question names under 50 characters for branching logic to work as intended.
• Question title: is external-facing information. This is how the question will be worded in the GOapply UI for the GOapply user. For mapped questions, this defaults to the field name, but can be changed if desired.
  • The Question name and Question title may be set to the same value for a question, or you may choose to set the Question name to an abbreviated version. For example, the Question name might be Requested Amount, while the Question title might be Please provide the amount you are requesting.
• Question Description: appears under the Title on the application; this is optional and can provide additional context or guidance to help applicants understand how to answer the question.
• Hide from Reviewer: if checked, will hide this question from the PDF that is displayed to reviewers in the GOapply UI 
• Visible: turn off to hide the question from the applicant. This setting overrides the Is required setting. This setting is beneficial to use in conjunction with Default Values. For more information on Default Values, please see Question Properties - Data section. Note that when the "Visible" property is off, the question will also be hidden from reviewers.
• Read-only: if enabled, applicants will be able to see the question but not enter an answer.
• Required: turn on to make a response required by the GOapply user.
• Show the title and description: turn off to hide the question title and description in the GOapply UI.

 

  iQuestion Properties - Mapping

Within the mapping section, you can review the Target Entity and Target Field that are automatically set for mapped questions: 

This section will not appear for unmapped questions. 

The Overwrite existing checkbox will be checked by default for mapped questions. If checked, applicant response will overwrite any existing data in the corresponding field in akoyaGO. For fields mapped to Request in the first Phase of an Opportunity, the Request does not exist yet, so the questions mapped directly to the Request (not in a panel) do not yet contain data. However, this is something to consider for later phases, or for any questions within panels that could be impacting existing Constituent or Contact data. If you do not want the GOapply user's answer to overwrite existing data, make sure to uncheck this option. 

Please see GOapply Prefill Data - Simple Form Builder for more information on mapping to fields with existing data (especially in later phases)

 

  iQuestion Properties - Layout

  iQuestion Properties - Conditions

The Conditions section allows you to build conditional logic around this question. For more information, see Build Logic From Question.

  iQuestion Properties - Data

The Data section allows you to set a Default Answer for a question and control settings related to hidden values and input field values.

For example, I may want all Requests created for an Opportunity to be titled consistently. This is not a question I want applicants to see, but I want a Default Value to be applied upon submission when the Request is created in akoyaGO.

To do this, I will add a mapped question for the Request - Title field:

Because I do not want the GOapply User to see or answer this question, I will make sure to uncheck the Visible option under the Question Properties > General section: 

Then, I will set a Default Value for this question in the Data section: 

You can quickly check this from the Preview tab. If you want to display invisible elements in the Preview tab, make sure to click the icon in the top corner. The preview tab does not replace actual testing. You should thoroughly test any Default Values prior to publishing the Opportunity to GOapply Users to ensure the Default Value sets are as expected in akoyaGO. For more information, see the Preview Tab section below. 

  iQuestion Properties - Validation

Allows you to set validation rules, error messages, and a maximum character limit.  

For mapped questions, the maximum character limit defaults to the corresponding field's limit in akoyaGO. You can reduce the maximum character limit in GOapply to a smaller number, but it cannot exceed the actual field's character limit. 
A System Customizer user can find and increase field lengths in Power Apps. For more information, please see System Customizer Video - Column Properties or MS Learn - Create Field & Max Length.

Please note that when you add a mapped question via Simple Form Builder, the field’s properties (including character limit) are validated as they exist at that moment. These properties are saved and not automatically synced again when you make changes in Power Apps. This is by design, to keep the form stable and prevent unexpected changes. If a System Customizer has changed the properties of a field, such as a character limit, after a question has been added to a GOapply Form in Simple Form Builder, you will need to remove the question in Simple Form Builder and re-add it from the toolbox for the updates to take effect.

  Branching Logic

 

Logic can be built or reviewed directly from the Logic tab at the top of the page. Alternatively, you can also build logic from the Properties of an individual question from the Designer tab. Both methods will be covered in this section. 

 

  iBuild Logic from Logic Tab

Click the Logic tab and choose Add New Rule.

Click the Select… box to choose the question this logic begins with. 

In the Equals box, select the operator for your logic. The operators that appear here are dependent on the type of question chosen for the condition.

For example, if I am setting up logic to display and require a question if the Requested Amount is Greater than $10,000.

Because I am building logic around the Requested Amount question, which is a currency value, I see options like Greater Than, Less Than, etc.

 

If your operator requires additional information, add it below. For example, I chose Greater than, so I need to tell it an amount:

 

If you would like to add more conditions, click the Add Condition button again: 

Set additional conditions as needed. Make sure to consider and (meaning both conditions must be true) vs or (meaning either condition can be true):

 

Once you have built your conditions, set the action. Click Select action… to set the conditional action 

• Show/hide page: Makes the selected page visible. If you want to hide the page, invert the condition.
• Enable/disable page: Makes the selected page editable. If you want to make the page read-only, invert the logic of your condition.
• Show/hide question: Makes the selected question visible. If you want to hide the question, invert the logic of your condition.
• Enable/disable question: Makes the selected question editable. If you want to make the question read-only, invert the logic of your condition.
   

Click Add Action to add more than one action that will occur when this condition is met.

 

For example, here is my completed logic that will require and display a hidden question when the Requested Amount is greater than $10,000:

 

When you are finished, click Done.  

 

To edit an existing Rule from the Logic tab, click the rule. This will allow you to make changes. Make sure to click "Done" once you have adjusted as needed.

 

  iBuild Logic from Question

Alternatively, you can build logic from the Designer tab within the Question properties. Because you are working directly from the question, this method does not require you to identify the question within the action step(s).

 

Add your question to the form, and click on the Conditions icon in the sidebar:

 

Click the wand icon to define the condition around the appropriate action(s): 

 

Using the same steps listed above, define the condition(s). For multiple conditions, click the Add Condition button.

Once you are finished, click Apply.

 

Here is an example of logic from the question properties:

 

  iReview Logic from Logic Tab

 

  Preview Tab

 

The Preview tab lets you see how your phase will appear to the GOapply user. This can be used to quickly test formatting and branching logic.   

Click the laptop icon to change the device you are previewing your form from: 

Click the eye icon to show/hide invisible (hidden) pages or questions: 

Though the Preview Tab is useful for quickly checking formatting and logic and for seeing the form as a GOapply user will, it does not fully replace testing a phase. For more information on testing, please see GOapply Testing Best Practices.

  JSON Editor Tab

 

This tab displays the phase in JavaScript Object Notation (JSON) format, which can be useful if you are comfortable reviewing JSON. If you are not familiar with JSON, all required configuration can be completed using the Form Designer tab, and the JSON Editor is not needed. 

Please note that the JSON Editor tab is intentionally set to read only. Editing in the JSON Editor tab is not supported, as it may cause JSON corruption. This tab is intended for viewing the phase in JSON format only; all edits should be made using the Form Designer tab.

 

 

  Form Settings

 

Form Settings allow you to configure settings for the entire phase, such as question numbers, a thank-you message, and when validation will run. For more information on Form Settings in Simple Form Builder, please see Simple Form Builder - Form Settings.