There are a number of ways the M-Files connector can be configured depending on the user requirement. It can be configured as a job for each class or as a user selectable class during processing. The later has some advantages but also some limitations. If you want a user to be able to select a document class during processing then you would only be able to assign properties that are relevant for any classes that are going to be selected by the user. Setting up a job per class means you can assign all the properties and customize the job to be exactly how you need it. Essentially, the user still chooses the class but it is done when they select the job not when the are processing the batch.
The M-Files "Lookup Value" field is dependant on the property it is assigned to within the connector settings. It is only relevant for some types of properties but, for example, if you assigned the zone to a list property in M-Files then it would display the fixed list of values for the user to select from during processing. If you want to use more than 1 M-Files property that has a list (or a lookup of some sort) then you would need to add a zone for each property and assign each within the connector settings. Obviously M-Files fields that are simple text or date values would typically just be created as OCR or KFI type zones.
M-Files is a complex system and it can take a little bit to get your head around classes, class types, class groups, properties etc. But, once you have, it is a powerful solution and Umango is a great on-ramp for scanning and processing documents directly into it.
Link to this article http://umango.com/KB?article=97