[ADD] connector_voicent_helpdesk_ticket

[murtuzasaleh]

Voicent Helpdesk Ticket Connector

Odoo Helpdesk App does not provide an automated way to trigger phone calls when a ticket reaches a specific stage in the process.

For companies with a large number of tickets or when a ticket impacts many people, calling everyone one by one is a time-consuming option.

This module aims to automate calls to a customer or impacted third parties when a ticket reaches a specific stage.

[murtuzasaleh]

@max3903 I need your help in How I can execute queue job based on a specific condition in the scheduler.

Because when we change the status of the ticket it will create a job based on functionality and worker is execute the job at that time.

How I can stop that execution of that job when changed the state of the ticket.
And execute it when current time >= Next Call in the scheduler

[max3903]

@murtuzasaleh When the job is executed, first thing you want to do is check if current time >= Next Call.

Unless @guewen has a more elegant way to handle this.

[murtuzasaleh]

@max3903

As we discussed there are multiple voicent backend based on the checked is_active field call_line_id

But what if there are multiple lines with the same stage, Which stage I will assign in queue job?

[max3903]

@murtuzasaleh If you have multiple line with the same stage, they should create multiple job.

[guewen]

@murtuzasaleh When the job is executed, first thing you want to do is check if current time >= Next Call.

Unless @guewen has a more elegant way to handle this.

You can put an eta on the job to be executed only after a date, but you already did, not sure what your issue is. In a job you can check the time again and raise a RetryableJobError to postpone the job (https://github.com/OCA/queue/blob/d708db07aea2def4a45f5e0a5f0ef66ee428b2b6/queue_job/exception.py#L31).

[guewen]

Keep this in mind: queue.job records are only supposed to be the representation of a method's delayed execution. This is not where you want to store your business logic, attach your files, ... You have to consider it as a black box to execute a method asynchronously - and only this -, method which can be executed more than once (idempotent; so check the state when the job starts), jobs are deleted after some time...

Sometimes, you may want to create a new model to actually contains the state of your business logic (draft, sent, done, whatever), link it to attachments, add relations, ... and make your jobs work on a record of this model (example: def voicent_import_and_runcampaign(self, call_state): where call_state would be a record of this model). I'm not even sure you need a new model here.

[max3903]

@guewen How can we get this job to be retried if the status returned by Voicent is not OK?

[guewen]

You can raise a RetryableJobError with an optional number of seconds before the retry Le jeu. 20 juin 2019 à 22:24, Maxime Chambreuil <notifications@github.com> a écrit :

…

***@***.**** commented on this pull request. ------------------------------ In connector_voicent_helpdesk_ticket/models/helpdesk_ticket.py <#97 (comment)>: > + + +class HelpdeskTicket(models.Model): + _inherit = 'helpdesk.ticket' + + @job + @api.multi + def check_status_job(self, voicent_campaign, helpdesk_ticket, + call_line): + for rec in self: + voicent_obj = voicent.Voicent( + call_line.backend_id.host, + str(call_line.backend_id.port), + call_line.backend_id.callerid, + str(call_line.backend_id.line)) + status = voicent_obj.checkStatus(voicent_campaign) @guewen <https://github.com/guewen> How can we get this job to be retried if the status returned by Voicent is not OK? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#97?email_source=notifications&email_token=AADF3R26XVA5LSKHPQ6HDMDP3PRPRA5CNFSM4HQC64QKYY3PNVWWK3TUL52HS4DFWFIHK3DMKJSXC5LFON2FEZLWNFSXPKTDN5WW2ZLOORPWSZGOB4GQZQQ#pullrequestreview-252513474>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AADF3RZKJYZ7IWRBJVUUWU3P3PRPRANCNFSM4HQC64QA> .