Macromedia Flash Lite 1.1 Authoring Guidelines
Trademarks Add Life to the Web, Afterburner, Aftershock, Andromedia, Allaire, Animation PowerPack, Aria, Attain, Authorware, Authorware Star, Backstage, Bright Tiger, Clustercats, ColdFusion, Contribute, Design In Motion, Director, Dream Templates, Dreamweaver, Drumbeat 2000, EDJE, EJIPT, Extreme 3D, Fireworks, Flash, Flash Lite, Flex, Fontographer, FreeHand, Generator, HomeSite, JFusion, JRun, Kawa, Know Your Site, Knowledge Objects, Knowledge Stream, Knowledge Track, LikeMinds, Lingo, Live Effects, MacRecorder Logo and Design, Macromedia, Macromedia Action!, Macromedia Breeze, Macromedia Flash, Macromedia M Logo and Design, Macromedia Spectra, Macromedia xRes Logo and Design, MacroModel, Made with Macromedia, Made with Macromedia Logo and Design, MAGIC Logo and Design, Mediamaker, Movie Critic, Open Sesame!, Roundtrip, Roundtrip HTML, Shockwave, Sitespring, SoundEdit, Titlemaker, UltraDev, Web Design 101, what the web can be, and Xtra are either registered trademarks or trademarks of Macromedia, Inc. and may be registered in the United States or in other jurisdictions including internationally. Other product names, logos, designs, titles, words, or phrases mentioned within this publication may be trademarks, service marks, or trade names of Macromedia, Inc. or other entities and may be registered in certain jurisdictions including internationally. Third-Party Information This guide contains links to third-party websites that are not under the control of Macromedia, and Macromedia is not responsible for the content on any linked site. If you access a third-party website mentioned in this guide, then you do so at your own risk. Macromedia provides these links only as a convenience, and the inclusion of the link does not imply that Macromedia endorses or accepts any responsibility for the content on those third-party sites. Speech compression and decompression technology licensed from Nellymoser, Inc. (www.nellymoser.com). Sorenson Spark video compression and decompression technology licensed from Sorenson Media, Inc. Opera browser Copyright 1995-2002 Opera Software ASA and its suppliers. All rights reserved. Apple Disclaimer APPLE COMPUTER, INC. MAKES NO WARRANTIES, EITHER EXPRESS OR IMPLIED, REGARDING THE ENCLOSED COMPUTER SOFTWARE PACKAGE, ITS MERCHANTABILITY OR ITS FITNESS FOR ANY PARTICULAR PURPOSE. THE EXCLUSION OF IMPLIED WARRANTIES IS NOT PERMITTED BY SOME STATES. THE ABOVE EXCLUSION MAY NOT APPLY TO YOU. THIS WARRANTY PROVIDES YOU WITH SPECIFIC LEGAL RIGHTS. THERE MAY BE OTHER RIGHTS THAT YOU MAY HAVE WHICH VARY FROM STATE TO STATE. Copyright 1997-2004 Macromedia, Inc. All rights reserved. This manual may not be copied, photocopied, reproduced, translated, or converted to any electronic or machine-readable form in whole or in part without prior written approval of Macromedia, Inc. First Edition: June 2004 Macromedia, Inc. 600 Townsend St. San Francisco, CA 94103

CONTENTS

CHAPTER 1: Introduction. 7

