[midPoint] Where's the community at?

[Chris Woods]

Hi Jason,

I expect an issue may be employment contracts. If it were up to me I would 
post our samples, but they are not mine to post.

I would like to say a big thank you to you for your samples.

I did a bit of translation outside of work so they can't claim ownership of 
that. That is also a way someone can get involved.

I still hope to be able to release samples at some point but finding *that* 
person who can authorise it is proving elusive at the moment.

Regards,
Chris



Am 2. Juli 2020 19:31:29 schrieb Jason Everling <jeverling at bshp.edu>:
> Why are we still the only one’s that have contributed samples ☹ I know 
> there are some of you out there that have done some unique things with 
> midpoint, show it off, you never know, it could help someone else out!
>
>
>
> Fork it and contribute!
>
> https://github.com/Evolveum/midpoint-samples
>
>
>
> Jason
>
>
>
> From: Jason Everling
> Sent: Thursday, July 2, 2020 12:27 PM
> To: midPoint General Discussion
> Subject: RE: [midPoint] How to blank out user properties?
>
>
>
> Also, should have mentioned, it gets attached to the default template for 
> the object, such as default user template. We also have it set to read-only 
> in the gui so that it doesn’t get modified by anyone, which is something 
> you might also want to do.
>
>
>
> https://github.com/Evolveum/midpoint-samples/blob/master/samples/contrib/bshp/objects/objectTemplates/Default%20User%20Template.xml#L132
>
>
>
> From: Jason Everling
> Sent: Thursday, July 2, 2020 12:22 PM
> To: midPoint General Discussion
> Subject: RE: [midPoint] How to blank out user properties?
>
>
>
> So what I can read from, you want to archive the old value? We do this for 
> various attributes when they are changed, see here, I had added it to the 
> midpoint samples a while back, it will take the old value which was 
> previously set and then add it to a custom schema attribute for archival 
> history, such as a username change, level change, affiliation, etc..
>
>
>
> https://github.com/evolveum/midpoint-samples/blob/master/samples/contrib/bshp/objects/objectTemplates/Includes%20-%20Archiving.xml
>
>
>
> From: Richard Frovarp
> Sent: Thursday, July 2, 2020 11:13 AM
> Subject: [midPoint] How to blank out user properties?
>
>
>
> I'm reading a list of our employees from a DB through a
>
> DatabaseTableConnector resource. As part of that process I'm setting a
>
> custom schema element that is their title. That's fine. However, when
>
> they are no longer employed, they disappear from the database table.
>
>
>
> So I'm trying to blank out the title property, since if they aren't
>
> employed anymore, they don't have a title. We want to keep historic
>
> records, and they may still be a student, which we wouldn't populate a
>
> title.
>
>
>
> How does one go about doing this? It was suggested using an object
>
> template on the deleted situation, but that doesn't appear to be
>
> working.
>
>
>
> Resource:
>
>
>
> <reaction>
>
>  <situation>deleted</situation>
>
>  <synchronize>true</synchronize>
>
>  <action>
>
>    <handlerUri>http://midpoint.evolveum.com/xml/ns/public/model/action
>
> -3#unlink</handlerUri>;
>
>  </action>
>
>  <objectTemplateRef oid="5b23b0d3-0740-47a1-932d-c5a4ab513bc4" />
>
> </reaction>
>
>
>
> User Template:
>
>
>
> <mapping>
>
>  <description>Clean out department</description>
>
>  <strength>strong</strength>
>
>  <target>
>
>    <path>$user/extension/ndsuPrimaryJobTitle</path>
>
>  </target>
>
>  <expression>
>
>    <script>
>
>      <code>null</code>
>
>    </script>
>
>  </expression>
>
> </mapping>
>
>
>
> No errors are thrown, it's just that the title element remains populate
>
> with the last know value when the user is deleted from the resource.
>
>
>
> Thanks,
>
> Richard
>
> _______________________________________________
>
> midPoint mailing list
>
> midPoint at lists.evolveum.com
>
> https://lists.evolveum.com/mailman/listinfo/midpoint

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.evolveum.com/pipermail/midpoint/attachments/20200704/9a097ca8/attachment.htm>