Hello All,
I have a question regarding the uploadfile component. When a file is uploaded using this component, the default behavior is the screen shits its focus to the top.
Our requirement is to have the focus at the same section of uploadfile component i.e Upload as per the screenshot.
Whenever we upload any file in Appian, the file is scaned for virus and then upload to the Appian KM space.
The other requirement is to capture the metric/performance when a file of size ranging from 100MB to 1GB is uploaded.
Thanks & Regards
Girish Katti
Discussion posts and replies are publicly visible
What do you mean with " the default behavior is the screen shits its focus to the top."?
What kind of metric/performance do you want to capture?
Hello Stefan,
Thanks for the reply, " the default behavior is the screen shits its focus to the top." - I meant when a file is uploaded the screen scrolls back to the top.
What kind of metric/performance do you want to capture? - basically the time factor.
OK. So you mean that after a submit action, the new interface is displayed from the top? This is expected behavior. Why is this an issue? How does your UX work?
I am not aware that the is a metric available that shows how long a file upload takes.
Actually we are migrating a legacy application build on C# and in their current behavior after the submit action the interface is not displayed from the top
Yes I agree in Appain we see the interface is displayed from the top on submission, which is the issue for the users. So we have no alternative and confirm this is Appian behavior.
Any performance metrics on size vs. time is possible?
I understand. In my experience, it is important to NOT try to copy the exact UX of a legacy app into Appian. But I understand that this something stakeholders do not want to hear.
I do not know of any file upload specific metrics. I am still interested why you need/want this.
From the UI a file of 1 GB is uploaded and through the process the operation are performed like unzip and making entries to the database tables based on data present in the file.
This process have more than 50 nodes added based on the file processing logic.
During the upload its take a long time to display back the data which is not the case in legacy application. So the team wanted the metric of size vs time.
Trying to process a file that large using Appian processes is probably not something I would recommend.
https://community.appian.com/w/the-appian-playbook/188/transferring-processing-large-data-sets-etl
Low-code with Appian make us developers way faster, but the tradeoff is a reduction of flexibility. This works great for typical process driven business applications, but for handling of large files not so much.
We typically try to write the file to the DB as direct as possible and do the processing in stored procedures.
Sure will try the approach suggested.
Thankyou very much for the time reply and support.