generally not a good idea to tween symbols that have alpha levels that are not fully opaque (less than 100%).
Avoid intensive visual effects. These include large masks, extensive motion, alpha blending,
extensive gradients, and complex vectors.
Although animating with ActionScript may produce more desirable results, in general, you
should avoid unnecessary use of ActionScript because it can become processor intensive.
Experiment with combinations of tweens, key frame animations, and ActionScript-driven
movement to produce the most efficient results.
If possible, test animations frequently on your target phones.
Bitmap graphics Macromedia recommends optimizing bitmap graphics to 16 bits before importing them into Flash MX Professional 2004. Doing so reduces Flash Lite movie size and gives you more control over the final output. Also, make sure that bitmaps are imported at the size they need to be in the Flash Lite movie. Using larger than required bitmaps results in higher runtime memory requirements.
Bitmap versus vector graphics Flash Lite generally uses vector graphics to define content, which can tax a phones CPU when rendering complex graphics and animations. In general, the more vectors that are manipulated on the Stage, the more CPU power is required. This is also true for Flash movies delivered on desktop computers. However, a mobile phone is far less powerful than desktop computer, so you should avoid taxing the CPU. When creating content for mobile phones, it is sometimes better to use bitmaps instead of vectors because they require less CPU power to animate. For example, a road map of a large city would have too many complex shapes to scroll and animate well on a mobile phone if it were created as a vector graphic; a bitmap would work much better. Using bitmaps produces larger files than using vector images, so take care during development to find the right balance of CPU versus file size and runtime memory requirements. Because of mobile phones smaller screens, slower data transmission speeds, limited memory, and slower CPU speeds, you should take extra care in planning and testing. If you are using bitmaps, you can set image compression options that reduce your SWF file size.
To set bitmap image compression:
1. Start Flash and create a new document. 2. Select a bitmap in the Library window. 3. Right-click (Windows) or Control-click (Macintosh) the bitmaps icon in the Library window. 4. Select Properties from the options menu. The Bitmap Properties dialog box appears:

Development checklist

When you develop Flash content for mobile phones, make sure to check the following items:
Does the Flash content work? Is the Flash content intuitive and easy to interact with? Does the Flash content load data and SWF files without any problems? Can you optimize the images or rewrite code to further reduce the file size and memory requirements while improving performance?
Are all bitmap images successfully decoded and rendered on the mobile phone?
CHAPTER 3 Working with Sound
This section describes the various aspects of sound in relationship to Macromedia Flash Lite 1.1 for the mobile phones.

Audio formats

Flash Lite 1.1 supports MIDI, MFi, SMAF, uncompressed PCM (or WAV), compressed ADPCM, and compressed MP3 audio formats.

Event sound

Event sound is the ability to play sound independent of the Timeline; any event can be used to trigger an event sound. Event sound data must download completely before it begins playing, and it continues playing until either the end of the sound buffer has been reached or it is explicitly stopped. It is possible to loop event sounds within a SWF file.

Streaming sound

Streaming sounds begin playing as soon as enough data for the first few frames has been downloaded; stream sounds are synchronized to the Timeline for playing on a mobile phone. Flash Lite 1.1 supports uncompressed PCM (or WAV), compressed ADPCM, and compressed MP3 audio formats for streaming sound.

Embedding sound

Because Flash MX Professional 2004 does not natively support certain audio formats such as MIDI or SMAF, you must temporarily substitute a proxy sound in a recognized format such as MP3. You can use options in the Sound Properties dialog box and the Flash Publish Settings dialog box to link the proxy sound file to a MIDI file.
Sound files that have been substituted are displayed in green; blue sound waves are files that havent been substituted. For information on how to substitute sounds in your Flash Lite content, see Chapter 6, Creating Content.

Compound sound

Flash Lite 1.1 provides the ability to encapsulate device-specific sounds of multiple formats into a single tagged data block. This provides content developers with the ability to create a single piece of content that is compatible with multiple devices. As an example, a single Flash movie can contain the same sound represented in both MIDI and MFi formats. This Flash movie can be played back both on a device that supports only MIDI and on a device that supports only MFi, with each device playing back the specific sound format that it natively supports. During content creation, content developers identify the sound files in the formats that they want to bundle together. An external tool (FlashLiteSoundBundler.exe) is available to bundle the identified sound files into one sound data block, to be played when triggered by an event. When the appropriate event is triggered, Flash Lite 1.1 processes this bundled sound data block and plays the sound data in the specific format supported by the device. The sound bundle file generated by the FlashLiteSoundBundler.exe program creates a file with the extension.fls.

