Reusable module of the Orchestration Designer

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts
  • jishit
    Member
    • Nov 2018
    • 5

    Reusable module of the Orchestration Designer

    Hi guys,
    We are facing an OD call flow issues.

    I migrated a call flow created in OD7.0 to OD8.1.2. There are no compilation errors, and checking using the simulator works fine.
    However, the call type setting of the reusable module created in OD7.0 is a mixture of "Local" and "Subdialog".
    "Subdialog" is recommended from OD7.2.3 after.
    Will there be any problems if I leave "Local" and "Subdialog" mixed like this?
    Currently, there are a few VXML read errors (after GetKeyAndCheck) between the AEP and AP servers. I don't know if this is caused by the mixture of "Local" and "Subdialog".

    AEP 8.1.2
    OD 8.1.2
    AP Server; WebSphere
    Last edited by jishit; 12-19-2024, 05:43 PM.
  • wilsonyu
    Hot Shot
    .
    • Sep 2011
    • 24

    #2
    The mixture of "local" and "subdialog" is fine. You only need to be concerned when you see any problem like delay. Sometimes, local calls are needed especially when you need to need to pass parameters with complex variables

    Comment

    • avc925034797060
      • Jun 2025
      • 1

      #3
      Convert all reusable modules to "Subdialog" if possible, following OD7.2.3+ best practices.
      Check the call flow to ensure that the invocation of modules aligns with the expected call type.
      Debugging:
      1. Enable detailed logs on AEP and AP servers.
      2. Monitor the VXML sessions around the point of GetKeyAndCheck to identify if the mixture causes context switching issues.
      Geometry Dash

      Comment

      Loading