Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

e

Table of Contents
outlinetrue

...

  1. Box # 1: Still shows the Main Menu Groupings. This is convenient if you need to switch back and forth between two different "Main Menus" while building a form.
  2. Box # 2: Shows the Submenu "Grant Request" and the already-built Themes (different application form types) underneath the submenu. If you want to edit/preview a specific theme, simply click on its name from this list to select it.
    1. Additionally, you can find the "New Theme" button at the of this list before "Retired Themes" and "Filter." This allows you to create a new application form either from scratch or by copying another form first.
    2. Note # 1: Clicking "New Theme" will pull up the a window with both the options to create the new theme from scratch AND to copy the existing view of another theme. It is recommended to always start an application by copying another, and then making the necessary changes on the copy.
    3. Note # 2: Whenever you create a new theme, you MUST also create a Workflow for that new theme. If a new Theme is created without a Workflow given to it, users will NOT be able to perform any workflow actions (i.e. submit their application or Requirement).
  3. Box # 3: Displays the Preview of the Theme currently selected. In the example screenshot, you can see a Preview of the "2022 COVID-19 Response Application" (the currently selected Theme).
  4. Box # 4: Displays where you can find Retired Themes. These are application forms that are no longer used, but can still be found for referential (and copying) purposes. Click on "Retired Themes" to see a window with all of the application forms that are no longer used; from this window, you can also "Unretire" these themes (i.e. make them active application forms once again).
  5. Box # 5: Displays the "Builder" button; this is what you'll press in order to begin Editing the form itself. See the next section "Builder and Configuration View" for more information on this.
  6. Box # 6: Shows the toggle that allows you to switch an application form from being in "Draft Mode" (not yet usable) to being "Active" (ready for use as an application form). Best practice recommendation is to leave unfinished applications forms in Draft status until they are completed, after which you MUST ENSURE you move it to Active status otherwise the form will not be accessible.

...

  1. Box # 1: Shows the Theme (Form) itself (in this screenshot, the 2022 COVID-19 Response Grant Application Theme) in Builder mode. In Builder mode, all of the text and fields that are found on the Theme can be be seen as a rectangular box boxes (see screenshot below for example). The item that is currently Within Fluxx, each separate box is now as an element. The item that is currently selected is highlighted in Light Blue. In the screenshot, above, the Group item "(list view)" is selected. Items selected can be dragged around the screen in Box # 1 in order to move the position of this item around. Example box:  
    1. The Color found on the far right-hand side of each of these boxes indicates what type of item it is on the form. 
      1. A Green strip indicates a Group item. Groups are used to organize fields on the form. Text items, component items, and field items can be placed underneath Groups to either visually "group" those items underneath the Group header, or just to group them on the backend for administrative ease without having a visual effect on the Form. See an example of how items get visually "grouped" here below:
      2. Yellow (or Gold)  strip indicates that the item is Text. Text items are NOT fields and all text within them can be edited/changed as needed.
      3. Red/Pink strip indicates that the item is a Component. Components are fields (almost under their own Field Type) added to cards to perform a specific predetermined job. These can range from document components which allow you upload/store documents to Financial components and everything in between. Please see this Fluxx page for the full list of Components offered in the system. Please note that components are always evolving and being added.
      4. A Light Blue strip indicates that the item is a normal Field. This (along with Yellow-stripped Text items) is the most used item on all Themes.
  2. Box # 2: Shows the configuration for the specific item selected. In this case, since the Group item "(list view)" is selected, you can configure how that Group item functions. More information specifically about how all Items can be configured can be found in the dedicated Configuration sections below.

Group Configuration

Adding a New Element to a Form

Within the Fluxx builder menu, it's easy to add new fields/text/components to the form. To add a new item (also known as an element) to the form, simply hover your moues towards the bottom right-hand corner of any previously existing element until a while plus ("+") button appears on your screen (see also the screenshot below). By default, the system will add an element of the same type as the element that is currently selected by your user. So, in the example below I've selected a "Text" element (you can see by looking at the element that is highlighted in Light Blue), clicking on that white plus ("+") button will by default add a new text element to the page.

