Hi,
We're moving one of our sites to portals. We have functionality where the user clicks an upload button, which kicks off a process via startProcessLink (incompatible in portals). This current process is chained, so it waits until the process is complete; the interface closes after the user submits the documents. Once the interface closes, the user instantly sees the new documents they've uploaded.
startProcessLink
Now, to convert this logic to be compatible with portals, we've changed startProcessLink to dynamicLink to just toggle between interfaces and use a startProcess function (which is compatible with portals) to write the documents. This new approach is an asynchronous call, so it no longer shows the newly uploaded documents instantly. Even leveraging the refreshVariable function with the refreshAlways parameter set to true doesn't work as expected. The documents only show up after the user interacts with the screen. Any thoughts on how I can achieve this in portals?
dynamicLink
startProcess
refreshVariable
refreshAlways
true
Discussion posts and replies are publicly visible
Set your a!startProcess() call to Synchronous and use the onSuccess parameter? And if you're using the old version of a!startProcess(), it was already synchronous as long as the process is chained.
Also / potentially separately, this is one of the prime cases in which you should look into utilizing the "a!submitUploadedFiles()" command. I've done this in a test portal and it worked just fine.
Made some updates with my refreshVariable locals and set the isSynchronous parameter to true and it worked like a charm. Thanks!
Thanks for confirming. Hope you're doing well!