Sending notification to SAP build workzone from CAP app

[David21]

Hello everyone,

As the title suggests, I am trying to send notification from Cap app to build workzone. I have followed the following tutorial:

https://community.sap.com/t5/technology-blogs-by-sap/sending-notifications-from-sap-btp-applications...

The code seems to work fine but it's giving the following error:

 Also when I check the connection of my destination in btp, it returns 401 unauthorized.

 

[gregorw · Accepted solution]

Please use the CAP Plugin https://github.com/cap-js/notifications instead. But be aware that you have to use CAP 7 right now until Current peerDependency doesn't match cds 8 #57 is fixed.

[David21 · Accepted solution]

Appreciate the answer, just had a question about the setup. If i want to use it in production environment do i need to integrate the entire project in my app i.e. the util folder, notifytoRest.js file e.t.c or do i just add the plugin using npm Install and that will do it for me ?

[gregorw · Accepted solution]

I suggest you read through the CAP Plugin documentation: https://cap.cloud.sap/docs/node.js/cds-plugins

[David21 · Accepted solution]

It gives the following error: [notifications] - Sending notification of key: Default and version: 1 [persistent-outbox] - Emit failed { event: 'Default', cause: Error: NotificationType with key Default and version 1 does not exist at NotifyToRest.postNotification (/home/user/projects/Student/node_modules/@cap-js/notifications/srv/notifyToRest.js:35:21) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) at async Promise.all (index 0) at async NotifyToRest.handle (/home/user/projects/Student/node_modules/@sap/cds/lib/srv/srv-dispatch.js:65:21) at async ODataRequest.<anonymous> (/home/user/projects/Student/node_modules/@sap/cds/libx/outbox/index.js:286:18) at async ODataRequest.emit (/home/user/projects/Student/node_modules/@sap/cds/lib/req/context.js:58:9) at async ApplicationService.commit (/home/user/projects/Student/node_modules/@sap/cds/lib/srv/srv-tx.js:132:7) at async /home/user/projects/Student/node_modules/@sap/cds/libx/_runtime/cds-services/adapter/odata-v4/handlers/action.js:61:9 { unrecoverable: true } }

[gregorw · Accepted solution]

I would suggest you file an incident via the plugins GitHub repository.

[David21]

@MioYasutake 

yes the destination is working fine, the host URl did look odd to me as well but it is the one generated when i click on credentials . I was able to send the alert notifications from CAP app to build workzone using the following documentation:

https://help.sap.com/docs/cloud-portal-service/sap-cloud-portal-service-on-cloud-foundry/developing-...

The plugin works for me in the development env and the alert shows in the console, But it doesn't work in the production environment.

[David21]

I have read the documentation and added the plugin. I have used it in a test app that i have deployed on the build workzone but it is not creating notifications. The package.json looks like this:

 

And this is the service handler:

 Destination:

@gregorw 

 

 

[MioYasutake]

@David21

I was able to use the notification plugin successfully. The image in the link below is my destination setting.

https://qiita.com/tami/items/7c786f9d79a5fd157b24#2-destination%E3%81%AE%E7%99%BB%E9%8C%B2

I noticed a difference in URL. Please check if the host part matches the credentials generated in the Build Work Zone.