Quantcast
Viewing all articles
Browse latest Browse all 2878

Ideas needed for app with multiple attachements

Hi guys!

 

We are developing a custom UI5 app to hire employees. The app is basically just a big form: it has many input fields but also multiple attachment upload possibility (UploadCollection). After the user presses save, we take the data to the backend with the OData and create the employee. If the create action was successful, we should next:

a) save the attachments to GOS (or Archive) using the new employee Pernr as key,

b) create a PDF and

c) send an email with the PDF and the uploaded attachments.

 

My problem is understanding what is the timing/place of the attachment uploads and how it aligns with the Create-method where I have the other data at hand (but not the attachments since they seem to go a different route).

 

I'm looking for the place in code where I would have access to both the data coming from UI and the attachments (so I could do the saving to GOS, create PDF and email). I've read some blogs where people create Z-tables for temporarily storing the attachments etc. but maybe there's a smarter way?

 

Just a note: we have UI5 libraries v1.28.12. I read 1.30 has some new switches for UploadCollection, like InstandUpload. Would these help?

 

Thanks a lot for any ideas and tips!
br,

Ossi M


Viewing all articles
Browse latest Browse all 2878

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>