scheduler

Hello John,
you can enter ir.cron entry by demo data.

I disagree with this thing.

Is open erp running 24*7?
Europe :its 9 PM , Aus :its 6 AM, Ind : 1 AM, USA : 3 PM.

Please think for scheduler, 2 readonly fields suck!

It has been changed in trunk.

Hello John Daniel,

I agree with you, but if you observe the Schedular Functionalities closely you will get the idea, to create a scedular we need to write a method in to the model which is qite simplar to this one 'def _check(self, cr, uid, ids=False, context={}):'

if you observer closely ids=False, you will not get anythings here, and if we make an that 2 fields open for the editiing, Function, and Argument you can not defin or Write the Function, manually while running the server.

and so, when you going to define the function define the schedular, in xml file which is not a demo data,
<record id="ir_cron_crm_action" model="ir.cron">
            <field name="name">Check cases rules</field>
            <field name="interval_number">1</field>
            <field name="interval_type">hours</field>
            <field name="numbercall">-1</field>
            <field eval="False" name="doall"/>
            <field eval="'crm.case.rule'" name="model"/>
            <field eval="'_check'" name="function"/>
            <field eval="'()'" name="args"/>
        </record>

and initially if you do not want that it will start automatically after loading the module, make if inactive
 <field eval="False" name="active"/>

you can see that if you can see your schedular in the List even if you make this InActive, which for other record Inactive works differently.

so as a colclution its better to define the schedular in xml file as a dml data and load by upgrading the server. as when done in the crm module

Sorry mga(Open ERP),

But it was difficult for me to understand few english words(I don't know whether they are grammatical mistakes or they are techie words). Might be, these are against Britishers:)

But I am happy with what Fabein(OpenERP) said.

I will wait for next release.

Chao.

Hello John Daniel,

We appreciate your interest but it would be unfair to put comments like this.

Undoubtedly,the proper care will be taken but I would prefer that you only concern about the theme of the question(the aim).

Sorry for interrupting.

Close the question too.

Thank you.

hi Jay(Openerp),

i am sorry for the comments. i was not happy with what mga(openerp) had written.
so, the frustration came out.

 i thank you and Fabien for replies.

txs.