One special, technical use case for custom fields on a record involves creating a custom field on the section form that contains a URL that links to a separate application.  This URL must contain information about the section record that is passed to the application.  In this scenario tokens can be specified in the custom field that Astra Schedule will replace with the actual values for the specific section or meeting that is being displayed.

 

This use case is supported with section and section meeting custom fields.

 

The following tokens (beginning with $) are allowed:

 

•Section meeting values
 
$sectionmeetingid
$sectionmeetingsiskey

 

•Term values
 
$termname
$termsiskey

 

•Course values
 
$coursenumber
$coursename
$coursesiskey

 

•Subject values
 
$subjectcode
$subjectsiskey

 

•Section values
 
$sectionid
$sectionnumber
$sectionsiskey

 

•Campus values
 
$campusname
$campussiskey
$campusid

 

NOTE:  $sectionid, $sectionmeetingid and $campusid are GUIDs.

 

For example, a custom display-only URL Custom Field with the value:

 

http://hostname/appname/page?subject=$subjectcode&course=$coursenumber&sectionnumber=$sectionnumber&term=$termname&campus=$campusname

 

will be rendered on the page with the tokens replaced with values from the database, similar to this:

 

http://hostname/appname/page?subject=ACCTG&course=100&sectionnumber=A&term=2011SP&campus=MAIN

 

NOTE:  In single sign on environments, it is also possible to include a single sign on token ($SSOTicket) that will be replaced with the SSO ticket used for the session.  Astra Schedule will capture the SSO ticket during the login process.  This allows users to login just once when switching between applications.