How I configured it so it would work is:
1. In GA or GAX: Create the voice platform profile for the vxml application
2. In GAX: Create the operational parameter (the key must NOT have capital letters or spaces)
3. In GAX: Create a parameter group template containing the operational parameter and the associated vxml application
4. 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
5. 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.
6. 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.
