Table Of Contents
Customizing the Cisco MeetingPlace for Outlook Scheduling Form
About Customizing the Scheduling Form
Special Requirements
Available Tags
Customizing the Cisco MeetingPlace for Outlook Scheduling Form
The Cisco MeetingPlace for Outlook scheduling form (mpolschedule.htm) allows you to customize the information displayed in the MeetingPlace tab. This form resides in drive>:\Latitude\mpweb\template.
Customizing the mpolschedule.htm form requires proficiency with HTML and Java Script. It is assumed that you are familiar with these before you attempt to customize the mpolschedule.htm form.
This appendix is provided for informational purposes only. Cisco Systems does not support customizations performed by non-Cisco MeetingPlace personnel. Consult with your MeetingPlace support representative for information about MeetingPlace Professional Services. Professional Services are not part of your support contract and are billed on a time and materials basis. For information, contact your support representative. See Obtaining Technical Assistance, page x.
Topics in this appendix are:
•About Customizing the Scheduling Form
•Available Tags
About Customizing the Scheduling Form
The mpolschedule.htm template form contains scheduling fields in the form of HTML tags, with all but the most popular commented out. It does not contain all the scheduling fields available to MeetingPlace for Outlook since even commented fields must be downloaded to the MeetingPlace tab each time this tab is selected by users. The mpolschedule.htm form therefore strikes a balance between extensive customizability and usability.
To customize this form, uncomment or comment the various HTML tags as desired.
Caution Before customizing this or any template file, we recommend that you save a copy to the <drive>:\Latitude\MPWeb\mpoutlook directory, in case you need to revert to it or refer to it later.
The figure below is an example of the code found in the mpolschedule.htm file. See the table below for a full list of tags and descriptions.
•Each field is contained in a table row.
•Each table row starts with a tag <tr>
.
•Each table row ends with a tag </tr>
.
•The red line includes the tag that generates the form field.
•The green line sets a flag that indicates that a meeting parameter has been changed so that this information is transmitted to MeetingPlace.
•To comment out a table row, place a start comment tag <!--
before the <tr>
tag.
•End the comment after the end of the table row </tr>
with the end comment tag -->.
•To insert a table row, delete the start comment tag <!--
that appears before the appropriate <tr>
tag and the end comment tag -->
that appears after the appropriate </tr>
tag.
If changes do not appear after modifying this file, try restarting the MeetingPlace Agent Service. In Windows, choose Start > Settings > Control Panel > Services. Right-click MeetingPlace Agent Service and choose Restart.
Special Requirements
Keep the following requirements in mind when customizing the mpolschedule.htm form. You may require the MeetingPlace SDK to properly set up functionality with MeetingPlace for Outlook.
•Make sure that you set the onChange event for each field and tie it to the onMtgChanged JavaScript function.
•Note that the fields are in table rows. Comment out the entire table row <tr>.
•We recommend that you add most of your fields in the Advanced Settings tab. This is another table on the same HTML page.
For more advanced customizations, contact your MeetingPlace support representative about MeetingPlace Professional Services. See Obtaining Technical Assistance, page x.
Available Tags
The MeetingPlace for Outlook scheduling form (mpolschedule.htm) can be customized to include any number of the following tags. Tags are both input and output unless otherwise specified. Output tags can be followed by the display methods of TEXT, FORM, or LIST as follows:
•TEXT returns the value of the data.
•FORM returns the data in a form or table element. If the field is not modifiable, it is returned in read-only format.
•LIST returns an unnumbered list.
Not all display methods can be used by all tags.
Tag
|
Description
|
Values
|
Description
|
Year
|
Year for which the meeting is scheduled
|
4 digit year
|
FORM
|
Month
|
Month for which the meeting is scheduled
|
1-12
|
FORM
|
Day
|
Day for which the meeting is scheduled
|
1-31
|
FORM
|
Hour
|
Hour for which the meeting is scheduled
|
1-12
|
FORM
|
Min
|
Minute for which the meeting is scheduled
|
00-59
|
FORM
|
AMPM
|
Time of day for which the meeting is scheduled
|
AM or PM
|
FORM
|
Len
|
Scheduled length of the meeting
|
2-1440 minutes
|
FORM
|
nLoc
|
Number of attendee ports reserved for the meeting
|
2-120
|
FORM
|
MTGID
|
The meeting's vanity ID
|
up to 17 digits
|
FORM
|
fPasswordRequired
|
Whether a meeting is password protected
|
Yes/No
|
FORM
|
C_Password
|
The meeting password
|
ASCII text up to 17 characters
|
FORM
|
NamedIntroduction
|
Whether a meeting has arrival announcements turned on
|
Beep Only, Beep with Name, Silent
|
FORM
|
NamedDisconnect
|
Whether a meeting has departure announcements turned on
|
Beep Only, Beep with Name, Silent
|
FORM
|
fScreenedIntroduction
|
Whether the meeting has screened introductions turned on
|
Yes/No
|
FORM
|
fRecordConference
|
Whether the meeting will be recorded
|
Yes/No
|
FORM
|
DefaultAbility
|
Guest user ability
|
Listener/Speaker
|
FORM
|
TextName
|
The meeting's text name
|
ASCII text up to 17 characters
|
FORM
|
WhoCanListen
|
Who can listen to the meeting recording in MeetingNotes
|
None, Anyone, MeetingPlace Profile Users, Invited MeetingPlace Profile Users
|
FORM
|
MaxAttachments
|
The maximum number of attachments
|
0-30
|
FORM
|
QuickMtgEntry
|
Whether quick meeting entry is allowed
|
Yes/No
|
FORM
|
AutoStartRecord
|
Whether recording starts automatically
|
Yes/No
|
FORM
|
PasswordRequiredOnOD
|
Whether a password is required to outdial
|
Yes/No
|
FORM
|
fDisableRollCall
|
Whether rollcall is disabled
|
Yes/No
|
FORM
|
EntryRestriction
|
Who can attend the meeting
|
None, Anyone, User, Invited User
|
FORM
|
SendNotAboutMtgs
|
Whether to send notification about the meeting
|
Yes/No
|
FORM
|
AutoDistributeAtt
|
Whether to distribute attachments with the meeting notification
|
Yes/No
|
FORM
|
DefNotPriority
|
Default notification priority
|
Low, Medium, High
|
FORM
|
SendAboutMtgChngs
|
Whether to resend notification if the meeting is changed (rescheduled)
|
Yes/No
|
FORM
|
SendInviteListWithNot
|
Whether to send the list of invitees with the notification
|
Yes/No
|
FORM
|
SendMtgPwdWithNot
|
Whether to send the meeting password with the notification
|
Yes/No
|
FORM
|
fRecordpartnames
|
Whether to record attendee names as they join meeting
|
Yes/No
|
FORM
|
Billcode
|
The billing code for the meeting
|
Up to 17 digits
|
FORM
|
MTG_TelephoneNum
|
The telephone number of the MeetingPlace Audio Server
|
The configured telephone number of the server
|
FORM
(output only)
|
C_fAllowGuestView
|
Whether to display the meeting to everyone
|
Yes/No
|
FORM
|
C_SchedEmailAdd
|
The meeting scheduler's e-mail address
|
E-mail address as entered in the profile information
|
FORM
|
C_AlternatePhoneNum1
|
First alternate phone number for the meeting
|
Phone number
|
FORM
|
C_AlternatePhoneNum2
|
Second alternate phone number for the meeting
|
Pphone number
|
FORM
|
C_AlternatePhoneNum3
|
Third alternate phone number for the meeting
|
Phone number
|
FORM
|
C_AltPhoneNumName1
|
Name of the first alternate phone number
|
Alphanumeric text
|
FORM
|
C_AltPhoneNumName2
|
Name of the second alternate phone number
|
Alphanumeric text
|
FORM
|
C_AltPhoneNumName3
|
Name of the third alternate phone number
|
Alphanumeric text
|
FORM
|
C_FlexField
|
Flex field data for the meeting
|
Alphanumeric text
|
FORM
|