How to classify applications in Migrator for Notes to SharePoint

Hi. My name is Randy Rempel, and I'm a Senior Product Manager. Today, I'm going to briefly review application classification in Migrator for Notes to SharePoint. I previously talked about classifications in the database discovery video and the introduction to measuring application complexity video. Classification in MNSP is based on a set of rules, which appear as nodes under the classification rules node. There are two types of classification-- technical and business. MNSP includes a default set of classes. You can edit these classes, and add your own classes too. The technical classes are generally used to identify an application type. You can see the default classifications listed in the view. The rules typically reference a template name to identify the classification. The business classes are generally used to identify the business application group that the application belongs to. For example, the application may be a document library, but it is used by the legal department. Each technical and business class includes a set of rules that must match for a particular database in order for that database to be recognized as a member of the class. Each rule may specify that class members should be recognized by folder path, file name, template name, database title, database category, a database manager being listed in the database ACL, any user being listed in the ACL, a design element be used, or membership in a particular application type. A rule can contain one or more matching values, and regular expressions may optionally be used. If a class contains more than one rule, the user may specify an and or or relationship. Rules are prioritized, applied in a predefined order. The first one that matches is used and subsequent rules are not tested. The order of the rules can be changed within a classification. The actual classification process occurs as soon as databases are discovered, when database information is retrieved from the repository or when the user refreshes that database view. If you have updated or created new classification rules, refreshing the database view will update the classes of all the databases using the current classification rules. The technical classification and business classification are competed independently. The technical and business classifications are visible by default in this view. You can also apply the class rules to an individual or multiple database records. You can manually assign a technical class, and then a business class. Finally, you can create a new technical class from a single selected database record. You can lock a class to prevent refreshing it in the future. Let's create a new business classification called Testing. I also want to set the disposition value when this class is set-- that will save me an extra step. The new business class will be run on all of the databases. However, changes will not be made to any of the records that have a lock. Also, the disposition will not be applied automatically. I need to run the classification process again. Here, you can see that the disposition value has not changed. Now the assignment of the disposition will be based on the business class when I run this rule this time. Here, you can see that the disposition value has changed to "leave in place." I can also set the disposition value manually, just like I set the technical and business classes.