The steps to create a Sound Bundle File are:
1. Launch FlashLiteSoundBundler.exe. 2. Drag and drop a sound file to be bundled into the target window.
The FlashLiteSoundBundler.exe allows you to create compound sounds.
Chapter 3: Working with Sound
Note: Right click on this window to trigger the Exit button.
3. Flash Lite 1.1 Compound Information window will launch. 4. Drag and drop the rest of the sound files to be bundled. 5. Click on Save Bundle to save your Sound Bundle File in a specific location.
When the appropriate event is triggered, Flash Player processes this bundled sound data block and plays the appropriate sound data contained in the sound bundle. For information on how to substitute sounds in your Flash Lite content, see Chapter 6, Creating Content.
Adding a Sound Bundle File to a Flash document
With Flash MX Professional 2004, you can include event sounds when authoring documents for playback on mobile devices. The general process is described in this section. For detailed information on authoring for mobile devices, see the Content Development Kits on the Mobile and Devices Development Center at www.macromedia.com/devnet/devices. Flash does not support sound file formats used for mobile devices (such as MIDI and others); when authoring for mobile devices, you must temporarily place a proxy sound in a supported format such as MP3, WAV, or AIFF in the Flash document. The proxy sound in the document is then linked to an external mobile device sound, such as a MIDI file or a Sound Bundle file. During the document publishing process, the proxy sound is replaced with the linked external sound. The SWF file generated contains the external sound or sound bundle data and processes it appropriately for playback on a mobile device. When adding device specific sounds or sound bundles to Flash documents for playback on mobile devices, keep the following in mind:
This feature works with event sounds only. The Effect, Sync, and Edit options are not supported when linking a sound. You must specify an external device sound file for each sound in a document. As with all external files, the device sound file or the sound bundle file must be available during the publishing process but is not needed by the SWF file for playback.

The steps to add a Sound Bundle File to a Flash document are:
1. Import a sound file to the library in the Flash document (File > Import > Import to Library). 2. In the Library panel, right-click (Windows) or Control-click (Macintosh) the sound and select

Properties.

3. In the Device sound text box, enter a path or click the folder icon and browse to the location
where the Sound Bundle File is located. Click OK to close the Property inspector.
4. Add a button instance to the Stage from the Buttons common library (Window > Other
Panels > Common Libraries > Buttons).
5. Add the linked sound to the Hit frame of the button. 6. Open the Publish Settings dialog box (File > Publish Settings), and click the Flash tab.
7. Select Flash Lite 1.1 from the version menu.
8. The SWF file now contains the linked Sound Bundle File. 9. Select Control > Test Movie to test your Flash application. 10. Select File > Publish to save the SWF file that contains the Sound Bundle File created earlier.
CHAPTER 4 ActionScript Enhancements for Flash Lite 1.1
Macromedia Flash Lite 1.1 supports two new ActionScript functions: FSCommand() and FSCommand2(). Many new FSCommand and FSCommand2 commands have been introduced in Flash Lite 1.1 For a complete list of ActionScript expressions supported on mobile phones, see Appendix A, Supported ActionScript.
New ActionScript functions
Almost all of these new ActionScript functions are available only for creating Flash Lite 1.1 content; however, not all of them are applicable to all mobile phones. Be sure to check the functions and commands you plan on using before integrating them with Flash Lite content for specific mobile phones. FSCommand() Flash Lite 1.1 supports the FSCommand() function, which enables Flash Lite content to communicate with Macromedia Flash Player, the host application, and the device hosting the player. FSCommand2() The FSCommand2() function is a new ActionScript function that is supported in Flash Lite 1.1 but is not yet supported in the standard desktop version of Flash Player. The FSCommand2() and FSCommand() provide similar functionality, with the following main differences:

