Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
Created by: null on 20-09-2006 09:25:56 AM Hi is there anyway to configure an Element from XML without the dynamic URL loading option. I don't want to create a class with loads of setting options.
Ideally want to create a new "Audio class component" and load XML from the session directly and not via URL from some outside server.
If this isn't viable directly or simply, can you consider it for an additional option.
Cheers
Subject: RE: XML Feeds Replied by: Michael Bochynski on 03-10-2006 08:00:23 PM Karl,
you can achieve this functionality by obtaining this data once and setting it as session data.
You could use On-Call-Start XML API, reference the external URL and obtain the document, Your response would set session data required for the call. You can also pass the data in the initial URL, as it is described in the following Audium Knowledge Base article:
Note that as of Audium Studio 5.1.3 you can use Substitutions virtually anywhere in the elementsâ¿¿ settings. Hence, all the data you set in the On-Call-Start can be referenced using Substitutions, thus removing the necessity to reference the external URL for each element.
Regards, Michael
Subject: RE: XML Feeds Replied by: null on 06-10-2006 07:51:17 AM Michael,
Appreciate that, but I was aware of all this. You will know that substitutions can only do so much. For full much deeper dynamic configuration of the element there are things you just can't substitute!
Therefore if I answer my question in part. Using an "action" element I can fetch hybrid pieces of XML structures and move these to session variables.
What I want to do is to be able to arrive at an element further down the call flow change and say, "here's the XML content" configure yourself. Right now it's HTTP based, or class based.
I want the dynamic configuration to have an option of a session variable or the ability to pre-load XML and persist it for later reference without round tripping.
Hope all that makes sense! Clients are pointing it out!
Subject: pre-load and reference XML in a later step Replied by: null on 06-10-2006 07:51:40 AM Michael,
Appreciate that, but I was aware of all this. You will know that substitutions can only do so much. For full much deeper dynamic configuration of the element there are things you just can't substitute!
Therefore if I answer my question in part. Using an "action" element I can fetch hybrid pieces of XML structures and move these to session variables.
What I want to do is to be able to arrive at an element further down the call flow change and say, "here's the XML content" configure yourself. Right now it's HTTP based, or class based.
I want the dynamic configuration to have an option of a session variable or the ability to pre-load XML and persist it for later reference without round tripping.
Hope all that makes sense! Clients are pointing it out!
Subject: RE: pre-load and reference XML in a later step Replied by: Vance Vagell on 12-10-2006 06:45:15 PM Hi Karl,
Another option is to create a simple dynamic configuration class using the Audium Java API, that pulls your custom XML from session data and uses that to configure the element. Here is an example:
1) A custom call start action (using either the Java API or XML API) pulls down various XML configuration files from URIs. This step is pre-caching all of the XML configurations you will use later in your call. For each XML config found, a session data variable named ELEMENTNAME_CONFIG is created, where ELEMENTNAME is the name of the element the config is for.
2) Each element in the call flow that uses dynamic config does so via a custom Java class. This class checks the name of the element it is configuring, and uses that to retrieve session data named ELEMENTNAME_CONFIG.
3) This data is checked to ensure it is valid (custom) XML. If so, the Java class class parses the XML and configures the element from it.
[b:0e15244a6e]Note 1:[/b:0e15244a6e] The "XML" mentioned in this example is your own custom format (as opposed to the XML API, or XML configurations you see in the file system). This is because it is your small custom Java class that will parse the XML and manipulate each element's settings -- you have full control over the parsing and setting.
[b:0e15244a6e]Note 2:[/b:0e15244a6e] This approach only works when all dynamic content is available at the start of the call, and will not change throughout. Since all the XML is downloaded at the start of the call, any future changes will not be reflected until the next call.
If using the Java API to the extent suggested in that example is not an option please provide an example of how you would like this functionality to work (e.g. loading configurations from session data) and we will open a feature request for you.
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: