Skip to main content
June 3, 2024
Question

Fixed an issue with an Appian plugin

  • June 3, 2024
  • 4 replies
  • 0 views

So here’s the thing, I fixed an issue with an Appian plugin.

I downloaded its code, was able to get it running with all dependencies and build.gradle stuff, found the faulty code and upgraded it, I also upgraded and cleaned the code since lots of functions and/or variables were either deprecated or not used (seems like nobody tried to edit this plugin for ages now and is considered a black box)

Uploaded it to our demos environment for a spin and it works like butter now.

The thing is, this is a vital plugin for a certain demographic, I believe an update such as what I was able to accomplish in days should’ve been done by Appian a long time ago (this shouldn’t have passed testing stage let alone be published for thousands of developers and millions of users and be dismissed for a few years now)

So my question is has anyone ever faced a similar situation ? How did you deal with it ? And how do I / should I get in contact with Appian regarding this? I noticed the “report an issue” button in the Appian community but will there be a response if I send that email?

I’m curious what you guys think about this. slope

    4 replies

    davidj137213
    June 3, 2024

    I got in contact with Appian via Market explaining the problem, and how to fix it.... 

    mathieud0001
    June 3, 2024

    Simply submit your updated code for them to review.

    I would try the following things:

    1. Contact the App Market appmarket@appian.com 

    2. Open a support ticket (if contacting the app market doesn't work)

    3. Reach out to your Account Executive. (if opening a ticket doesn't work)

    mikes0011
    Brainy
    June 3, 2024

    Please tell me this means you fixed all the bugs in Log Reader?  [emoticon:98f842990f454422aa6a04953955f9d9]

    mathieud0001
    June 3, 2024

    Hoping for this too. [emoticon:d6dd260102fd406884fc96b8bc59760b]