Image Added


If you need to change what type of element is added, do not fret. When you go to add the new element, the attributes tab will show the kind of the element that is going to be saved. You can use the dropdown menu to select the appropriate type you need. See below for descriptions of each of the various types.

Image Added

  1. Component: This element will based on a Component. These are unique "fields" that differ widely one from the other. See the Component Configuration section for more details.
  2. Field: The most used type. This will allow the element to pull in a column from the record type in question; e.g. if we're looking at a Grant Requests form, any column off of the Grants Request data type can be pulled into a field element.
  3. Calculated Field: Same as field, above, but can pull in calculated fields as opposed to your run of the mill columns. Calculated fields are fields that use math to combine several different "real" fields into one, combined numeric field. Think "Total Score" on review records as an example.
  4. Group: Groups are used to group various fields and other element types. See the Group Configuration section for more details.
  5. Text: Used to configure flat (or dynamic) text on a form. See the Text Configuration section for more details.
  6. Image: Can be used to upload an image. Not widely used by the WPP.
  7. Spacer: As the name implies, adds at least 1 line of space wherever this element is added. The element can also be adjusted to add more than one line of space, if so desired.

Group Configuration

Groups have specific Configuration options that are good to be aware of. Groups are very important for Form design as they allow for several pieces of additional functionality: for Groups have specific Configuration options that are good to be aware of. Groups are very important for Form design as they allow for several pieces of additional functionality: for example, they (1) allow for a dynamic table of contents that allows you to include within the TOC the Groups most relevant to the record in question and (2) allow for dynamic If/Then Logic (also known as Hide/Display Logic in this guide), e.g. if I select "Yes" for Field X, then display Fields W, Y, and Z (but don't display W, Y, and Z if I select "No" in Field X).

...

Since each component is different and performs a specific job, each has its own configuration settings. Let's take a look at a few two examples and see some of the different configuration options available.

...

Some components, on the other hand, have quite a few configuration options. A good example of this latter type of component is the "Program Org" component. Below, you can find a screenshot of what this component looks like on a Form with only a few pieces changed from the default configuration (added to the default are the "Project Staff 1-3" fields, the last three in the list)of component is the "Program Org" component. The component allows you to select the Organization to attach to your grant (or will be auto-populated for Grantees that are connected to only one organization). It also allows you to list who at the organization listed will be the Primary Contact on the grant, the Primary Signatory on the grant, and (if desired) up to three other staff who will be working on the grant/submitting requirementsbe working on the grant/submitting requirements.


Below, you can find a screenshot of what this component looks like on a Form with only a few pieces changed from the default configuration (added to the default are the "Project Staff 1-3" fields, the last three in the list).


And below you'll find a screenshot of how this Component is configured from the Builder menu on the Admin Panel. Please see the descriptions below the screenshot to get a sense for what can be configured within this component.

...

  1. Box # 1: Displays the component within the builder screen and shows that we've selected the "Organization" component for configuration.
  2. Box # 2: Shows three checkboxes that configure this component.
    1. Grantee can be a Person: Allows for a checkbox on the form that, when toggled, will switch between the "Lookup" search box for Organizations (when checkbox is unchecked) to the "Lookup" search box for People within the system (when the checkbox IS checked). If using the People lookup function, the Grant will only be directly linked to a Person record and will NOT have any links to any organization records.
      1. Example of what this looks like (with a configured label for the checkbox):
      2.  
      3. This is NOT recommended as the WPP wants to have links to an Organization stemming from all Grants. For PERC members (who don't have a "real" organization), the Organization record is more or less a match of their user record but with additional details (such as the street address of their office at the UW).
    2. Grantee must be a Person: Similar to Grantee can be a Person, above, the difference is that there will be NO checkbox to toggle between searching People and searching Organizations; instead, there will ALWAYS be the search box for People, with no option on the Form side to search for Organizations.
      1. This means that, when selected, Grants that have this Theme will NEVER be connected to an Organization record. Recommended against.
    3. Freeze Organization, Organization Location and Grantee User in the states below: This allows you to configure this component such that the fields found within (i.e. the Organization, the Organization Location, and the Grantee contacts) are FROZEN (that is, not editable) in the statuses that you specify in the right-hand side box below the text "Freeze in these states." This can be useful if, for example you don't want the Grantees to be able to change their co-PIs during or starting at a specific stage in their application process. E.g. "After the Letter of Interest is submitted, the Grantees will not be able to change their organization or co-PIs."
  3. Box # 3: Contains the spots for two different labels.
    1. Person Grantee: This label is used when the "Grantee can be a Person" checkbox is selected. It allows you to configure the text next to the Checkbox that allows you to toggle between an "Organization" grantee and a "Person" grantee.
      1. See the example from Box # 2 to see what this label looks like.
    2. Organization Label: This label is used when the the Form is using an "Organization" grantee rather than a "Person" grantee. Determines what the label for the "Organization" record will be called. Default is to leave the label as "Organization."
      1. Example of what this label looks like:
  4. Box # 4: Contains the Allow blank child field values (Enabling this removes auto population of fields) checkbox. When NOT selected, picking an Organization record for the Organization search bar will auto-populate the Location field with "(Organization Name) – Headquarters," and the Primary Contact, Primary Signatory, and Project Staff 1 - 3 fields with the Primary Contact as stored on the linked Organization record. If this checkbox IS selected, then just the Location field will auto-populate and the Grantee contacts fields will stay blank unless manually filled in by a user.

  5. Box # 5: Shows the Satellite Organization Label. This is a slight "misnomer;" this label actually determines what the label for the "Location" field will be (see Box # 3 sub-bullet b.ii. to see an example of the Location label rendered as "Location").
    1. In Fluxx, Satellite Organizations can be created for an organization that has offices in multiple locations. The satellites are not separate organization records with their own set of contacts, but rather a sub-set of one organization that can be selected in the program org component on a request.
    2. So, if you have a satellite Organization linked to the Organization that is linked from the Grant, your Location field will give you a dropdown menu with "(Org Name) – headquarters" as the first option and "(Org Name) – (Satellite Location Street Address, City)" as the second option.
      1. Example of what the dropdown menu looks like here:
  6. Box # 6: Shows the Organization Location Label. This determines the label for the Location field when this component is shown in Detail view (and NOT in Edit view).
    1. Screenshot of what this looks like when the label is changed to "Org Location": 
  7. Box # 7: Shows the Organization Owner Label. This is used as the label for the Primary Contact on the Grant record. As such, WPP uses the label "Primary Contact" (as you can see from the various screenshots of this component, above). Use this field if you'd like to change the label from Primary Contact to something else (e.g. "Principle Investigator").
  8. Box # 8: Shows the Organization Owner Profile and Organization Owner Role filter options. Use these options to ensure that the person selected to be the Grant's Primary Contact meets certain criteria, e.g. that the User has a "Grantee" profile available to them (i.e. they can get into the Grantee Portal) or that they have a specific user role.
    1. Note: For each "User" available from within the Program Organization Component, the Profile and Role filters are available as well as a filter for "Program." It is generally recommended against using the Program filter, as the WPP recommends listing all users under "All Programs" (so there isn't much to filter out from that field).).
  9. Box # 9: Shows the Delete button where you can remove this component if you so desired. Note: Deleting the component will delete any configuration options you have saved for it; if you were to add the same component back to the Form afterwards, it would be added with all configurations moved back to the default.

Below Box # 8 Below the area seen in the screenshot, there are additional configuration options to add the Project Staff 1 - 3 fields and ensure, like for the Organization Owner user, that these users meet specific criteria regarding their Profile or Roles.

Field Configuration

Similar to components, each field type has its own configuration options, ALL of which are discussed in detail on the page Fields, Field Types, and Field Modification in this guide. Please review the configuration options for each of the Field Types there to get a better sense for what can be changed/made to function differently within the Fluxx Admin Panel.

Values, Visibility, and Styling Configuration