Siebel behaves weirdly. This is the statement that i think most of the people would agree to. And with experience, you will know a lot of things written in theory/bookshelf will not behave in the same way practically. Naming a few like activating a field, enabling a method etc. The list goes on and on and on.
Out of many one such instance i have faced recently, when i have created a runtime event and the same was not reflecting, even when i have reloaded the RTE couple of times.
Keep a note to beginners here that whenever you create or update a Runtime Event or its related Action Sets, you need to do Reload Runtime Events which is there in the Menu. This is required in the same way when you need to do a Clear Cache after creating or updating an LOV to get it reflected in the component.
Now as i said even after i have done the Reload RTE couple of times, when i was testing the RTE change was not reflecting. As part of the troubleshooting i have tried to launch a dedicated client, and to my surprise, RTE was getting reflected.
This discovery indicated that somehow the component is not taking the effect of newly created RTE. Now if you go with theory this should not be the case.
Resolution: Now i have witnessed this issue not once but twice. How to resolve it? Bounce the component and chances are more likely that issue will get resolve and RTE will be reflected in component.
For the benefit of the user, i have made a thumb rule, if something inexplicable happens in siebel, bounce the component if you could to avoid hours of frustration. Happy Learning !!!
