Changes

Jump to: navigation, search

Forms

17 bytes added, 20:34, 17 May 2023
Determining the right structure for you?
==Determining the right structure for you?==
Now that you have determined the questions you want to ask to get the data you need, consider the “what” and “how” what is the right data structure for you within the context of SmartSimple.
'''What custom fields are right for you?'''
'''How will you get the data to the people who need it?'''
Different people may need to access data in different ways. For example, you may need to aggregate the answers or surface the answers in a report export, PDF, JSON file, web-based portal, public search, map plot, or something completely custom using the API. How you intend to output the data influences how the data needs to be stored (and where) as well as which features and fields will work best for you within SmartSimple.
 
'''Where the data will be stored within your system?'''
Consider where the data you collect is stored. For example, information about a grantee might best be stored on that grantee's profile or their organization’s profile. This way the user is not required to enter the same information into multiple forms. If information needs to be displayed in multiple locations or multiple systems, consider where the single source of truth will be and what features will be used to update other locations such as system variables, data exchange, or the SmartConnect API. If data is coming from an outside source, consider which integration you will use. For example, you may choose to populate an organization's details based on the information from the IRS verification service instead of having the user enter their own organization details.
'''How will you coordinate data structures across programs?'''
You may have many programs running for many years across many teams. Think about how you can ensure the use of the same fields and structures across multiple programs and teams. Also consider if your application cycles require the use of versioning so form changes are only applied to specific cohorts of applicants.
 
'''Where the data will be stored within your system?'''
Consider where the data you collect is stored. For example, information about a grantee might best be stored on that grantee's profile or their organization’s profile. This way the user is not required to enter the same information into multiple forms. If information needs to be displayed in multiple locations or multiple systems, consider where the single source of truth will be and what features will be used to update other locations such as system variables, data exchange, or the SmartConnect API. If data is coming from an outside source, consider which integration you will use. For example, you may choose to populate an organization's details based on the information from the IRS verification service instead of having the user enter their own organization details.
'''How will the process flow?'''
Smartstaff, administrator
3,320
edits

Navigation menu