|Any string replacers you set up are available to all forms within the FormFlow instance.|
String replacers are a type of data source. They can be used to extract that data from an external database you have set up a connection to. Jenzabar-provided string replacers are available on the wiki.myjenzabar.net Literal String Replacer page.
In the example below, a string replacer can be used in the email being sent to the form user that could add their name to the email.
Create a String Replacer
1. Click the Add icon.
2. In the Name field, enter an easily recognizable name for the string replacer.
3. From the Literal Type drop-down, select Static or SQL Fragment.
· Static is a string value that will always replace the tag. For example, you can annually update all of your forms to use “@@CurrentAcademicYear.” You’d type in “2016” and anywhere that tag is typed, 2016 will replace it. Static tags are infrequently used.
· SQL Fragment is a SQL SELECT statement that returns the value that should replace the tag.
4. If you select SQL Fragment, the Database drop-down pick list appears. Select the database you are using to create the string replacer.
Only those databases you have established a connection with will be available to be selected.
5. From the Cache Mode drop-down select, User, Application or None.
· User means the value will only be refreshed once per user. This prevents the replacer engine from having to access the database multiple times for the user. These values are typically user specific and do not change (e.g., birthdate).
· Application means the value will be refreshed once for the entire application. All users accessing this value will receive the same response. These do not change regularly (e.g., @@SchoolMotto).
· None means the values will not be cached. The SQL fragment will be executed against the database every time it is requested. These may change frequently (e.g., @@ CurrentGPA0.
6. Click Save and Test.
7. Click Done.