-
Notifications
You must be signed in to change notification settings - Fork 17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Generate CEL User record on Blocks by default (checkbox option) #6
Comments
Hi, It sounds like an interesting idea.
So my proposition is to implement some more flexible solution:
Therefore, the managing of this options does not need changes in the script structure, however it is still possible to add some thin customization by single "Custom" blocks. With best regards, |
Howdy, Right on the spot, it is for generating trace and historical information on the IVR for QA, process workflow and of course statisctical purposes. At that moment didn't even think of script debugging, which would certainly be a bonus. Couldn't agree more about your concerns on the CEL , and when thinking about
Would that handling be done with an embedded macro after each "TRACE BLOCK" (if it can be called this way)? When you say:
Would this be a code on the block.class so all blocks inherited from it? Did I get this right? Best Regards, Frederico C Wilhelms |
Hi, As far as I understand you want to hardcode some CEL function as before/after block notification command.
What do you mean by "TRACE CONNECTOR" and "TRACE BLOCK"?
Yes the command fields have to be declared in the base Block class. Do you want to do it by yourself and make a pull request? With best regards, |
Howdy,
Didn't expressed myself correctly, can see why you thoutgh of a hard-code; actually, was thinking in an optional button (JS based template overlay ) to simplify the filling the field., I apologize if it suggested otherwise.
Was under the impression that a new block "TRACE" would tie this, for the specific goal of generating these before/after events.
Yes, was considering it really hard. Since I'm on a timeline, and quite sure this was not on your agenda for now, ... Best regards, |
Howdy ,
I'm using Astergazer to administer quite some IVRs, and in order to get all desired tracking , I'm generating quite a good ammount of UsegCEL in the process.
After looking in to the code, thoutgh about incorporating an option to the BLOCK so it could inherit a UserCEL that would be generated at TRANSLATE time from an option checkbox / textbox ( USEREVENTCODE , PARAMETERS ), in the various blocks .
So , whenever you check the "AUTOGENERATE USERCEL" , it would enable the textbox in that specific block to aggregate (like a combo) a USEREVENTBLOCK to it .,
This would associate that EVENT generation on the point, and would not pollute the script GUI with the blocks, considering that in that specific case , the EVENT is associated whith that block.,
In my need, It would suffice to generate a "[ENTRY|EXIT]_[BLOCK]{IDENTIFICACION | LABEL}" event , with an optional PARAMETER string., but thinking a little further, do believe that others would like to consider expanding this idea.
So, considering just this milestone of a supposed roadmap, could you give me the directions to code this in the better way possible, respecting your your structure?
Thanks in advance,
Frederico Wilhelms
The text was updated successfully, but these errors were encountered: