DOCSLIB.ORG

Orchestration Server Developer's Guide

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Orchestration Server Developer's Guide Orchestration Server Developer's Guide Orchestration Server 8.1.3 3/10/2020 Table of Contents Orchestration Server 8.1.3 Developer Guide 5 Document Change History 7 SCXML Language Reference 9 Contents of SCXML Language Reference 53 Orchestration Extensions 55 Queue Interface 58 Classification Interface 124 Core Extensions 136 Interaction Interface 175 Interaction Interface Object Model 178 Interaction Interface Functions 198 Interaction Interface Action Elements 201 Interaction Interface Events 275 Dialog Interface 303 Statistic Interface 371 Resource Interface 382 Elasticsearch Connector 393 Migration from IRD 400 Orchestration Server Integration 406 Orchestration Getting Started Guide 412 Orchestration Server How-To 422 External Interfaces 426 Orchestration Server Sample Applications 437 Route to DN 444 Route to DN Using Target ID 445 Handle Routing Failure 446 Route to DN and Put to Virtual Queue 447 Route to Agent 448 Route to Agent Using Target ID 449 Route to Agent Without Checking Ready State 450 Route to Agent on Specific DN Type 451 Route to Agent and Run Treatments in Parallel 452 Route to Place 453 Route to Place Using Target ID 454 Route to Place Without Checking Ready State 455 Route to Agent Group 456 Route to Agent Group Using Target ID 457 Route to Agent Group Without Checking Ready State 458 Route to Agent Group With Threshold 459 Route to Place Group 460 Route to Place Group Using Target ID 461 Route to Place Group Without Checking Ready State 462 Route to Queue 463 Route to Queue Using Target ID 464 Route to Agent by Skills 465 Route to Agent by Skills Using Target ID 466 Route to Routing Point 467 Route to Routing Point Using Target ID 468 Route to Multiple Agents 469 Route to Multiple Agents Using Target ID 470 Route to Agent Using Statistic 471 Set Default Destination 473 ECMA Script on Top Level 474 ECMA Script on Entry Into State 475 ECMA Script on Exit From State 476 ECMA Script During Transition 477 ECMA Script After Invoke 478 ECMA Script Function 479 ECMA Script and Data Model 480 Fetch Data 481 Fetch Data in JSON Format 482 Fetch Data With Parameters 483 Fetch Data Using POST Method 484 Handle Fetch Failure 485 Invoke Session 486 Invoke Session With Parameters 488 Receive Event From Invoked Session 490 Receive Event From Invoked Session and Extract Event Data 492 Cancel Invoked Session 493 Handle Invoke Failure 494 Access Interaction Properties 496 Set User Data 497 Delete User Data 498 Delete All User Data 499 Access Voice Interaction Properties 500 Create Call 501 Collect Digits 502 Play Announcement With One Prompt 503 Play Announcement With Two Prompts 504 Play Announcement and Collect Digits 505 Play Sound 506 Record User Announcement 507 Delete User Announcement 508 Play Application 509 Cancel Call 510 Start on Remote Resource 511 Run Series of Treatments 512 Get Statistic Value 513 Get Average Statistic Value 514 Get Minimum Statistic Value 515 Get Maximum Statistic Value 516 Get Configuration Option Name 517 Check If Special Day 518 Get List Item Value 519 Lookup Value 520 Get Time in Time Zone 521 Get Date in Time Zone 522 Get Day in Time Zone 523 Work With E-Mail Or SMS 524 Work With Chat 527 Orchestration Server Sample Templates 530 Expand Target List 534 Change the Ownership of an Interaction 536 Detach an Interaction 539 Detect Consult Call 542 Detect User Data Changes 546 Route to Fetched Targets With Invoking SCXML Strategies 549 Orchestration Server Troubleshooting 552 Orchestration Server 8.1.3 Developer Guide Orchestration Server 8.1.3 Developer Guide SCXML Language Reference The Orchestration applications, such as routing applications, are created by writing SCXML documents either via your favorite text editor or via Genesys Composer. SCXML is a W3C evolving standard which allows applications to be described or represented in a state machine execution language. See SCXML Language Reference. Orchestration Extensions Orchestration Extensions are provided in the form of one or more functional modules that package up related actions, objects, functions and events that enable developers to interact with the Genesys platform without having to directly leverage existing SDKs. This allows developers from within Orchestration to create feature rich and open applications. See Orchestration Extensions. Migration from IRD For customers with existing IRD strategies, Composer can be used to help migrate your existing strategies. For information on the various mappings from IRD functions and objects please see IRD To Composer Migration Guide. For supplementary information please refer to Migration from IRD. Orchestration Integration To facilitate richer application development Orchestration enables other enterprise applications and systems within your environment to interact with it via open standard web based interfaces. By enabling this it allows the full potential of Orchestration within an enterprise setting to be realized and allows developers to build applications that extended past the capabilities of what is natively supported by Orchestration. To allow other applications within your enterprise to directly interact with Orchestration and the sessions that it is executing we support an external interface which is described here in External Interfaces and to enable Orchestration sessions to reach out and interact with other systems we support our Orchestration Integration Interfaces which is described here Orchestration Server Integration. Orchestration Server Developer's Guide 5 Orchestration Server 8.1.3 Developer Guide Getting Started Guide This guide is intended as a reference for those working with Orchestration for the first time, but can also serve as a reference for common use cases. For first time users, it is recommended you walk through the exercises sequentially as each section builds on the previous section. For users that is familiar with Orchestration, this guide will provide various samples for common tasks. See Orchestration Getting Started Guide. How-To This topic provides details on how to perform common tasks using SCXML and/or Orchestration See Orchestration Server How-To. Samples and Templates This collection of SCXML files will help you develop your Orchestration Server applications. It gives examples of typical use cases which serve as building blocks for your SCXML applications. See Samples and Templates. Troubleshooting See Orchestration Server Troubleshooting. Orchestration Server Developer's Guide 6 Document Change History Document Change History As described in the ORS 8.1.4 Release Note, the following topics are new or have been updated. 8.1.400.30 The ORS REST API POST method for starting a new SCXML session now supports application/json as a new value for Content-Type. 8.1.400.26 ORS now supports URIs of lengths up to 4,094 bytes. Previously, ORS truncated URLs longer than 2,048 bytes upon execution of the <session:fetch> action with the HTTP GET method. 8.1.400.24 This release introduces a new function, which allows you to retrieve the Orchestration Server version. _genesys.session.getServerVersion Parameters: None Return value type: STRING (version of Orchestration Server) 8.1.400.21 This release introduces a new detach attribute for the <ixn:redirect> action. Please see the release note for more information. 8.1.400.17 Previously, ORS allowed the function _genesys.session.setOptions to override only eight options. This restriction is now removed. Orchestration Server Developer's Guide 7 Document Change History 8.1.400.15 If Transaction List item attributes are stored in non-string format and the _genesys.session.getListItemValue(list, item, key) function retrieves the value of a particular key , it is returned as string. Previously, in this scenario, the _genesys.session.getListItemValue() function ignored non-string attributes. Also, if _genesys.session.getListItemValue() is called with two arguments or with ‘*’ as a third argument, the returned object will also include attributes whose values are empty strings. Previously, in ORS version 8.1.300.29, a minor defect was introduced, and attributes with empty values were not included in the returned object, when _genesys.session.getListItemValue() retrieved the Transaction List directly via ORS. To provide a reason for a session not being able to control a session that it owns, this release adds a new resultof property to the interaction.notcontrolled event. 8.1.400.12 A new “urs” method is added to the session:fetch Action Element. It simplifies usage of Universal Routing Server functions, previously available for Orchestration Server only via the Universal Routing Server Web interface. See <fetch> under the Action Elements section. Orchestration Server Developer's Guide 8 SCXML Language Reference SCXML Language Reference Click here to view the organization and contents of the SCXML Language Reference. SCXML stands for State Chart XML: State Machine Notation for Control Abstraction. Orchestration Server utilizes an internally developed SCXML engine which is based on, and supports the specifications outlined in the W3C Working Draft 7 May 2009 [4]. There are, however, certain changes and/or notable differences (see Extensions and Deviations) between the W3C specification and the implementation in Orchestration Server which are described on this page. Only the ECMAScript profile is supported (the minimal and XPath profiles are not supported). Usage SCXML documents are a means of defining control behaviour through the design of state machines. The SCXML engine supports a variety of control flow elements as well as methods to manipulate and send/receive data, thus enabling users to create complex mechanisms. For example, Orchestration, which is a consumer of the SCXML engine, uses SCXML documents to execute strategies. A simple strategy may involve defining different call routing behaviours depending on the incoming caller, however, the SCXML engine facilitates a wide variety of applications beyond simple call routing. Authoring SCXML documents can be done using any text editor or by leveraging the Genesys Composer tool. Syntax and Semantics The appearance of an SCXML document is very similar to that of any other markup language.
Load more

