From 3c70700602cb98dc966d87f37468246c31e7a5ab Mon Sep 17 00:00:00 2001 From: Rashmi Date: Fri, 21 Nov 2025 13:59:19 +0530 Subject: [PATCH 1/2] README changes for Delete issue --- README.md | 34 ++++++++++++++++++++++++++-------- 1 file changed, 26 insertions(+), 8 deletions(-) diff --git a/README.md b/README.md index 28803ffd..11734256 100644 --- a/README.md +++ b/README.md @@ -512,38 +512,56 @@ When the application is deployed as a SaaS application with above code, a reposi parameters: service: sdm service-plan: standard + + ``` +3. Add the similar code to your xs-security.json as shown below which enables to have your application specific and SDM roles coupled in to a role collection: + + ``` + "role-collections": [ + { + "name": "@@Sample_Bookshop_Role Collection@@", + "description": "SDM and application roles", + "role-template-references": [ + "$XSAPPNAME.admin", + "$XSSERVICENAME(sdm).SDM_User" + ] + } ``` + Here the name of role collection can be choice of yours and role template references can point to application roles. + "$XSSERVICENAME(sdm).SDM_User" should be added to use SDM and "sdm" name should be the instance name from mta.yaml. + + Note: If such a role collection is not configured then unauthorized user end up in misusing the attachments. -3. Build the project by running following command from root folder of incidents-app. +4. Build the project by running following command from root folder of incidents-app. ```sh mbt build ``` Above step will generate .mtar file inside mta_archives folder. -4. Deploy the application +5. Deploy the application ```sh cf deploy mta_archives/*.mtar ``` -5. Launch the application +6. Launch the application ```sh * Navigate to Html5Applications menu in BTP subaccount and open the application (nsincidents v1.0.0) in a browser. * Click on incident with title Solar panel broken. ``` -6. The `Attachments` type has generated an out-of-the-box Attachments table (see highlighted box) at the bottom of the Object page: +7. The `Attachments` type has generated an out-of-the-box Attachments table (see highlighted box) at the bottom of the Object page: Attachments Table -7. **Upload a file** by going into Edit mode and either using the **Upload** button on the Attachments table or by drag/drop. The file is then stored in SAP Document Management Integration Option. We demonstrate this by uploading the PDF file from [_xmpl/db/content/Solar Panel Report.pdf_](./xmpl/db/content/Solar%20Panel%20Report.pdf): +8. **Upload a file** by going into Edit mode and either using the **Upload** button on the Attachments table or by drag/drop. The file is then stored in SAP Document Management Integration Option. We demonstrate this by uploading the PDF file from [_xmpl/db/content/Solar Panel Report.pdf_](./xmpl/db/content/Solar%20Panel%20Report.pdf): Upload an attachment -8. **Open a file** by clicking on the attachment. We demonstrate this by opening the previously uploaded PDF file: `Solar Panel Report.pdf` +9. **Open a file** by clicking on the attachment. We demonstrate this by opening the previously uploaded PDF file: `Solar Panel Report.pdf` Delete an attachment -9. **Rename a file** by going into Edit mode and setting a new name for the file in the filename field. Then click the **Save** button to have that file renamed in SAP Document Management Integration Option. We demonstrate this by renaming the previously uploaded PDF file: `Solar Panel Report.pdf` +10. **Rename a file** by going into Edit mode and setting a new name for the file in the filename field. Then click the **Save** button to have that file renamed in SAP Document Management Integration Option. We demonstrate this by renaming the previously uploaded PDF file: `Solar Panel Report.pdf` Delete an attachment -10. **Delete a file** by going into Edit mode and selecting the file(s) and by using the **Delete** button on the Attachments table. Then click the **Save** button to have that file deleted from the resource (SAP Document Management Integration Option). We demonstrate this by deleting the previously uploaded PDF file: `Solar Panel Report_2024.pdf` +11. **Delete a file** by going into Edit mode and selecting the file(s) and by using the **Delete** button on the Attachments table. Then click the **Save** button to have that file deleted from the resource (SAP Document Management Integration Option). We demonstrate this by deleting the previously uploaded PDF file: `Solar Panel Report_2024.pdf` Delete an attachment ## Running the unit tests From c6082fc5d3cf992b73bd79f7c441817167ac73cf Mon Sep 17 00:00:00 2001 From: Rashmi Date: Mon, 24 Nov 2025 11:28:25 +0530 Subject: [PATCH 2/2] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 11734256..eeb1cf31 100644 --- a/README.md +++ b/README.md @@ -530,7 +530,7 @@ When the application is deployed as a SaaS application with above code, a reposi Here the name of role collection can be choice of yours and role template references can point to application roles. "$XSSERVICENAME(sdm).SDM_User" should be added to use SDM and "sdm" name should be the instance name from mta.yaml. - Note: If such a role collection is not configured then unauthorized user end up in misusing the attachments. +> **Note:** If such a role collection is not configured then unauthorized user end up in misusing the attachments. 4. Build the project by running following command from root folder of incidents-app. ```sh