In some cases special codes can be embedded that will be replaced with dynamic content. For example, if a form is used as part of an application packet for multiple positions, the specific position title being applied to can be shown in the form. All substitutions in forms are coded in the form of [special_code].
These codes can be used within form Labels and Content sections when relevant:
- [organization_name] – (e.g. “Memorial Student Center”).
Future: Should this use the name of the organization owning the form or the organization using it in the context of a a specific web session? For example, the MSC may make a form available to all of its member committees. Should the replacement show “MSC” as the parent organization or the committee (e.g. “MSC SCONA”) using it for a membership application? The owner of a form will always be defined, but may be ill-suited for a specific context. The context organization may be ill-defined (or harder to determine) in some use cases (such as an endorsement form for a third-party).
- [position_name] – Substitutes position title (e.g. “President”), except when used in Endorser forms in which case it shows “position of organization” (e.g. “President of Memorial Student Center”, a.k.a. purpose)
Future: This code should be reworked to yield a consistent result regardless of context. It should always be only the name of the position without the organization name be appended.
- [position_description_link] – Substitutes a web link (e.g. “https://getinvolved.tamu.edu/positions/1“)
- [application_deadline] – Substitutes position posting end date/time as “2020-01-31 00:00:00.000”
- [interview_dates] – Not yet fully implemented (shows “TBA”)
These appear to currently only work for Endorsements (Q: Are these simply the form field IDs?):
- [applicant_name]
- [appraiser_name]
- [relation_type]
These appear to currently only work for Endorsement email templates (Q: Are these simply the form field IDs?):
- [FormDescription]
- [purpose]
- [RequesterName]
- [EndorserName]
- [UniqueLink]