excel

Hi,

You can have "Export to excel" link , clicking on the link , the excel report can be generated.

You can use this smart service to export the data to excel.
Export Data Store Entity to Excel Smart Service - Appian 22.1

Hi,

Thanks for your response.

When I have gone through the provided help link, I didn't find a way to call a database view in that.

Can you throw some light on how to call a database view.

Thanks

Create CDT based on the view and map the entity in datastore.

Use the entity in the Export to excel smart service and set the other info in the smart service. On Data->Output tab, save the new document AC to process variable.

Thanks for sharing more details.

Is it possible to call a process model when I click on the "Export to Excel" link and use the service instead of using 

a!exportDataStoreEntityToExcel()

Yes, you can use start process link to call a process.

Is it not possible to call a process model using a!dynamicLink().

Thanks.

Is it possible to start/trigger process model using a!dynamicLink()

Rao2022 said:

Is it possible to start/trigger process model using a!dynamicLink()

Yes.  For this you would include a call to a!startProcess() within the dynamicLink's saveInto parameter.  This would launch the referenced process model asynchronously (in other words, in the background exclusively), and the user would stay on the current form.

The good side is that you can have data generated by the process (including a created Document Id) save back into the local data on your original interface - meaning you could have the referenced process model generate a document, then pass that back to your form and expose it via a Document Download Link (i.e. contained in a Rich Text Display Field).

Rao2022 said:

Is it possible to start/trigger process model using a!dynamicLink()

Yes.  For this you would include a call to a!startProcess() within the dynamicLink's saveInto parameter.  This would launch the referenced process model asynchronously (in other words, in the background exclusively), and the user would stay on the current form.

The good side is that you can have data generated by the process (including a created Document Id) save back into the local data on your original interface - meaning you could have the referenced process model generate a document, then pass that back to your form and expose it via a Document Download Link (i.e. contained in a Rich Text Display Field).

Thank you. Let me give it a try this way.