Syntax status = FSCommand2( "ResetSoftKeys ) Return value
Player operation commands
The commands in this section provide the mobile phones memory value to Flash content on the mobile phone. GetFreePlayerMemory() The GetFreePlayerMemory() function returns the amount of memory, in kilobytes, currently available to Flash Lite. This function is executed immediately upon invocation. If this function is not supported, a value of -1 is returned.
Syntax status = FSCommand2( "GetFreePlayerMemory ) Return value
A value of -1 if the function is not supported; otherwise, the amount of memory available, in kilobytes. GetTotalPlayerMemory() The GetTotalPlayerMemory() function returns the total amount of memory, in kilobytes, allocated to Flash Lite. This function is executed immediately upon invocation. If the function is not supported, a value of -1 is returned.
Syntax status = FSCommand2( "GetTotalPlayerMemory ) Return value
A value of -1 if the function is not supported; otherwise, the amount of memory available, in kilobytes.
Launch() This function starts another application on the mobile phone. The name of the application being launched and the parameters to it, separated by commas, are passed in as a single parameter.
Note: This feature is operating-system dependent.
The launch() function is supported only when Flash Lite is running in stand-alone mode. It is not supported when the player is running in the context of another application (for example, as a plug-in to a browser).
Syntax status = FSCommand( "Launch", "application-path,arg1,arg2,.,argn" ) Supported applications
This feature is not supported in all mobile phones. Quit() The Quit() function causes Flash Player to stop playback and exit. It is executed immediately upon invocation. If this function is not supported, a value of -1 is returned. The Quit() function is supported only when Flash Lite is running in stand-alone mode. It is not supported when the player is running in the context of another application (for example, as a plug-in to a browser).
Syntax status = FSCommand2( "Quit ) Return value
A value of -1 if the function not supported.
Platform integration commands
A standard set of commands has been created to get and set platform-specific information. These include information such as current time and date, network status, signal strength, battery level, and so on. The implementations of these commands all rely on either FSCommand or FSCommand2 commands. Date and time The commands in this section provide the mobile phones date and time information to Flash content on the mobile phone. GetDateDay() The GetDateDay() function returns the day of the current date. It is a numeric value (without a leading zero). Valid days are 131.
The GetDateDay() function is executed immediately upon invocation. If this function is not supported, a value of -1 is returned.

Syntax status = FSCommand2( "GetLocaleLongDate, "longdate" ) Return value
A value of -1 if the function is not supported; 0 if its supported. Sample resultant values for longdate:

October 16, October 2004

GetLocaleShortDate() The GetLocaleShortDate() function sets a parameter to a string representing the current date, in abbreviated form, formatted according to the currently defined locale. The parameter is passed in by name. The value returned is a multiple-character, variable-length string. The actual formatting depends on the mobile phone and the locale. The GetLocaleShortDate() function is executed immediately upon invocation. If this function is not supported, a value of -1 is returned.
Syntax status = FSCommand2( "GetLocalShortDate, "shortdate" ) Return value
A value of -1 if the function is not supported; 0 if its supported. Sample resultant values for shortdate:

10/16/2004 16-10-2004

GetLocaleTime() The GetLocaleTime() function sets a parameter to a string representing the current time, formatted according to the currently defined locale. The parameter is passed in by name. The value returned is a multiple-character, variable-length string. The actual formatting depends on the mobile phone and the locale. The GetLocaleTime() function is executed immediately upon invocation. If this function is not supported, a value of -1 is returned.
Syntax status = FSCommand2( "GetLocalTime, "time ) Return value
A value of -1 if the function is not supported; 0 if its supported. Sample resultant values for time:

6:10:44 PM 18:10:44

GetTimeHours() The GetTimeHours() function returns the hour of the current time of day, based on a 24-hour clock. It is a numeric value (without a leading zero). Valid hours are 023. The GetTimeHours() function is executed immediately upon invocation. If this function is not supported, a value of -1 is returned.
Syntax status = FSCommand2( "GetTimeHours ) Return value
A value of -1 if the function is not supported; otherwise, the current hour, returned as a number (0-23). GetTimeMinutes() The GetTimeMinutes() function returns the minute of the current time of day. It is a numeric value (without a leading zero). Valid minutes are 059. The GetTimeMinutes() function is executed immediately upon invocation. If this function is not supported, a value of -1 is returned.

cs: da: de:

Czech. Danish. German. UK or international English. USA English. Spanish. Finnish. French. Hungarian. Italian. Japanese. Korean. Dutch. Norwegian. Polish. Portuguese. Russian.
en-UK: en: es: fi: fr: hu: it: jp: ko: nl: no: pl: pt: ru:

sv: tr: xu:

Swedish. Turkish. The language cannot be determined. Simplified Chinese. Traditional Chinese.

zh-CN: zh-TW:

Device and player identification The commands in this section provide the mobile phones ID and platform information to Flash content on the mobile phone. GetDeviceID() The GetDeviceID() function sets a parameter that represents the unique identifier of the mobile phone (for example, serial number). This function is executed immediately upon invocation. If GetDeviceID() is not supported, a value of -1 is returned.
Syntax status = FSCommand2( "GetDeviceID id ) Return value
This feature is not supported in all mobile phones. GetPlatform() The GetPlatform() function identifies the current platform. The platform broadly describes the class of the mobile phone. For mobile phones with open operating systems, this identifier is typically the name and version of the operating system. The name of the platform is returned in a variable that is passed in by name, in the form of a string. This function is executed immediately upon invocation. If GetPlatform() is not supported, a value of -1 is returned.
Syntax status = FSCommand2( "GetPlatform, platform ) Return value
A value of -1 if the function not supported; 0 if its supported. Sample resultant values for platform:
indicates that the device is a 506i phone. indicates that the device is a FOMA1 phone.
GetDevice() The GetDevice() function identifies the mobile phone on which Flash is running. This identifier is typically the model name. The name of the mobile phone is returned in a variable that is passed in by name. The device identifier is a string. This function is executed immediately upon invocation. If GetDevice() is not supported, a value of -1 is returned.
Syntax status = FSCommand2( "GetDevice, device) Return value

2. For Macintosh:

Copy and paste DeviceMsg.cfg to Macintosh HD::Users:<user name>:Library: Application Support:Macromedia:Flash MX 2004:language:Configuration: The configuration consists of multiple feature lines. Each line starts with a feature tag name followed by an equal sign. Lines starting with "//" are considered to be comments and are not processed. There are two methods to set up a feature line. The first method is to add a double quoted string after the equal sign. When this string is present, that feature is turned on no matter what the original settings of the Test Movie player are. This string added by the user will be displayed in the authoring tool output window to remind the content developer of the platforms on which this feature is not supported. The second method is to put "on" or "off" after the equal sign to turn on/off that feature. A special feature line can also be set up to change the sound order preference when creating content with compound sound data. One example is: {Midi,SMAF_MA2,SMAF_MA3,SMAF_MA5,MFI,MFI_Fujitsu,MFI_Mitsubishi,MFI_NEC, MFI_Panasonic,MFI_Sharp,MFI_Sony} In this example, Midi sound is set to have the highest priority when a compound sound bundle is processed. All the supported device sound formats are listed in this example. Once the user specifies this special feature line in the configuration file, playback of the device sound formats specified in this line will be supported in the test movie player. Sound formats not specified in this line will not be supported in the test movie player. The details of tags that can be specified in the configuration file are explained in the following table:
Tag name AddSound ADPCM PCM Default Value(note) Tag Usages On On On Sound playback is allowed ADPCM sound format is allowed PCM sound format is allowed Notes
Chapter 7: Testing Content

Tag name MIDI SMAF

Default Value(note) Tag Usages On On MIDI sound format is allowed All the SMAF sound format is allowed. capSMAF is set to 1;
This is a generic tag for all SMAF sound formats.

SMAF MA2

MA2 SMAF sound format is This is set to On allowed when the SMAF tag is set to On MA3 SMAF sound format is This is set to On allowed when the SMAF tag is set to On MA5 SMAF sound format is This is set to On allowed when the SMAF tag is set to On Generic Mfi sound format sound is allowed Mfi sound with Fujitsu extension is allowed Mfi sound with Mitsubishi extension is allowed Mfi sound with NEC extension is allowed Mfi sound with Panasonic extension is allowed Mfi sound with Sharp extension is allowed Mfi sound with Sony extension is allowed MP3 sound format is allowed Only one device sound can be played at one time, no mixing allowed When turned on, sound will be played only when it is associated with a key press Stream Sound is supported, _capStreamSound is set to 1. When turned on, only loadVars calls associated with a key press are allowed

continue do. while
Action; executes the statements inside the loop, and then Fully supported evaluates the condition of the loop for as long as the condition is true. Action; creates an instance of a movie clip while the movie is playing. Fully supported

duplicateMovieClip

Description Action; specifies the actions, clauses, arguments, or other conditional to run if the initial if statement returns false. Action; evaluates a condition and specifies the statements to run if the condition in the initial if statement returns false. Comparison operator; compares two expressions for equality and returns true if expression1 is equal to expression2; otherwise, returns false. This action is string specific. The following examples illustrate true and false results for the eq operator:
x =Amy; y=Fred; x eq Amy; // true x eq y; // false

else if

eq (string equal)

eval()

Function; accesses variables. The value of the variable is Fully supported returned. Action; allows the Flash application to communicate with Partially the program hosting Flash Player. supported

fscommand()

ge (string greater than Comparison operator; returns true if the string Fully supported or equal) representation for expression1 is greater than or equal to the string representation for expression2; otherwise, returns false. This action is string specific.
The following examples illustrate true and false results for the ge operator:
x =Amy; y=Fred; x ge y; // false x ge Amy; // true y ge x; // true getProperty()
Function; returns the value of the specified property for the movie clip instance.
Partially supported. (See Supported ActionScript on page 61.) Fully supported

getTimer()

Function; returns the number of milliseconds that have elapsed since the SWF file started playing.

getURL()

Description Action; loads a document from a specific URL into a window or passes variables to another application at a defined URL. When sending variables, specify whether to load variables using a GET or POST method. GET appends the variables to the end of the URL, and is used for small numbers of variables. POST sends the variables in a separate HTTP header and is used for long strings of variables.
Support Partially supported (The URL protocols http, https, mailto, and tel are supported, once per event action.)

gotoAndPlay()

Fully supported Action; sends the playhead to the specified frame in a scene and plays from that frame. If a scene is not specified, the playhead goes to the specified frame in the current scene. Fully supported Action; sends the playhead to the specified frame in a scene and stops it. If no scene is specified, the playhead is sent to the frame in the current scene. Fully supported Comparison operator; returns true if the string representation for expression1 is greater than the string representation for expression2; otherwise, returns false. This action is string specific. Action; evaluates a condition to determine the next action in a movie. If the condition is true, Flash runs the statements that follow. Fully supported

Support Fully supported Fully supported Not supported

stopDrag() String()

Function; returns a string representation of the specified Not supported argument as follows: If x is a Boolean value, the return string is true or false. If x is a number, the return string is a decimal representation of the number. If x is a string, the return string is x. If x is a movie clip, the return value is the target path of the movie clip in slash (/) notation. If x is undefined, the return value is an empty string. String function; extracts part of a string. Action; creates a branching structure for ActionScript statements. The switch action tests a condition and executes statements if the condition returns a value of true. Fully supported Fully supported

substring() switch()

tellTarget()
Action; Can be used to apply instructions to a particular Fully supported Timeline or movie clip. For example, tellTarget() can be assigned to buttons that stop or start movie clips on the Stage or prompt movie clips to jump to a particular frame. Action; turns anti-aliasing on and off in Flash Lite. Anti- Fully supported aliasing smooths the edges of objects but results in slower movie playback. The toggleHighQuality() action affects all movies in Flash Lite. Action; evaluates the expression and displays the results Fully supported in the Output panel when you run the Test Movie command. Action; removes a movie clip from Flash Lite that was previously loaded or created using the loadMovie() or duplicateMovieClip() actions. Action; removes a movie at a specified level from Flash Lite that was previously loaded or created using the loadMovie() action. Fully supported

toggleHighQuality()

trace()

unloadMovie()

unloadMovieNum()

while()

Fully supported Action; runs a statement or series of statements repeatedly in a loop as long as the condition argument is true.
APPENDIX B Supported ActionScript Properties
This appendix lists the Macromedia Flash Lite 1.1 ActionScript properties and points out any exceptions.

FTPS076

FTPS077

FTPS078

FTPS079

FTPS080

FTPS081

FTPS082

ActionScript processing Flash Player detected an ActionScript processing error found. ActionScript error. The warning message contains the ActionScript command that caused the processing command. error. Invalid entry found in configuration file: Line line number. Configuration file found. Flash Player detected an invalid entry on line line number in the configuration file. Flash Player detected a cofiguration file.

FTPS083

FTPS084
Message Identifier Message FTPS085
loadVariables requests are allowed only when associated with a keypress, not supported on these platforms: platform name. loadMovie requests are
Explanation Flash Player detected a loadVariables call associated with a keypress. It will be executed, but it is not supported on certain platforms. This message is shown only when platform strings are specified in corresponding flags in the configuration file. Flash Player detected a loadMovie call associated with a keypress. It will be executed, but it is not supported on certain platforms. This message is shown only when platform strings are specified in corresponding flags in the configuration file. Flash Player detected a getURL() call associated with a keypress. It will be executed, but it is not supported on certain platforms. This message is shown only when platform strings are specified in corresponding flags in the configuration file. Flash Player detected an FSCommand() call associated with a keypress. It will be executed but it is not supported on certain platforms. This message is shown only when platform strings are specified in corresponding flags in the configuration file. A loadVariables call is detected by Flash Player. The call is allowed on a frame or when associated with a keypress, but this feature is not supported on certain platforms. This message is shown only when platform strings are specified in corresponding flags in the configuration file.

FTPS086