Created by: Angelina Talley on 14-01-2010 05:14:14 PM We have a need to log items from a decision element in our call flow. For all other types of elements, it's easy to just add items to add to the General tab's Add to Log area. But, when dragged into the Studio editor, the Decision element of course does not have that tab. The simplest solution of course would be to just configure the decision element with a Java class and log the values there in Java, or to write a custom decision element (which will gain us the Java interface or the General tab both). However, we're looking at many, many decision elements that need to have values logged, so maintaining that many Java classes is not practical. Is there any way to have both the General tab and something like the decision or XML editor? Or, can someone suggest another alternative?
Thanks!
Subject: RE: logging from a decision element Replied by: Althaf Bealdar on 28-06-2011 08:44:42 AM
We have a need to log items from a decision element in our call flow. For all other types of elements, it's easy to just add items to add to the General tab's Add to Log area. But, when dragged into the Studio editor, the Decision element of course does not have that tab.
The simplest solution of course would be to just configure the decision element with a Java class and log the values there in Java, or to write a custom decision element (which will gain us the Java interface or the General tab both). However, we're looking at many, many decision elements that need to have values logged, so maintaining that many Java classes is not practical.
Is there any way to have both the General tab and something like the decision or XML editor? Or, can someone suggest another alternative?
Thanks!
There is no other go we have to use Java Class for Logging. Here create a common class which will log your requirement data like storing it in session and get that value based on the Decision element name. For example: if you want to log some Dynamic value store that Value in Session by naming Variable name as prefixing some text to the Decision element name where you will be logging it. in that decision element use get that value Dynamically specifying like "elementAPI.getSessionData("SESS_"+elementAPI.getCurrentElement()); assign this value to some variable and log that VAriable in Decision Element. I Hope this will help you. Thanks, Althaf
Subject: RE: logging from a decision element Replied by: Althaf Bealdar on 28-06-2011 08:47:56 AM We have a need to log items from a decision element in our call flow. For all other types of elements, it's easy to just add items to add to the General tab's Add to Log area. But, when dragged into the Studio editor, the Decision element of course does not have that tab. The simplest solution of course would be to just configure the decision element with a Java class and log the values there in Java, or to write a custom decision element (which will gain us the Java interface or the General tab both). However, we're looking at many, many decision elements that need to have values logged, so maintaining that many Java classes is not practical. Is there any way to have both the General tab and something like the decision or XML editor? Or, can someone suggest another alternative?
Thanks!
There is no other go we have to use Java Class for Logging. Here create a common class which will log your requirement data like storing it in session and get that value based on the Decision element name. For example: if you want to log some Dynamic value store that Value in Session by naming Variable name as prefixing some text to the Decision element name where you will be logging it. in that decision element use get that value Dynamically specifying like "elementAPI.getSessionData("SESS_"+elementAPI.getCurrentElement()); assign this value to some variable and log that VAriable in Decision Element. I Hope this will help you. Thanks, Althaf
Subject: RE: logging from a decision element Replied by: Hemal Mehta on 03-07-2011 09:53:14 AM One alternativen and somewhat crude way, if you really want to avoid java classes, put a audio element just before with a file silence.wav (no audio) and log everything just before that decision element and then in decision element use the xml editor. The decision element will anyways log the result.
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:
