Hello Experts,
In Cloud Foundry using business application studio I am creating a Custom UI5 application to trigger the workflow. I am referring the following blogs-
https://blogs.sap.com/2020/08/27/starting-workflow-from-custom-fiori-application-in-cloud-foundry/
https://blogs.sap.com/2020/08/31/enhancing-custom-application-as-workflow-task-ui-in-cloud-foundry/
I have created 2 applications -
App1) Workflow
App2) Custom UI5 app using which I am able to successfully trigger the workflow from UI5 app and I can see that item in My Inbox as well. PFB-
However, once the item is selected in My Inbox it is throwing the following error:
PFB code from my custom UI5 application:
1) xs-security.json
2) xs-app.json
3) mta.yaml
4) Service Instances in Cloud Foundry
I am not sure why My Inbox is unable to load the component of the custom ui5 application, which as a standalone app is working fine.
The url which My Inbox is trying-https://xxxxxxxtrial.cockpit.workflowmanagement.cfapps.eu10.hana.ondemand.com/nsPOCCreateInvoice/Component-preload.js
Standalone app url-
https://xxxxxxxtrial-dev-myapp-cap-createinvoice-approuter.cfapps.eu10.hana.ondemand.com/nsPOCCreateInvoice/Component-preload.js
Can you please help.
Thanks & Regards,
Shubham
Hello Shubham,
This is due to the existing restriction with Workflow Management SaaS application. You cannot view the user tasks based on SAPUI5 component from My Inbox application hosted in Workflow Management (see the restrictions here). For now only Forms are supported.
For that you have to use create the Launchpad module and add the My Inbox tile in it. You can download the content for Workflow Management FLP from here, just build and deploy it. Then you can use My Inbox and it will show the tasks.
Hello Shubham Dehariya,
this xs-app.json are from approuter or from that html5 module.
I can see, that you are probably using standard portal site from workflow management and therefore you are effectively bypassing your app router.
If that xs-app.json is defined on approuter level, then you are bypassing it also.
Add a comment