Recommended publications
  • Multilingual Aspects in Speech and Multimodal Interfaces
    Multilingual Aspects in Speech and Multimodal Interfaces Paolo Baggia Director of International Standards 1 Outline Loquendo Today Do we need multilingual applications? Voice is different from text? Current Solutions – a Tour: Speech Interface Framework Today Voice Applications Speech Recognition Grammars Speech Prompts Pronunciation Lexicons Discussion Points 2 Company Profile . Privately held company (fully owned by Telecom Italia), founded in 2001 as spin-off from Telecom Italia Labs, capitalizing on 30yrs experience and expertise in voice processing. Global Company, leader in Europe and South America for award-winning, high quality voice technologies (synthesis, recognition, authentication and identification) available in 30 languages and 71 voices. Multilingual, proprietary technologies protected Munich over 100 patents worldwide London . Financially robust, break-even reached in 2004, revenues and earnings growing year on year Paris . Offices in New York. Headquarters in Torino, Madrid local representative sales offices in Rome, Torino New York Madrid, Paris, London, Munich Rome . Flexible: About 100 employees, plus a vibrant ecosystem of local freelancers. 3 International Awards Market leader-Best Speech Engine Speech Industry Award 2007, 2008, 2009, 2010 2010 Speech Technology Excellence Award CIS Magazine 2008 Frost & Sullivan European Telematics and Infotainment Emerging Company of the Year Award Loquendo MRCP Server: Winner of 2008 IP Contact Center Technology Pioneer Award Best Innovation in Automotive Speech Synthesis Prize AVIOS- SpeechTEK West 2007 Best Innovation in Expressive Speech Synthesis Prize AVIOS- SpeechTEK West 2006 Best Innovation in Multi-Lingual Speech Synthesis Prize AVIOS- SpeechTEK West 2005 4 Do We Need Multilingual Applications? Yes, because … . We live in a Multicultural World . Movement of students/professionals, migration, tourism .
    [Show full text]
  • Orchestration Server Developer's Guide
    Orchestration Server Developer's Guide SCXML Language Reference 10/2/2021 Contents • 1 SCXML Language Reference • 1.1 Usage • 1.2 Syntax and Semantics • 1.3 Extensions and Deviations • 1.4 SCXML Elements • 1.5 Event Extensions • 2 Logging and Metrics • 2.1 Supported URI Schemes • 2.2 Supported Profiles • 2.3 Examples Orchestration Server Developer's Guide 2 SCXML Language Reference SCXML Language Reference Click here to view the organization and contents of the SCXML Language Reference. SCXML stands for State Chart XML: State Machine Notation for Control Abstraction. Orchestration Server utilizes an internally developed SCXML engine which is based on, and supports the specifications outlined in the W3C Working Draft 7 May 2009 [1]. There are, however, certain changes and/or notable differences (see Extensions and Deviations) between the W3C specification and the implementation in Orchestration Server which are described on this page. Only the ECMAScript profile is supported (the minimal and XPath profiles are not supported). Usage SCXML documents are a means of defining control behaviour through the design of state machines. The SCXML engine supports a variety of control flow elements as well as methods to manipulate and send/receive data, thus enabling users to create complex mechanisms. For example, Orchestration, which is a consumer of the SCXML engine, uses SCXML documents to execute strategies. A simple strategy may involve defining different call routing behaviours depending on the incoming caller, however, the SCXML engine facilitates a wide variety of applications beyond simple call routing. Authoring SCXML documents can be done using any text editor or by leveraging the Genesys Composer tool.
    [Show full text]
  • A State-Transfer-Based Open Framework for Internet of Things Service Composition
    Doctoral Dissertation Academic Year 2018 A State-Transfer-based Open Framework for Internet of Things Service Composition Keio University Graduate School of Media Design Ruowei Xiao A Doctoral Dissertation submitted to Keio University Graduate School of Media Design in partial fulfillment of the requirements for the degree of Ph.D of Media Design Ruowei Xiao Thesis Advisor: Associate Professor Kazunori Sugiura (Principal Advisor) Professor Akira Kato (Co-advisor) Professor Keiko Okawa (Co-advisor) Thesis Committee: Professor Akira Kato (Principal Advisor) Professor Keiko Okawa (Member) Professor Kai Kunze (Member) Senior Assistant Professor Takeshi Sakurada (Member) Abstract of Doctoral Dissertation of Academic Year 2018 A State-Transfer-based Open Framework for Internet of Things Service Composition Category: Science / Engineering Summary Current Internet-of-Things (IoT) applications are built upon multiple architec- tures, standards and platforms, whose heterogeneity leads to domain specific tech- nology solutions that cannot interoperate with each other. It generates a growing need to develop and experiment with technology solutions that break and bridge the barriers. This research introduces an open IoT development framework that offers gen- eral, platform-agnostic development interfaces, and process. It allows IoT re- searchers and developers to (re-)use and integrate a wider range of IoT and Web services. A Finite State Machine (FSM) model was adopted to provide a uniform service representation as well as an entry point for swift and flexible service com- position under Distributed Service Architecture (DSA). Leveraging this open IoT service composition framework, value-added, cross-domain IoT applications and business logic can be developed, deployed, and managed in an on-the-fly manner.
    [Show full text]
  • Download As A
    Client-Side State-based Control for Multimodal User Interfaces David Junger <[email protected]> Supervised by Simon Dobnik and Torbjörn Lager of the University of Göteborg Abstract This thesis explores the appeal and (ease of) use of an executable State Chart language on the client-side to design and control multimodal Web applications. A client-side JavaScript implementation of said language, created by the author, is then discussed and explained. Features of the language and the implementation are illustrated by constructing, step-by-step, a small multimodal Web application. Table of Contents Acknowledgments Introduction 1. More and more modality components 1.1 Multimodal Output 1.2 Multimodal Input 2. Application Control 2.1 Multimodal Architecture and Interfaces 2.2 Internal application logic 2.3 Harel State Charts 2.4 SCXML 2.5 Benefits of decentralized control 3. JSSCxml 3.1 Web page and browser integration 3.2 Implementation details 3.3 Client-side extras 3.4 Performance 4. Demonstration 4.1 The event-stream 4.2 The user interface 4.3 Implementing an output modality component 4.4 Where is the “mute” button? 5. The big picture 5.1 Related work 5.2 Original contribution 6. Future Work References Acknowledgments I learned about SCXML (the aforementioned State Chart language) thanks to Torbjörn Lager, who taught the Speech and Dialogue course in my first year in the Master in Language Technology. Blame him for getting me into this. Implementing SCXML was quite a big project for me. I would never have considered starting it on my own, as I have a record of getting tired of long projects and I was afraid that would happen again.
    [Show full text]
  • A Framework for the Declarative Implementation of Native Mobile Applications
    A Framework for the Declarative Implementation of Native Mobile Applications Patricia Miravet∗, Ignacio Marin∗, Francisco Ortiny, Javier Rodriguez∗ June 28, 2013 Abstract The development of connected mobile applications for a broad au- dience is a complex task due to the existing device diversity. In order to soothe this situation, device-independent approaches are aimed at im- plementing platform-independent applications, hiding the differences among the diverse families and models of mobile devices. Most of the existing approaches are based on the imperative definition of applica- tions, which are either compiled to a native application, or executed in a Web browser. The client and server sides of applications are im- plemented separately, using different mechanisms for data synchroniza- tion. In this paper we propose DIMAG, a framework for defining native device-independent client-server applications based on the declarative specification of application workflow, state and data synchronization, user interface, and data queries. We have designed DIMAG consider- ing the dynamic addition of new types of devices, and facilitating the generation of applications for new target platforms. DIMAG has been implemented taking advantage of existing standards. Keywords: Device fragmentation, mobile applications, data and state syn- chronization, dynamic code generation, client-server applications 1 Introduction The development of connected mobile applications is a promising field for companies and researchers. Around 6 billion cellular connection subscrip-
    [Show full text]
  • Automatic Method for Testing Struts-Based Application
    AUTOMATIC METHOD FOR TESTING STRUTS-BASED APPLICATION A Paper Submitted to the Graduate Faculty of the North Dakota State University of Agriculture and Applied Science By Shweta Tiwari In Partial Fulfillment for the Degree of MASTER OF SCIENCE Major Department: Computer Science March 2013 Fargo, North Dakota North Dakota State University Graduate School Title Automatic Method For Testing Strut Based Application By Shweta Tiwari The Supervisory Committee certifies that this disquisition complies with North Dakota State University’s regulations and meets the accepted standards for the degree of MASTER OF SCIENCE SUPERVISORY COMMITTEE: Kendall Nygard Chair Kenneth Magel Fred Riggins Approved: 4/4/2013 Brian Slator Date Department Chair ABSTRACT Model based testing is a very popular and widely used in industry and academia. There are many tools developed to support model based development and testing, however, the benefits of model based testing requires tools that can automate the testing process. The paper propose an automatic method for model-based testing to test the web application created using Strut based frameworks and an effort to further reduce the level of human intervention require to create a state based model and test the application taking into account that all the test coverage criteria are met. A methodology is implemented to test applications developed with strut based framework by creating a real-time online shopping web application and using the test coverage criteria along with automated testing tool. This implementation will demonstrate feasibility of the proposed method. iii ACKNOWLEDGEMENTS I would like to sincerely thank Dr. Kendall Nygard, Dr. Tariq M. King for the support and direction.
    [Show full text]
  • SCXML and VOICE INTERFACES 1 Introduction 2 W3C Architectures
    SCXML AND VOICE INTERFACES Graham Wilcock University of Helsinki, Finland Abstract. The paper shows how State Chart XML (SCXML) can support the design of voice interfaces. After describing the W3C Data Flow Presentation (DFP) framework, SCXML is illustrated by a simple stopwatch example. When the presentation layer’s initial graphical interface is extended by adding voice components, the SCXML-based flow layer can be reused unchanged, thanks to the clean separation between the flow layer and the presentation layer. 1 Introduction State Chart XML (SCXML) (W3C 2007a) is a general-purpose event-based state machine language. It is expected to play a role in more than one area where W3C is currently developing technical architectures. One area is the Voice Browser Activity, another is the Multimodal Interaction (MMI) Activity. In Section 2 we review the W3C’s recent discussions of the technical architectures in these areas. Section 3 presents a simple example SCXML application. Section 4 describes how the application can be extended by adding new components in the presentation layer, while reusing the same SCXML-based flow layer. 2 W3C architectures The Voice Browser Activity has developed the Data - Flow - Presentation (DFP) architecture (W3C 2006), outlined in simplified form in Figure 1 (Barnett et al. 2006). The data layer manages data for the application. The flow layer controls the logic or application flow. The presentation layer handles interaction with the user. The separation of concerns on which the DFP architecture is based is an instance of the successful Model - View - Controller (MVC) design pattern that is widely used in software engineering.
    [Show full text]
  • NEXOF-RA NESSI Open Framework – Reference Architecture IST- FP7-216446
    NEXOF-RA NESSI Open Framework – Reference Architecture IST- FP7-216446 Deliverable D9.1 Relevant Standardisation Bodies and Standards for NEXOF Franz Kudorfer, Siemens Nunzio Ingraffia, Engineering Mike Fisher, BT Due date of deliverable: 31/08/2008 Due date of rework: 31/03/2009 Actual submission date: 27/03/2009 This work is licensed under the Creative Commons Attribution 3.0 License. To view a copy of this license, visit http://creativecommons.org/licenses/by/3.0/ or send a letter to Creative Commons, 171 Second Street, Suite 300, San Francisco, California, 94105, USA. This work is partially funded by EU under the grant of IST-FP7-216446. NEXOF-RA • FP7-216446 • D9.1 • Version 07, dated 26/03/2009 • Page 1 of 34 Change History Version Date Status Author (Partner) Description 01 12/08/2008 Draft Franz Kudorfer First extract of WIKI 02 04/09/2008 Draft Nunzio Ingraffia Contribution to introduction, revisiting the standardization bodies paragraph, and suggestion to conclusions. 03 05/09/2008 Draft Mike Fisher Review and language enhancement 04 09/09/2008 Final Franz Kudorfer Executive summary, polishing and finalisation of the document 05 25/02/2009 Draft Franz Kudorfer Complete rework according to reviewers’ remarks 06 06/03/2009 Draft Franz Kudorfer Submission to internal review 07 26/03/2009 Final Franz Kudorfer Rework according to review comments and finalisation of the document NEXOF-RA • FP7-216446 • D9.1 • Version 07, dated 26/03/2009 • Page 2 of 34 EXECUTIVE SUMMARY Standards have an essential influence on the acceptance and applicability of IT solutions. NESSI is committed to deliver an Open Framework based on Open Standards (NEXOF).
    [Show full text]
  • Xml Based Framework for Contact Center Applications
    XML BASED FRAMEWORK FOR CONTACT CENTER APPLICATIONS Nikolay Anisimov, Brian Galvin and Herbert Ristock Genesys Telecommunication Laboratories (an Alcatel-Lucent company) 2001 Junipero Serra, Daly City, CA, USA Keywords: Call center, contact center application, VoiceXML, Call Control XML, organizational structure. Abstract: W3C languages, VoiceXML and CCXML all play an important role in contact centers (CC) by simplifying the creation of CC applications. However, they cover only a subset of contact center functions, such as simple call control and interactive voice response (IVR) with automatic speech recognition. We discuss ways to complement VoiceXML and CCXML in order to cover all necessary contact center functions required to script end-to-end interactions in a consistent and seamless way. For this purpose we introduce an XML forms-based framework called XContact comprising the CC platform and applications, multi-script and multi-browsing, and interaction data processing. We also discuss how routing as a key CC capability can be scripted/captured within such framework in order to demonstrate the overall approach. 1 INTRODUCTION center product cannot be easily transferred to another one. Contact centers (CC) play a very important role in A proven way of achieving application contemporary business. According to some uniformity, platform independence, and estimations (Batt et al, 2005, Brown et al, 2005, simplification of the task of creating business Gans et al, 2003) 70% of all business interactions applications is to employ XML-based standards and are handled in contact centers. In the U.S., the related technologies. XML is increasingly used as a number of all contact center workers is about 4 basis for building applications in different vertical million or 2.5-3% of the U.S.
    [Show full text]
  • Orchestration Server Deployment Guide
    Orchestration Server Deployment Guide Orchestration Server 8.1.4 8/16/2021 Table of Contents Orchestration Server 8.1.4 Deployment Guide 4 About Orchestration Server 6 New in This Release 12 Architecture 16 Deployment Models 30 SCXML and ORS Extensions 35 General Deployment 37 ORS Features 48 Persistence 49 High Availability 54 Graceful Shutdown 62 Clustering 63 Load Balancing 67 Multiple Data Centers 72 Direct Statistic Subscription 74 Performance Monitoring 79 Hiding Sensitive Data 90 Debug Logging Segmentation 96 Elasticsearch Connector 97 Direct Statistic Definition 120 Configuration Options 124 Application-Level Options 125 Common Log Options 183 Switch gts Section 186 DN-Level Options 188 Enhanced Routing and Interaction Submitter Script Options 191 Interacting with eServices 199 ORS and SIP Server 205 SCXML Application Development 210 Install Start Stop 216 Installation 217 Starting and Stopping 225 Uninstalling ORS 229 Graceful Shutdown 62 Sizing Guidance 231 Orchestration Server 8.1.4 Deployment Guide Orchestration Server 8.1.4 Deployment Guide Welcome to the Orchestration Server 8.1.4 Deployment Guide. This guide explains Genesys Orchestration Server (ORS) features, functions, and architecture; provides deployment-planning guidance; and describes how to configure, install, uninstall, start, and stop the Orchestration Server. About Orchestration Server General Configuration & Deployment This section includes information on: This section includes information on: ORS Overview Prerequisites New in This Release Deployment Tasks Architecture
    [Show full text]
  • SCXML for Building Conversational Agents in the Dialog Web Lab
    SCXML for Building Conversational Agents in the Dialog Web Lab David Junger, Torbjörn Lager and Johan Roxendal Department of Philosophy, Linguistics and Theory of Science, University of Gothenburg. Department of Swedish, University of Gothenburg. [email protected], [email protected], [email protected] 1. Introduction takes care of some of the problems of ordinary FSMs – in The W3C has selected Harel Statecharts, under the name particular the notorious state explosion problem. Further- of State Chart XML (SCXML), as the basis for future stan- more, a complex state may contain a history state, serving dards in the area of (multimodal) dialog systems (Barnett et as a memory of which substate S the complex state was al. 2012). In an effort to educate people about SCXML we in, the last time it was left for another state. Transition to are building a web-based development environment where the history state implies a transition to S. In addition, the the dialogs of embodied, spoken conversational agents can SCXML standard also provides authors with means for ac- be managed and controlled using SCXML, in a playful and cessing external web-API:s to for example databases. interesting manner. The expressivity of SCXML makes it possible not only to specify large and very complex dialog managers in the 2. SCXML = STATE CHART XML style of FSMs, but also to implement more sophisticated SCXML can be described as an attempt to render Harel dialog management schemes such as the Information-State statecharts (Harel 1987) in XML. Harel developed his stat- Update approach (Kronlid & Lager 2007).
    [Show full text]
  • Orchestration Server 8.0 Deployment Guide
    Orchestration Server 8.0 Deployment Guide The information contained herein is proprietary and confidential and cannot be disclosed or duplicated without the prior written consent of Genesys Telecommunications Laboratories, Inc. Copyright © 2010 Genesys Telecommunications Laboratories, Inc. All rights reserved. About Genesys Alcatel-Lucent's Genesys solutions feature leading software that manages customer interactions over phone, Web, and mobile devices. The Genesys software suite handles customer conversations across multiple channels and resources—self-service, assisted-service, and proactive outreach—fulfilling customer requests and optimizing customer care goals while efficiently using resources. Genesys software directs more than 100 million customer interactions every day for 4000 companies and government agencies in 80 countries. These companies and agencies leverage their entire organization, from the contact center to the back office, while dynamically engaging their customers. Go to www.genesyslab.com for more information. Each product has its own documentation for online viewing at the Genesys Technical Support website or on the Documentation Library DVD, which is available from Genesys upon request. For more information, contact your sales representative. Notice Although reasonable effort is made to ensure that the information in this document is complete and accurate at the time of release, Genesys Telecommunications Laboratories, Inc., cannot assume responsibility for any existing errors. Changes and/or corrections to the information contained in this document may be incorporated in future versions. Your Responsibility for Your System’s Security You are responsible for the security of your system. Product administration to prevent unauthorized use is your responsibility. Your system administrator should read all documents provided with this product to fully understand the features available that reduce your risk of incurring charges for unlicensed use of Genesys products.
    [Show full text]