<div dir="ltr">he couldn't use an OR statement because at a given time a person can have 2 records, just like in our case, you can have a faculty/staff member that are currently enrolled in courses thus are also a student. So there is 2 unique records using different identifiers. Intents solved that for us but in a larger institution it can become quite complex as noted in the wiki,
<a href="https://wiki.evolveum.com/display/midPoint/Synchronization+Sorter">https://wiki.evolveum.com/display/midPoint/Synchronization+Sorter</a> <div> <br clear="all"><div><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><br></div></div></div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Apr 23, 2019 at 9:01 AM Wojciech Staszewski <<a href="mailto:wojciech.staszewski@diagnostyka.pl">wojciech.staszewski@diagnostyka.pl</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hello Martin!<br>
What about single correlation rule with "OR" and "AND" combination?<br>
<br>
<br>
<q:or xmlns:org="<a href="http://midpoint.evolveum.com/xml/ns/public/common/org-3" rel="noreferrer" target="_blank">http://midpoint.evolveum.com/xml/ns/public/common/org-3</a>"><br>
<q:equal><br>
<q:matching>polyStringNorm</q:matching><br>
<q:path>c:employeeNumber</q:path><br>
<expression><br>
<path>declare namespace ri='<a href="http://midpoint.evolveum.com/xml/ns/public/resource/instance-3" rel="noreferrer" target="_blank">http://midpoint.evolveum.com/xml/ns/public/resource/instance-3</a>';<br>
$account/attributes/ri:employeeNumber</path><br>
</expression><br>
</q:equal><br>
<q:and><br>
<q:equal><br>
<q:matching>polyStringNorm</q:matching><br>
<q:path>c:givenName</q:path><br>
<expression><br>
<path>declare namespace ri='<a href="http://midpoint.evolveum.com/xml/ns/public/resource/instance-3" rel="noreferrer" target="_blank">http://midpoint.evolveum.com/xml/ns/public/resource/instance-3</a>';<br>
$account/attributes/ri:firstname</path><br>
</expression><br>
</q:equal><br>
<q:equal><br>
<q:matching>polyStringNorm</q:matching><br>
<q:path>c:familyName</q:path><br>
<expression><br>
<path>declare namespace ri='<a href="http://midpoint.evolveum.com/xml/ns/public/resource/instance-3" rel="noreferrer" target="_blank">http://midpoint.evolveum.com/xml/ns/public/resource/instance-3</a>';<br>
$account/attributes/ri:surname</path><br>
</expression><br>
</q:equal><br>
</q:and><br>
</q:or><br>
<br>
Cheers!<br>
WS<br>
<br>
W dniu 23.04.2019 o 15:25, Ivan Noris pisze:<br>
> Hi David,<br>
> <br>
> you may need this: <a href="https://wiki.evolveum.com/display/midPoint/Synchronization+Sorter" rel="noreferrer" target="_blank">https://wiki.evolveum.com/display/midPoint/Synchronization+Sorter</a><br>
> <br>
> Best regards,<br>
> <br>
> Ivan<br>
> <br>
> On 23. 4. 2019 15:15, Martin, David (DIT) wrote:<br>
>> I'm new to midPoint, just doing a Trial/PoC (v3.9). Currently I have 2 database resources (one is HR and the other Student Records) configured and have successfully imported accounts and generated Users. The Correlation rule was a simple match on Employee Number / Student ID (I added a schema extension for Student ID).<br>
>><br>
>><br>
>> Now I am trying to model a more complex Correlation where it checks first based on Employee Number / Student ID and if that isn't found then checks based on Given Name and Family Name. The scenario is that a person may be both staff and student. The ID Number should be the same in both systems but it isn't always picked up, hence the second check.<br>
>><br>
>><br>
>> At the moment I have tried to set them up as separate Correlation rules within the Synchronization on the Resource, but it seems if the first Correlation finds no matches it ignores the second rule . Conversely if the first rule finds a match it will also run the second rule. Ultimately I want to have multiple rules with different assurance levels. If a high assurance rule finds a single match we can stop and linking could occur. Other rules would only produce possible matches and require manual review and correlation.<br>
>><br>
>><br>
>> The system allows multiple Correlation rules, but I couldn't find any documentation or examples that explain how to use these. Any thoughts on how to approach this or documentation I've missed?<br>
>><br>
>><br>
>> thanks<br>
>><br>
>> David<br>
>><br>
>> [Charles Sturt University]<<a href="http://www.csu.edu.au/" rel="noreferrer" target="_blank">http://www.csu.edu.au/</a>><br>
>><br>
>> | ALBURY-WODONGA | BATHURST | CANBERRA | DUBBO | GOULBURN | MELBOURNE | ORANGE | PORT MACQUARIE | SYDNEY | WAGGA WAGGA |<br>
>><br>
>> ________________________________<br>
>> LEGAL NOTICE<br>
>> This email (and any attachment) is confidential and is intended for the use of the addressee(s) only. If you are not the intended recipient of this email, you must not copy, distribute, take any action in reliance on it or disclose it to anyone. Any confidentiality is not waived or lost by reason of mistaken delivery. Email should be checked for viruses and defects before opening. Charles Sturt University (CSU) does not accept liability for viruses or any consequence which arise as a result of this email transmission. Email communications with CSU may be subject to automated email filtering, which could result in the delay or deletion of a legitimate email before it is read at CSU. The views expressed in this email are not necessarily those of CSU.<br>
>><br>
>> Charles Sturt University in Australia<<a href="http://www.csu.edu.au" rel="noreferrer" target="_blank">http://www.csu.edu.au</a>> The Grange Chancellery, Panorama Avenue, Bathurst NSW Australia 2795 (ABN: 83 878 708 551; CRICOS Provider Number: 00005F (National)). TEQSA Provider Number: PV12018<br>
>><br>
>> Consider the environment before printing this email.<br>
>><br>
>><br>
>> _______________________________________________<br>
>> midPoint mailing list<br>
>> <a href="mailto:midPoint@lists.evolveum.com" target="_blank">midPoint@lists.evolveum.com</a><br>
>> <a href="http://lists.evolveum.com/mailman/listinfo/midpoint" rel="noreferrer" target="_blank">http://lists.evolveum.com/mailman/listinfo/midpoint</a><br>
> <br>
> -- <br>
> Ivan Noris<br>
> Senior Identity Engineer<br>
> <a href="http://evolveum.com" rel="noreferrer" target="_blank">evolveum.com</a><br>
> <br>
> <br>
> _______________________________________________<br>
> midPoint mailing list<br>
> <a href="mailto:midPoint@lists.evolveum.com" target="_blank">midPoint@lists.evolveum.com</a><br>
> <a href="http://lists.evolveum.com/mailman/listinfo/midpoint" rel="noreferrer" target="_blank">http://lists.evolveum.com/mailman/listinfo/midpoint</a><br>
> <br>
<br>
-- <br>
Wojciech Staszewski<br>
Administrator Systemów Sieciowych<br>
tel. kom: 663 680 236<br>
<a href="http://www.diagnostyka.pl" rel="noreferrer" target="_blank">www.diagnostyka.pl</a><br>
Diagnostyka Sp. z o. o.<br>
ul. Prof. M. Życzkowskiego 16, 31-864 Kraków<br>
Numer KRS: 0000381559 (Sąd Rejonowy dla Krakowa-Śródmieścia w Krakowie, XI Wydział Gospodarczy KRS)<br>
NIP: 675-12-65-009; REGON: 356366975<br>
Kapitał zakładowy: 33 756 500 zł.<br>
<br>
Pomyśl o środowisku zanim wydrukujesz ten e-mail.<br>
_______________________________________________<br>
midPoint mailing list<br>
<a href="mailto:midPoint@lists.evolveum.com" target="_blank">midPoint@lists.evolveum.com</a><br>
<a href="http://lists.evolveum.com/mailman/listinfo/midpoint" rel="noreferrer" target="_blank">http://lists.evolveum.com/mailman/listinfo/midpoint</a><br>
</blockquote></div>