RE: Question regarding upcoming PullAction changes in version 2.0.7

2017-12-07 Thread Mikael Ekblom
. joulukuuta 2017 11.40 To: user@syncope.apache.org Subject: Re: Question regarding upcoming PullAction changes in version 2.0.7 Hi Mikael, using pullUtils to get internal matches (if found) is exactly the best-practice for preprocess() to get internal data, congrats :-) Regards. On 07/12/2017

Re: Question regarding upcoming PullAction changes in version 2.0.7

2017-12-07 Thread Francesco Chicchiriccò
:* tiistai 5. joulukuuta 2017 10.08 *To:* user@syncope.apache.org *Subject:* Re: Question regarding upcoming PullAction changes in version 2.0.7 Hi Mikael, the SyncDelta processing was modified by SYNCOPE-1234 [1]. The new preprocess() method is invoked before any other method of the provided

RE: Question regarding upcoming PullAction changes in version 2.0.7

2017-12-07 Thread Mikael Ekblom
467 Mobil: +358 207 699 467 From: Francesco Chicchiriccò [mailto:ilgro...@apache.org] Sent: tiistai 5. joulukuuta 2017 10.08 To: user@syncope.apache.org Subject: Re: Question regarding upcoming PullAction changes in version 2.0.7 Hi Mikael, the SyncDelta processing was modified by SYNCOPE-1234 [1

Re: Question regarding upcoming PullAction changes in version 2.0.7

2017-12-05 Thread Francesco Chicchiriccò
Hi Mikael, the SyncDelta processing was modified by SYNCOPE-1234 [1]. The new preprocess() method is invoked before any other method of the provided implementation, giving clear chance to alter the data coming from underlying resource prior to any other Syncope-side consideration. Before [1]

Question regarding upcoming PullAction changes in version 2.0.7

2017-12-04 Thread Mikael Ekblom
Hi, I have one question: in version 2.0.7 I have noticed that you have added a preprocess function to the default pull actions class. We would like to alter the syncdelta in certain cases ie the user should be kept as enabled (ie. __ENABLED__ set to true) as the user can have two different