• State Not Answered
  • Replies 5 replies
  • Subscribers 15 subscribers
  • Views 920 views
  • Users 0 members are here
Options
Related

Deploying widget extension to Verint Community hosted in a Virtual Machine.

Eliot Cuduco

Good morning,

I developed a widget extension in Visual Studio with a function that I called within the implementation of automation in the Community site. I was able to add the compiled DLL into the bin folder of my local machine installation of Verint, and the function that I developed ran well as expected. However, when I take the DLL and deployed it into another Verint installation in a Virtual machine. The extension is recognized and enabled (and even appeared in the API documentation), however, when the site is trying to run execute the code, I am getting this is the error:

Note: The name of the extension is pavilion_v1_user_methods


UnknownException: An error occurred while rendering the '' script from the 'Pavilion - Update all users private emails with fake emails' automation ('Pavilion - Update all users private emails with fake emails'/5fc84ee7-cea7-4292-8a38-7d0702f873e7). (An unidentified error occurred within a script.) ---> ScriptException: ReferenceError: pavilion_v1_user_methods is not defined (An unidentified error occurred within a script.)

   --- End of inner exception stack trace ---
   at Telligent.Evolution.Platform.Scripting.Implementations.ScriptedExtensionExecutionService.HandleExecutionException(Exception ex, ScriptExecutionExceptionHandling exceptionHandling, ScriptedExtension extension, String scriptName, IRenderedScript& renderedScript)
   at Telligent.Evolution.Platform.Scripting.Implementations.ScriptedExtensionExecutionService.ExecuteScriptByName(ScriptedExtension extension, String scriptName, ScriptExecutionExceptionHandling exceptionHandling)
   at Telligent.Evolution.Platform.Automations.Implementations.AutomationExecutionService.<>c__DisplayClass10_0.<Execute>b__0()
   at Telligent.Evolution.Components.UserDataService.RunAsUser(Action a, String username, Nullable`1 userId, Nullable`1 membershipId)
   at Telligent.Evolution.Components.UserService.RunAsUser(Action a, String username, Nullable`1 userId, Nullable`1 membershipId)
   at Telligent.Evolution.Api.Services.UserService.RunAsUser(Action a, String username, Nullable`1 userId, Nullable`1 membershipId)
   at Telligent.Evolution.Platform.Automations.Implementations.AutomationExecutionService.Execute(TextWriter writer, ConfiguredAutomation configuredAutomation, AutomationTriggerContext triggerContext, Nullable`1 cancellationToken, Boolean throwExceptions)
   at Telligent.Evolution.Platform.Automations.Implementations.AutomationJob.Execute(JobData jobData)
Parents Reply Children
  • 0 in reply to Former Member

    I did not find any differences (so far). Eventually, I tried to run it again, it worked. However, I noticed that at first when it worked I had a weird behavior in which the job ran the script just for a very small amount (like 100 or 200 records) of the expected data. Then I tried again, it happened the same. However, in the first attempt, I ran completely and processed all the data (over 6K records). I am wondering if there is a connection issue. Slight smile
    Thanks again in advance.

  • Former Member
    0 Former Member in reply to Eliot Cuduco

    It's possible that a plugin reload resolved the initialization issue. Do you have any exceptions in Administration > Monitoring > Exceptions?

    What are your selected triggers for the automation? API events, manual, scheduled?

  • 0 in reply to Former Member

    I think you are right about the "plugin to reload resolved the initialization". Yes, I did have plugin initializations errors. The trigger that I was using was scheduled. At some point, I tried an experiment of running it with another trigger (API event on User.AfterUpdate event). In that case, it worked, then I went back to schedule, and it worked better. And by, better, I mean that at least it recognized the object, but just ran for small data. Then, I tried again a couple of times, and it finally ran for the large expected data. After that, it has been consistent. All of that was yesterday. Today, we tried again, and it ran consistently. So, again, it is possible that something (perhaps...a refresh) in between the attempts on yesterday fixed the initial abnormal behavior.  I will continue to make observations, but I think all is well for now. Thanks again for everything.

About
Privacy Policy
Terms of use
Copyright 2024 Verint, Inc.
Powered by Verint Community