SAP Fiori Elements – Call me lazy but I loooove Fiori Elements the ability to create an entire Fiori-compliant UI just by using annotations on your OData service is absolute genius. OData Service for PDF handling – Since the end consumer was to be a SAPUI5 app, naturally I would wrap the generation of the pdf from the smartform in the GET_STREAM method of a media-enabled OData service.ģ. ![]() ![]() I would only add code to convert the smartforms to pdf (enter that handy little heaven-sent CONVERT_OTF function module!)Ģ. Smartforms – I reused the existing smartforms already developed and working as desired. The solution that I designed had the following components:ġ. ![]() ![]() My task was to achieve this whilst re-using as much of their existing software artifacts as possible. Some time ago I had to work in one such landscape where the client had invested heavily in smartforms but wanted to preview and download custom smartform documents from their shiny new SAP Fiori UI. With the evolution from Sapscripts to Smartforms to Adobe forms, as SAP developers we’ve had to be fluent in all these technologies because over time organizations have accumulated the older types of forms in their landscapes, and sometimes migrating these digital assets to say, Adobe forms is not always a priority (as long as it still works don’t touch it, they say). Over the years we have seen the proliferation of a range of print form technologies within the SAP domain.
0 Comments
Leave a Reply. |