tag:blogger.com,1999:blog-5874979429188093780.post2029414868402143669..comments2024-03-18T06:46:54.352+01:00Comments on Andrej Baranovskij Blog: Explaining Change Indicator Property for ADF BC AttributeAndrej Baranovskijhttp://www.blogger.com/profile/04468230464412457426noreply@blogger.comBlogger4125tag:blogger.com,1999:blog-5874979429188093780.post-35813592350639218132019-03-10T11:58:02.874+01:002019-03-10T11:58:02.874+01:00Honestly unbelievable , we have a use case that Us...Honestly unbelievable , we have a use case that Users can make update on same Row on Different Columns without bothering each other, and really it was not an easy use case with default Change indicator on Row Level .<br />but with your post life became so easy, the user can be notified about others' change during commit and they still have the ability to commit their work while they are checking others change.<br /><br />Thank you very much for such straight forward solution for a difficult use-case .Ubaihttps://www.blogger.com/profile/04150305786245300819noreply@blogger.comtag:blogger.com,1999:blog-5874979429188093780.post-43543240766614853632014-02-23T07:06:00.248+01:002014-02-23T07:06:00.248+01:00super andresuper andreAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-5874979429188093780.post-68051803311607478822014-02-20T16:10:48.363+01:002014-02-20T16:10:48.363+01:00Hi,
Ok, here I'm using change indicator for d...Hi,<br /><br />Ok, here I'm using change indicator for different purpose.<br /><br />Your case sounds like ADF bug. Keep in mind, this is not always possible to find one single change indicator in EO.<br /><br />I think better is to override EO lock method and in case of exception, catch it and try to lock again.<br /><br />Regards,<br />AndrejusAndrej Baranovskijhttps://www.blogger.com/profile/04468230464412457426noreply@blogger.comtag:blogger.com,1999:blog-5874979429188093780.post-72046764997077403102014-02-20T15:58:42.399+01:002014-02-20T15:58:42.399+01:00hi
This is important to avoid possible data corru...hi<br /><br />This is important to avoid possible data corruption.<br /><br />see als "ADF Code Guidelines - include new change indicator mandatory recommendation?"<br />at https://java.net/jira/browse/ADFEMG-151<br /><br />"When an entity object is updated concurrently by more than one user and one of those users loses affinity with their application module during the update, it is possible to experience data corruption if a change indicator has not been defined for the entity object. ..... To avoid this type of scenario, define a change indicator attribute for all entity objects"<br /><br />regards<br />Jan VerveckenAnonymousnoreply@blogger.com