The below table illustrates the sequence in which MIMIX checks DLO entries for a match.
Search Order |
Folder Path |
Document Name |
Owner |
---|---|---|---|
1 |
Exact |
Exact |
Exact |
2 |
Exact |
Exact |
*ALL |
3 |
Exact |
Generic* |
Exact |
4 |
Exact |
Generic* |
*ALL |
5 |
Exact |
*ALL |
Exact |
6 |
Exact |
*ALL |
*ALL |
7 |
Generic* |
Exact |
Exact |
8 |
Generic* |
Exact |
*ALL |
9 |
Generic* |
Generic* |
Exact |
10 |
Generic* |
Generic* |
*ALL |
11 |
Generic* |
*ALL |
Exact |
12 |
Generic* |
*ALL |
*ALL |
13 |
*ALL |
Exact |
Exact |
14 |
*ALL |
Exact |
*ALL |
15 |
*ALL |
Generic* |
Exact |
16 |
*ALL |
Generic* |
*ALL |
17 |
*ALL |
*ALL |
Exact |
18 |
*ALL |
*ALL |
*ALL |
Document example - Table 24 illustrates some sample data group DLO entries. For example, a transaction for any document in a folder named FINANCE would be blocked from replication because it matches entry 6. A transaction for document ACCOUNTS in FINANCE1 owned by JONESB would be replicated because it matches entry 4. If SMITHA owned ACCOUNTS in FINANCE1, the transaction would be blocked by entry 3. Likewise, documents LEDGER.JUL and LEDGER.AUG in FINANCE1 would be blocked by entry 2 and document PAYROLL in FINANCE1 would be blocked by entry 1. A transaction for any document in FINANCE2 would be blocked by entry 6. However, transactions for documents in FINANCE2/Q1, or in a child folder of that path, such as FINANCE2/Q1/FEB, would be replicated because of entry 5.
Entry |
Folder Path |
Document |
Owner |
Process Type |
---|---|---|---|---|
1 |
FINANCE1 |
PAYROLL |
*ALL |
*EXCLD |
2 |
FINANCE1 |
LEDGER* |
*ALL |
*EXCLD |
3 |
FINANCE1 |
*ALL |
SMITHA |
*EXCLD |
4 |
FINANCE1 |
*ALL |
*ALL |
*INCLD |
5 |
FINANCE2/Q1 |
*ALL |
*ALL |
*INCLD |
6 |
FIN* |
*ALL |
*ALL |
*EXCLD |