" /> Difference Composer and IRD - Genesys CTI User Forum

Author Topic: Difference Composer and IRD  (Read 4468 times)

Offline Francielealmeida

  • Newbie
  • *
  • Posts: 2
  • Karma: 13
Difference Composer and IRD
« on: September 06, 2012, 08:07:21 PM »
Advertisement
Hi,

What is the main differences between the Composer and the IRD, and which is ORS (Orchestration Server) main function?

Offline cavagnaro

  • Administrator
  • Hero Member
  • *****
  • Posts: 7641
  • Karma: 56330
Re: Difference Composer and IRD
« Reply #1 on: September 06, 2012, 08:15:32 PM »
ORS is a new component with version 8 that process XML as new strategies design...gives more functions and power over controlling an interaction.
IRD is native URS designer, while composer is an eclipse GUI modified with a plugin that does the Genesys work. I have seen posts complaining about some stuff you can't do on composer but I don't think that there is any document that says exactly what the differences are, so trying both would be the best way to figure it out.

Offline Francielealmeida

  • Newbie
  • *
  • Posts: 2
  • Karma: 13
Re: Difference Composer and IRD
« Reply #2 on: September 06, 2012, 08:31:23 PM »
Ok, thanks for your help!

Offline bublepaw

  • Sr. Member
  • ****
  • Posts: 283
  • Karma: 10
Re: Difference Composer and IRD
« Reply #3 on: September 14, 2012, 09:56:48 AM »
Hi,

As far as I can see current version of composer should have function parity with IRD on level around 90%. IRD is old type of approach where You have flow trigger by one event (call arrived on routing point, agent answered call, maile arrived at queue). Composer and ORS give You state machine which can be triggered from many points - for example You can easily with one click create flow where queue is interupted by dtmf while same thing in IRD is complex. With ORS You can have flow that is started by request from web/mobile app and later is continued by voice call. With ORS and composer You can  create one flow for the whole call including agent part of call - for example call arrives on RP, You do selection, You wait unti agent answers call, do something else, wait till agent disconects call and write something to database - all on one Composer flow.

Having said that You can still use composer to write strategy in old fashion like in IRD. In Composer help file You have tables which shows IRD function and equivalent of Composer function.

One thing that much more different is deployment process which is still far away from what is there in IRD.