tag:blogger.com,1999:blog-159518135309222917.post2490789534898146879..comments2024-03-08T01:53:07.559-08:00Comments on How to Siebel?: My top 5 Siebel Mistakes in 2015Unknownnoreply@blogger.comBlogger2125tag:blogger.com,1999:blog-159518135309222917.post-63039623221197524272016-01-26T22:56:54.316-08:002016-01-26T22:56:54.316-08:00Glad you like it Priyanka,
It is important to kn...Glad you like it Priyanka, <br /><br />It is important to know your mistakes, before we can try to correct them. I have actually started adding comments after writing this post. :)Jimhttps://www.blogger.com/profile/12540305358376025735noreply@blogger.comtag:blogger.com,1999:blog-159518135309222917.post-80546545803522775382016-01-25T09:29:40.949-08:002016-01-25T09:29:40.949-08:00A nice read Jim. Thanks for sharing the list.
Lea...A nice read Jim. Thanks for sharing the list.<br /><br />Leaving no comments is very frequent - we use following format for comments<br />Priyana - 25012016 - Project ID/Name - reason for code implementation<br /><br />Other mistakes which I keep making are using profile attributes, and its true that they are very difficult to track back.<br /><br />One additional is - not populating process name property in Workflow so when it ends up in error or exception we can not identify from the logs like which WF has the problem, this one is a very common mistake in my team!!Priyankahttps://www.blogger.com/profile/00275508543726537165noreply@blogger.com