I’m working on GAX (in a multi-tenant environment) and the new OPM Block in Composer v.8.1.201.72.
I’m having trouble assigning a GAX operational parameter to a variable in composer - can’t get it to assign
in GAX i have got the following parameter configured:
Name: After Hours Phone Number
Key: destAfterHourDN
Type: String
Value: 5000
Can anyone please point me the right direction on how to assign the APM_OPM system variable. The default value is:
eval(‘(’+session.connection.protocol.sip.requesturi[‘parameters’]+‘)’)
Also the correct syntax to assign the above parameter value to a user variable in the OPM block.
Did You deploy correctly scxml script through GAX. It should have OPM section with two values inside Transaction and Transaction_dbid. Otherwise You have to use normal list lookup functions.
Actually it is same - You still need to either deploy vxml profile through GAX - in such case GAX will create copy of profile object with CME with proper data or You need to do it manually by adding OPM section with same content in profile Annex tab
Actually when you create an OPM in GAX - it creates a list object in configuration under transactions. I have already mentioned that in my previous post, however my question is “how to assign the operational parameter value to a user variable in the OPM block in Genesys Composer.”
I’m looking for an example/code to show how to do that.
Before You access anything through OPM block You need to follow instruction I gave You in previous post. Sample code to access anything from OPM in vxml code is following
it look like you need to assign OPM values in IVR profile/RM config. but I didn’t try to do it yet…
check does this feature is supported by your RM and take a look on this limitation:
Note: As of 01/01/12, RM currently does not support OPM parameters with key names in capital letters at a solution level.
In GA or GAX: Create the voice platform profile for the vxml application
In GAX: Create the operational parameter (the key must NOT have capital letters or spaces)
In GAX: Create a parameter group template containing the operational parameter and the associated vxml application
In GAX: Deploy the parameter group template to create a parameter group. This step is the one that makes a new voice platform profile that contains the contents of the voice platform profile you created in Step 1 AND the OPM options section that contains the transaction and transaction_dbid KVPs
In Composer: add an OPM block to the call flow and in the assign OPM data section specify AppState.APP_OPM.X where X is the key from the parameter that you created in Step 2.
Make sure that the voice platform profile that is started is the one created in Step 4 because it is the one that has the OPM option values. The actual data is transferred to the IVR when RM starts it.
To get a updated value of the OPM parameter during the call you can use a Web Request block to query http://urs-ip:urs-http-port/urs/console?config+transaction+1234= (were 1234 is the transaction dbid that you want to retrieve) and an assign block to munge the returned data into JSON. in fact you could do that INSTEAD of using the OPM block in the callflow.