[midPoint] RE : RE : RE : RE : RE : Namespace problem

[Belleville-Rioux, Vincent]

I see, thanks for pointing that out!

Just for the record, what I am trying to setup is something, should we go ahead with midPoint, that's required for us:

We have about 10k new students each semester and also have about the same number of students that get "offboarded" from some services due to various reasons.

What we're trying to evaluate is how we could automate such state changes so we can do something like :

- 1 month before the start of the semester, all students registered to at least one class will get their account created / activated.  A notification message will be sent.

- 12 months after the end of the last semester where the student had at least one class, the account will be deactivated and a notification message will be sent.

The startDate and endDate are properties we can read from an SQL table (but I'm simulating that with a CSV file for now).  I guess we'll have to reconcile at least once a day because that table will have updates to those dates as students use our online tools to register / unregister themselves to classes.

We should also have the ability to override those values with other dates like "bannedOn" or "temporaryExtension" :

The bannedOn date would make any student which has that date as a non-null value be kept inactive for 7 years from that date.

The temporaryExtension date would make any student account active for 12 months from that date, regardless of the endDate imported from SQL.

So, as you can see, dates are really useful for our use cases.  I understand that this was added rather quickly to 2.2.  Would you suggest we upgrade our test environment to the latest snapshots and try and follow the development from there on?

Thanks,

Vincent

________________________________
De : midpoint-bounces at lists.evolveum.com [midpoint-bounces at lists.evolveum.com] de la part de Radovan Semancik [radovan.semancik at evolveum.com]
Date d'envoi : 30 septembre 2013 09:05
À : midpoint at lists.evolveum.com
Objet : Re: [midPoint] RE : RE : RE : RE : Namespace problem

On 09/27/2013 11:05 PM, Belleville-Rioux, Vincent wrote:
I found the TimeFrom and TimeTo configuration options and I am experimenting a NullPointerException with those...

The time-based mapping constraints were a last-moment addition to version 2.2. It was based on a request from one of our partners that went late in our development cycle. But because it was so important we have added it in the roadmap. However as it was a last-minute change and it was only required to support this for activation mappings the implementation was really done and tested only for this type of mappings. I would be really surprised it it worked in the object template. However I can explore how much work is needed to make it work even for object template:

https://jira.evolveum.com/browse/MID-1623

Please watch this jira issue to see how it goes. Also please note that even though I have optimistically set fix version to 2.2.1 I do not promise that it can fit into this release. I have to explore it first. I will have time for that in next few days.


--

                                           Radovan Semancik
                                          Software Architect
                                             evolveum.com

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.evolveum.com/pipermail/midpoint/attachments/20130930/54b94bfb/attachment.htm>