Hi all, another note:
Sync process include many operations for example "create","assign","link","unlink", etc... but into notification configuration we find only "create","update","delete","none". How to intercept a failure/success during "assing", or during an operation different from ["create","update","delete","none"]? At the moment the only workaround we have thought is configure it manually in content.xml. Kind regards. [http://www.intesys.it/firme/logo_intesys.jpg] Nicola Baiocco | Software Developer Intesys - Via Roveggia 122 A - 37136 Verona Tel. 045 503663 | Fax 045 503604 [email protected] www.intesys.it<http://www.intesys.it> [Great Place to Work]<http://www.intesys.it/Partecipazione-dei-dipendenti/> [Sito a impatto zero] <http://www.intesys.it/Sostenibilita-Ambientale/> Le informazioni contenute nella presente e-mail e nei suoi allegati potrebbero essere confidenziali/riservate e sono dirette unicamente ai destinatari sopra indicati. In caso di ricezione da parte di persona diversa è vietato qualunque tipo di divulgazione o copia anche parziale. Chi riceva questo messaggio per errore è pregato di inoltrarlo al mittente e di cancellare questa e-mail. This e-mail and its attachments may contain confidential/reserved information and is intended only for the use of the address(es) named above. If the reader of this message is not the intended recipient of this message, please note that distribution or copying of this communication is forbidden. Anyone who receives this communication in error should return it immediately to the sender and delete the message. Da: Nicola Baiocco [mailto:[email protected]] Inviato: martedì 17 febbraio 2015 14:40 A: [email protected] Oggetto: Syncope 1.2.1 Notification Hi all, We have a syncTask that sync from AD and propagates to an external resource, we've tried to configure some notifications to get propagation error (failure). Our notification configuration: 1. Notification with custom template for events: [PropagationTask]:[membership]:[EXTERNAL_RESOURCE]:[create]:[FAILURE] [PropagationTask]:[membership]:[EXTERNAL _RESOURCE]:[delete]:[FAILURE] [PropagationTask]:[membership]:[ EXTERNAL _RESOURCE]:[none]:[FAILURE] [PropagationTask]:[membership]:[ EXTERNAL _RESOURCE]:[update]:[FAILURE] [PropagationTask]:[role]:[EXTERNAL _RESOURCE]:[create]:[FAILURE] [PropagationTask]:[role]:[EXTERNAL _RESOURCE]:[delete]:[FAILURE] [PropagationTask]:[role]:[EXTERNAL _RESOURCE]:[none]:[FAILURE] [PropagationTask]:[role]:[EXTERNAL _RESOURCE]:[update]:[FAILURE] [PropagationTask]:[user]:[EXTERNAL _RESOURCE]:[create]:[FAILURE] [PropagationTask]:[user]:[ EXTERNAL _RESOURCE]:[delete]:[FAILURE] [PropagationTask]:[user]:[EXTERNAL _RESOURCE]:[none]:[FAILURE] [PropagationTask]:[user]:[EXTERNAL _RESOURCE]:[update]:[FAILURE] 2. notificationjob.cronExpression every 2 seconds; During tests we have broken authentication config used by connector for propagation (so every propagation fails), but nothing happens, we've checked "task" table but seems that no notification tasks were stored. Have you got some hint? Thank in advance. Kind regards. [http://www.intesys.it/firme/logo_intesys.jpg] Nicola Baiocco | Software Developer Intesys - Via Roveggia 122 A - 37136 Verona Tel. 045 503663 | Fax 045 503604 [email protected]<mailto:[email protected]> www.intesys.it<http://www.intesys.it> [Great Place to Work]<http://www.intesys.it/Partecipazione-dei-dipendenti/> [Sito a impatto zero] <http://www.intesys.it/Sostenibilita-Ambientale/> Le informazioni contenute nella presente e-mail e nei suoi allegati potrebbero essere confidenziali/riservate e sono dirette unicamente ai destinatari sopra indicati. In caso di ricezione da parte di persona diversa è vietato qualunque tipo di divulgazione o copia anche parziale. Chi riceva questo messaggio per errore è pregato di inoltrarlo al mittente e di cancellare questa e-mail. This e-mail and its attachments may contain confidential/reserved information and is intended only for the use of the address(es) named above. If the reader of this message is not the intended recipient of this message, please note that distribution or copying of this communication is forbidden. Anyone who receives this communication in error should return it immediately to the sender and delete the message.
