If you just start Web Learn and learn a page it will only
bring in objects that map to a Certify Class and are "enabled". If the user wants to see objects that are not "enabled", simply uncheck "Learn Enabled
Objects Only" in Web Learn's Options menu before learning the page.
These objects will be shown Web learn as "disabled" but that can
be changed by right-clicking it in the learn tree and choosing "Toggle
Enabled" as long as the object maps to a Certify Class.
If the object do not map to a Certify Class then the only way
to add it in the map is to use Web Learn's Touch-Learn. If an object is Touch-Learned, Web Learn will map it to a
htmlLink if it does not map to a Certify Class.
This is because it is assumed that if a user adds an
object through Touch-Learn they must want to test it.
Touch-Learned objects will also have a menu that lets the
user change the Certify Class.
An alternative way to get the objects into the map is to assign the object to a specific Certify class and always make them "enabled". To do this, the user can create their own config from scratch or by
starting with Factory.cfg as a template, which can be done from the
Configuration Manager (accessible from Web Learn's File menu). A custom config is
persisted in a local file and must then be distributed to any client the user
wants this configuration on.
In Web Learn's Config Manager the custom
configuration can be set as the "default config" and this configuration will be
pulled into memory when starting Web Learn instead of the factory config.
In Certify 8.5.0, Incremental Learn for Web uses the default configuration in Web Learn. The attributes of Web objects added via Incremental learn driven from the CertifyWebLearn configuration file.