SAP Fiori elements: Frequently Asked Questions

[@abhishekanand3325]

Succinct explanations to some of the commonly asked questions . Great Job !!

[@SAPUXEngineering]

Hey Abhishek, We're glad you like the video! Kind regards, Conrad (SAP UX Engineering)

[@Rahul-wg7yj]

awesome video, such a crystal clear answer wow!!

[@CurSeDdAnceR]

Great stuff... Thanks for quick FAQs .

[@SAPUXEngineering]

Thanks, Rohit! We're glad you liked the content. Kind regards, Conrad (SAP UX Engineering team)

[@sumeetkumaryadav3380]

can we extend the standard fiori element app with draft functionality by adding new table in the cds. if yes ,can u share any document or link??

[@SAPUXEngineering]

Hey Sumeet, Do you intent to convert a non-draft application delivered by SAP to a draft application by CDS extension in the backend? I don’t think this can be achieved. SAP Fiori elements analyzes the metadata of the associated service to determine an application is draft/non-draft. If the metadata mentions that the application is based on a draft enabled service, SAP Fiori elements will be able to ensure the UI is built accordingly & orchestration between the server is switched to draft mode as well. As far as we understand, the backend application framework doesn’t provide any such extension capability to do this. Regards, Vinod (SAP UX Engineering)

[@sumeetkumaryadav3380]

@@SAPUXEngineering Hi, i want to extend the standard Draft enabled application with my custom table draft enabled cds view. if i create extension of standard transaction/consumption view and associate my custom table cds view with draft enabled annotation,so will it work??

[@SAPUXEngineering]

I am not aware of the implementation framework of the BO which is in the context. In general there is work already done to enable the node extension & metadata extension by which you could ensure the extended node is exposed as a navigation property. You could also extend the annotation by which you can get this extended node annotated as a UI.LineItem or UI.FieldGroup (based on the navigation properties cardinality). But I am not sure what the status is and if the BO that you are looking is implemented in framework that supports this. It is more a BO implementation framework question. From the SAP Fiori elements perspective, if the metadata/annotation is changed, we do re-templating of the application and ensure. This means, without any changes on the SAP Fiori elements application, the table/form will be rendered automatically next time you start your application. But unfortunately this would be a broken story, as you would expect by selecting an instance in the newly created table you would be navigated to the details page. To achieve this one needs to make some changes in the manifest of the application. As of now this is not supported, but we are working on this requirement in the hopes that it will become a capability soon. Hopefully you find this helpful! For faster answers next time, we recommend asking in-depth consulting-related questions on the SAP Community. Experts from around the world browse there every day, so you may get the answer you are looking for much more quickly. Kind regards, Vinod (SAP UX Engineering)