~~~ Please read before posting. ~~~

Important: We need your Club Number at a minimum, and as many details as possible.
For further info please read This page before posting.

Variable scope inquiry

  • NotLiable
  • NotLiable's Avatar Topic Author
  • Offline
  • FreeToastHost Ambassador
  • FreeToastHost Ambassador
  • Posts: 250
  • Thanks: 38

Variable scope inquiry

5 years 9 months ago
#78002
Hi,
I reviewed your post "[2019-09-27 09:35:18 GMT, FTH Developer] More variables have been added for your use in Agenda Emails." To test out all variables, I updated my test file bo be as below. It looks like some variables (FN caps, LN caps, caward, laward, and awards) only work within the scope of generating a name tag, while others might be confined to the scope of an agenda e-mail and/or Basic e-mail setting. Is this the case, where certain variables are only available in specific contexts?
Next, I can't figure out what the nextmtgcount and nextmtgordinal variables represent. When I, in the meeting agenda context, send the field test e-mail, those fields showed nextmtgcount: 127 and nextmtgordinal: 127th. What do "127" and "127th" mean?
It seems that an explanation (including scope) of all available variables would be worthwhile to include in the documentation.

Regards.

<!DOCTYPE html>
<HTML xmlns=" www.w3.org/1999/xhtml " xml:lang="en" lang="en-us">
<BODY>
<!--
File: FTH Variable Test.html
Author: Arthur L. Farnsworth
Purpose: File to test all of the variables offered by FTH
Created: 10 Jul 2017
Revisions: 31 Aug 2017 Rename file from Name badge test.html
28 Nov 2019 Add remaining variables to test them all
-->
<!--
Print all field names and values
-->
name: {{name}}<BR>
firstname: {{firstname}}<BR>
lastname: {{lastname}}<BR>
FN caps: {{firstnamecaps}}<BR>
LN caps: {{lastnamecaps}}<BR>
namesuffix: {{namesuffix}}<BR>
datejoined: {{datejoined}}<BR>
membersince: {{membersince}}<BR>
officerrole: {{officerrole}}<BR>
emeritus: {{emeritus}}<BR>
clubname: {{clubname}}<BR>
clubnumber: {{clubnumber}}<BR>
caward: {{caward}}<BR>
laward: {{laward}}<BR>
awards: {{awards}}<BR>
<!--
Here are variables added for agenda e-mails
See support.toastmastersclubs.org/2011-10-23...ed-for-agenda-emails
The first set are Member Variables, which are the name, firstname, lastname, namesuffix, officerrole, and emeritus variables from above.
Next are the Next Meeting Variables
-->
nextmtgtm: {{nextmtgtm}}<BR> <!-- Name of TMOD for next meeting -->
nextmtgttm: {{nextmtgttm}}<BR> <!-- Name of Table Topicsmaster for next meeting -->
nextmtgge: {{nextmtgge}}<BR> <!-- Name of General Evaluator for next meeting -->
nextmtgdate: {{nextmtgdate}}<BR>
nextmtgtime: {{nextmtgtime}}<BR> <!-- Start time of next meeting -->
nextmtgcount: {{nextmtgcount}}<BR>
nextmtgordinal: {{nextmtgordinal}}<BR>
<!--
Lastly, the Club Website Variables. clubname and clubnumber from above are here, as is weburl
-->
weburl: {{weburl}}<BR>
<!--
There are also adminname and adminemail
-->
adminname: {{adminname}}<BR>
adminemail: {{adminemail}}<BR>
</BODY>
</HTML>
The topic has been locked.
  • SteveTheTechie
  • SteveTheTechie's Avatar
  • Offline
  • Administrator
  • Administrator
  • Posts: 11526
  • Thanks: 3050

Re: Variable scope inquiry

5 years 9 months ago - 5 years 9 months ago
#78003
The only variables that are valid for a particular context are those that are in the drop-down list or pop-up associated with that context.

1. I will not be making all variables available for all context.
__Reason: Variables that associated with a particular member's name or a particular meeting would have no meaning when inserted in a general web page. (specific examples for illustration)

2. There are really three categories of variables, at this time:
__a. Information about a particular member.
__b. Information about a particular meeting.
__c. General club/website information.

__> There may be other variables added in the future for these categories. We also have variables for dues notices, but unfortunately, those are (currently) totally separate and implemented completely differently.

3. I am very reluctant to make commitments about what variables will or will not be added. In fact, some could be eliminated in the future. (Think {{caward}} & {{laward}}, for example, which do not work with Pathways.)

4. nextmtgcount: 127 and nextmtgordinal: 127th are just related to a count of many meetings (agendas) your club has in the system. e.g., "Meeting # 127" or "127th Meeting".

5. I think we would be happy for any kind of documentation contributions you would like to make related to this.
Last edit: 5 years 9 months ago by SteveTheTechie.
The topic has been locked.
Moderators: BrianJane AtkinsonPamrhtaylor3marc33NotLiablejgavinLcala305peterb323
Time to create page: 0.250 seconds