27
Jul
2009
Siebel – Autosave Opportunity data – The concept
by Renuka AnkamRequirement:
System should have capability to automatically save opportunity(RFPs) data in Draft state after a certain interval.
Presumption:
1) The Business Component to be used for the UI applet should not have any required fields at the Table or BC level itself or All the required fields should be pre-defaulted with some unique values.
2) There should not be any dependency of setting the field value from any other Siebel Objects like: Applet level Browser/Server scripts, Bus comp Browser/Server scripts, Application Browser/Server scripts to the target Business Components.
3) The pre-defaulted values of the required fields (if present) will be visible in the applets and the user then can set the field values according to their needs when and wherever required.
4) In our solution, after loading of the applet or after the new record creation a pop up warning message will be thrown to the user after certain duration (say 20 sec) mentioning that the current record will be saved in the database it its current form. The user need to change the field value within this duration, otherwise the record will be saved in the database in its current state.
I have outlined the basic assumptions, as a part of the Case Study. Also, a brief conceptual background is outlined above. I will present the sample code that we used behind the scenes in the following posts. Till then, you can also think of some solutions and start putting them up in this thread.
Somehow, start a timer on the Applet OnLoad event (somehow, i dunno how!!).. and then maybe trigger a write record by fetching the field values.. maybe that could work..
What’s your solution??
[...] is a follow up post on my previous post, Siebel – Autosave Opportunity data – The concept where I introduced the concept and analysis of the following problem statement: “System [...]