How to start SQL to Excel plugin with the function a!startProcessLink?

Certified Associate Developer

Hi,

Actually I created a Process Model that export SQL to Excel with the plugin, but I don't know how I can put this PM in a!startProcessLink function and how I can filter inside my interface. Last time I used a!exportDataStoreEntityToExcel function but I don't know how replecate the same filters and conditions with this Process Model.

Thanks for your help.

  Discussion posts and replies are publicly visible

Parents
  • This is all a bit too vague for me to know how to approach an answer - can you tell us more about your use case, the user experience you're going for, what you already have in place (particularly as far as what the user would currently see, and how/where they'd be seeing it in your appian setup)?

    Usually, for example, I would not be considering "start process link" whatsoever for this - i'd have a form (i.e. a mostly read-only interface appearing somewhere on my site), where the user can select some desired parameters / filters / etc, then they press a "generate" button, which calls the process model by a!startProcess(), which runs automatically and generates the output dictated by what they had entered at the time of the "generate" click, and when completed, it passes the generated document ID back into the interface which I then show in a document download link in a Rich Text field.

  • 0
    Certified Associate Developer
    in reply to Mike Schmitt

    Yes, that's it . Actually I have an Interface that show a ReadOnlyGrid with dropdown and text field as filters. I want put this Process Model in a button and apply the filters, but i don't have the knowledge for do that.

  • Luckily it's not too difficult to do this - for a basic implementation you can merely pass the filters into the process model (which you'd have to configure in such a way that it handles them correctly, which in your case probably means integrating them into your SQL statement in whatever way is necessary).  Your "generate" button would simply call a!startProcess() and you'd pass in the filters as parameters, and capture the document ID of the generated document in the onSuccess saveInto.

Reply
  • Luckily it's not too difficult to do this - for a basic implementation you can merely pass the filters into the process model (which you'd have to configure in such a way that it handles them correctly, which in your case probably means integrating them into your SQL statement in whatever way is necessary).  Your "generate" button would simply call a!startProcess() and you'd pass in the filters as parameters, and capture the document ID of the generated document in the onSuccess saveInto.

Children