As you use the In-Application Support Player Configuration utility to change and save settings, it creates a configuration file, writes the necessary lines of code, and saves it to the appropriate location.
If a target application supports help integration, there is a link specifically for that target application on the home page of the utility. There is also a link for SmartHelp options at the bottom of the page. The options on the SmartHelp page apply to all target applications that support SmartHelp, plus all browser-based applications since SmartHelp can be deployed for any application that runs in a browser, except ones that hide the browser toolbar.
Note: When you publish a Player package, only the target application folders that were recorded in the content are included. When you launch the utility, it will only display links to configure these applications. If you want to configure other target applications as well, you can copy other target application folders into the Player package. When the utility detects the additional folders, it will display links for those applications as well. All of the target application folders are stored in the Library in a package called hintconfig. It is in the same location as all of the other folders, that is, /System/Publishing/In-Application Support/<brand>.
As you make changes to the configuration settings and save them, the Activity column on the home page displays information about the date and time the change was made, and the name of the person who made them. You can add a name in the My name is field at the top of the page. If you add your name, or pick your name from the dropdown list, it appears in the Activity column and also on Notes. You can add or change your name on any page. On the home page, you can also change the language of the interface.
To launch the In-Application Support Player Configuration utility (locally):
You can add a note to each option as well as to the configuration file as a whole. These notes are saved as comments in the configuration file. You can use notes to add information about why a change to the configuration was made, and so on.
To add, edit, or delete a note:
Save the Configuration File
If you are launching Configuration Utility from the command file, the configuration file (odcustomurl.js) is saved directly to the appropriate folder within the content folder on the local drive.
Note: If you are not sure that the configuration file was saved correctly, you can retry the save. The Save Configuration page appears, displaying the location where the file was saved. If necessary, you can save the file manually, and then use the Check option to verify that the file is in the correct location.
To save the configuration file locally:
At the bottom of each page of configuration settings, there is a Revert button. This option changes all of the settings on the page back to what they were the last time that the configuration was saved.
To revert the settings:
Reset to Defaults
You can also set options back to the original settings. There is a Reset to Defaults button at the bottom of each page, which sets all the options on the page back to original defaults.
To reset to defaults:
Table of Contents