topic Re: February Developer Challenge - CAP Plugins: Week 3 in Application Development and Automation Discussions

February Developer Challenge - CAP Plugins: Week 3

thomas_jung — Tue, 05 Mar 2024 16:14:06 GMT

If you missed week 1, you could find all the details: here
If you missed week 2, you could find all the details: here

Now that the challenge is complete: here is my sample solution: jung-thomas/dev-challenge-feb-2024: Developer Challenge February 2024 (github.com)

For this week's challenge we are going to mix things up. Week 1 and week 2 both focused on extending the protocol or version of service endpoints. This week we will use a plugin that has a completely different purpose. We are going use the Change Tracking plugin. This plugin both extends the data model and the Fiori UI automatically. It stores change history information, exposes it within our service and adds a Change History UI element to our Fiori application; all with extremely minimal effort on your part!

Your Task this week

The Change Tracking plugin provides out-of-the box support for automated capturing, storing, and viewing of the change records of modeled entities. All we need is to add @changelog annotations to your models to indicate which entities and elements should be change-tracked.

https://github.com/cap-js/change-tracking

Your task is to add change tracking to the Books entity and the Title attribute in your application.

To complete the challenge, post a screenshot of the Fiori UI for managing Books with the Change History with a change entry displayed.

Bonus 1: Add change tracking to the Books.Author association. However, don't display the unique ID when the association is changed. Instead, the change log should record and display the Author Name.

Re: February Developer Challenge - CAP Plugins: Week 3

brunonalon — Wed, 21 Feb 2024 17:01:56 GMT

Re: February Developer Challenge - CAP Plugins: Week 3

satya-dev — Wed, 21 Feb 2024 18:01:15 GMT

here is my submission
I changed the stock and price.

Re: February Developer Challenge - CAP Plugins: Week 3

stickman_0x00 — Wed, 21 Feb 2024 22:16:59 GMT

Re: February Developer Challenge - CAP Plugins: Week 3

Ruthiel — Thu, 22 Feb 2024 00:38:23 GMT

Hello!
Someone with this issue when trying to access the 'Managing Books' UI?

Re: February Developer Challenge - CAP Plugins: Week 3

smok1 — Thu, 22 Feb 2024 00:56:59 GMT

Here's mine:

Re: February Developer Challenge - CAP Plugins: Week 3

brunonalon — Thu, 22 Feb 2024 01:57:07 GMT

This is because the admin service requires an admin user.

You can just remove this or create a mock user with an admin role.

Re: February Developer Challenge - CAP Plugins: Week 3

govardhansahil — Thu, 22 Feb 2024 06:41:46 GMT

Re: February Developer Challenge - CAP Plugins: Week 3

Alpesa1990 — Thu, 22 Feb 2024 08:42:27 GMT

Very useful plugin!

Re: February Developer Challenge - CAP Plugins: Week 3

Ruthiel — Thu, 22 Feb 2024 10:12:59 GMT

Thank you very much Bruno for your precious help!
I could complete successfully the week:

Re: February Developer Challenge - CAP Plugins: Week 3

thomas_jung — Thu, 22 Feb 2024 10:41:29 GMT

Or you can use the built in mock user of ‘Alice’ - no password. https://cap.cloud.sap/docs/node.js/authentication#mock-users

Re: February Developer Challenge - CAP Plugins: Week 3

ajmaradiaga — Thu, 22 Feb 2024 11:25:00 GMT

I added weights to the heights 🙂

Really cool plugin!

Re: February Developer Challenge - CAP Plugins: Week 3

qmacro — Thu, 22 Feb 2024 12:13:44 GMT

Main task: showing change tracking of the Books entity's title element:

Bonus: showing change tracking of the Books entity's author element, but ensuring that the value of the name element from the Association to Authors is shown, rather than just the ID from the managed association's foreign key field (author_ID):

Re: February Developer Challenge - CAP Plugins: Week 3

qmacro — Thu, 22 Feb 2024 12:18:26 GMT

OK folks, so how many of you here went for the beautiful approach that CAP offers, moreover _encourages_, which is the ability to separate concerns?

In other words, who annotated the definitions in `db/schema.cds` directly, and who created a separate new CDS file and used the `annotate` directive (https://cap.cloud.sap/docs/cds/cdl#the-annotate-directive)? @thomas_jung @ajmaradiaga and I would love to know!

Re: February Developer Challenge - CAP Plugins: Week 3

smok1 — Thu, 22 Feb 2024 13:27:22 GMT

100% in a separate srv/change-tracking.cds

Re: February Developer Challenge - CAP Plugins: Week 3

eduardomonteiro20 — Thu, 22 Feb 2024 16:23:59 GMT

Re: February Developer Challenge - CAP Plugins: Week 3

Alpesa1990 — Thu, 22 Feb 2024 17:44:05 GMT

I have annotated the definitions directly in schema.cds but I guess it is not the best practice 😂 I´m going to separte it in two files...

Re: February Developer Challenge - CAP Plugins: Week 3

MioYasutake — Thu, 22 Feb 2024 20:32:36 GMT

Re: February Developer Challenge - CAP Plugins: Week 3

Former Member — Thu, 22 Feb 2024 20:50:05 GMT

Re: February Developer Challenge - CAP Plugins: Week 3

ajmaradiaga — Fri, 23 Feb 2024 04:41:12 GMT

I did it in a separate file 🙂 I was about to paste an image but realised that that will give away the answer haha