<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p>Hello Ramiji,</p>
<p><br>
</p>
<p>the feature you're trying to use, i.e. approving changes that
were detected by LiveSync, has not been implemented yet.</p>
<p><br>
</p>
<p>We first implemented the most common scenario: approving
explicitly requested changes (submitted via GUI, Java, SOAP or
REST API).</p>
<p><br>
</p>
<p>What you need is probably not that hard to implement. What needs
to be clarified is exact expected behavior - for example, should
we consider changes detected only by LiveSync, or by
reconciliation as well?</p>
<p> a) If by LiveSync only: what with changes that would get lost
(somehow - it might happen for reasons internal or external to
midPoint). Normally, such changes are covered by reconciliation.
If we would forbid reconciliation, we would have to have another
mechanism for recovering such forgotten/lost changes.<br>
</p>
<p> b) If by reconciliation as well: what with changes that would
be rejected? They would trigger new approval process at each
reconciliation task run.<br>
</p>
<p><br>
</p>
<p>Best regards,</p>
<p>Pavol<br>
</p>
<br>
<div class="moz-cite-prefix">On 05.05.2016 15:07, Rijndaal Ramiji
wrote:<br>
</div>
<blockquote
cite="mid:VI1PR06MB13126C93363DAFC4C6062F1DB77C0@VI1PR06MB1312.eurprd06.prod.outlook.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<style type="text/css" style="display:none;"><!-- P {margin-top:0;margin-bottom:0;} --></style>
<div id="divtagdefaultwrapper"
style="font-size:12pt;color:#000000;background-color:#FFFFFF;font-family:Calibri,Arial,Helvetica,sans-serif;">
<p>Hi.<br>
<br>
I'm currently studying workflows, and my admin project would
like to use it in the LiveSync provisioning process.<br>
<br>
We currently have an HR resource that has a livesync task.<br>
An object template for the sync event of HR can create the CN
for AD and stores it in $user/extension/CN.<br>
<br>
Finally, My ActiveDirectory resource has on outbound
mapping of $user/extension/CN in icfs:name.<br>
<br>
It works like a charm! (this product is quite of amazing ;) )</p>
<p><br>
</p>
<p>Btw, I'm reading about workflows of approval and we would
like to make the liveSync process of provisioning to be
overlooked by a workflow.<br>
<br>
I have configured the workflow process, and it works for,
example, creation of an user from MidPoint "new user".<br>
<br>
Before the effective provisioning on AD, it ask to the admin
to reject or approve the request of creation.<br>
<br>
This workflow sadly, seems to not work with the automatic
creation of the account from the "unmatched" reaction...<br>
<br>
Is this a known bug , <span style="font-family: Calibri,
Arial, Helvetica, sans-serif, 'Apple Color Emoji', 'Segoe UI
Emoji', NotoColorEmoji, 'Segoe UI Symbol', 'Android Emoji',
EmojiSymbols; font-size: 16px;">should </span>this be the
exact flow or maybe I have made something wrong?<br>
<span style="font-size: 12pt;"><br>
Thank you all! </span></p>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
midPoint mailing list
<a class="moz-txt-link-abbreviated" href="mailto:midPoint@lists.evolveum.com">midPoint@lists.evolveum.com</a>
<a class="moz-txt-link-freetext" href="http://lists.evolveum.com/mailman/listinfo/midpoint">http://lists.evolveum.com/mailman/listinfo/midpoint</a>
</pre>
</blockquote>
<br>
</body>
</html>