Displaying a Loading Banner While a Background Process Fetches a Document

vamshik254967 said:

document based on a primary key. The process takes approximately 5–10 seconds to retrieve the document and return it to the interface.

If you are retrieving using primary key, then you should investiagte the reason behind 5-10 s in query. Ideally it should be in milliseconds so you should definitely optimise your query. 

vamshik254967 said:

In the saveInto, I included both a!startProcess() and an a!save() to update a local flag variable that controls the banner visibility. However, I observed that the local variable is not updated immediately when the link is clicked. Instead, it gets updated only after the process started by a!startProcess() completes

saveInto executed saved in the order they appear within saveInto expression. Most likely your startProcess() is followed by the a!save() to update the local variable. Swap their order and it should resolve the execution order.

vamshik254967 said:

an alternative approach or recommended pattern in Appian

Generally user can download a document in two cliks on form itself. For example, Show a fetch button, when user clicks on it query and retrieve the doc id using primary key and save in in a local variable. When this local variable is populated, show a link 'Download' (and hide the 'Fetch' button) which allows user to download file having documentDownloadLink in backend()

vamshik254967 said:

document based on a primary key. The process takes approximately 5–10 seconds to retrieve the document and return it to the interface.

If you are retrieving using primary key, then you should investiagte the reason behind 5-10 s in query. Ideally it should be in milliseconds so you should definitely optimise your query. 

vamshik254967 said:

In the saveInto, I included both a!startProcess() and an a!save() to update a local flag variable that controls the banner visibility. However, I observed that the local variable is not updated immediately when the link is clicked. Instead, it gets updated only after the process started by a!startProcess() completes

saveInto executed saved in the order they appear within saveInto expression. Most likely your startProcess() is followed by the a!save() to update the local variable. Swap their order and it should resolve the execution order.

vamshik254967 said:

an alternative approach or recommended pattern in Appian

Generally user can download a document in two cliks on form itself. For example, Show a fetch button, when user clicks on it query and retrieve the doc id using primary key and save in in a local variable. When this local variable is populated, show a link 'Download' (and hide the 'Fetch' button) which allows user to download file having documentDownloadLink in backend()

I have already attempted to change the order of the actions within the saveInto parameter, placing the a!save() before and after the a!startProcess() call. However, this did not resolve the issue. The local variable still gets updated only after the process execution is completed, rather than immediately when the link is clicked.

Can you elaborate what the startProcess is doing actually? If you can call the query in a!save itself and get the document then what issue are you facing is enabling the documentDownloadLink with docId? I mean can the startProcess be skipped/removed entirey?

In this scenario, the a!startProcess() call is responsible for fetching the document. The process model invokes an SAP integration using the provided primary key, retrieves the corresponding document, and then returns the document back to the interface for download. Since the document retrieval depends on the SAP response, the process takes approximately 5–10 seconds to complete.

Got it! 

If changing the order of a!save and a!startprocess is not working, can you share a high level code structure with definition of local, banner field showWhen conditions as well as dynamic link saveInto in particular so as to help the current design better