In the standard delivered Gateway Service for working with Launchpads there is a function import that updates the frequently used counter to whatever the current counter is +1.
I have a requirement to provide a button on the UI so that the end user can reset the counter. Theory being, there job may change and while they may have access to certain applications that are in their frequently used list, they may not need them as frequently any longer and they should have the option to remove them.
It would have been fabulous to redefine this standard delivered service and make the change, but given the current class inheritance and SAP's unwillingness to unmark a super class as final, this is not possible.
We are writing a new gateway service whose sole pupose is to update this counter to 0.
Most of the code to accomplish this can just be copied from existing classes.
I am struggling with how this should be structured.
I had put this together in an update entity method. However, this doesn't seem correct since we are basically passing a reference id like:
04ZESS0DZESS_MYHR_FPM20005056A51C9D1EE3AFFEA106D591C3EA
And expecting the code to update some obscure table with a value of 0 for the counter.
1) Is this a correct approach?
2) Should this be done in a function import given that we aren't really updating the entity per se but rather some end user personalization attribute?
3) Is there an issue with having a Gateway Service that is comprised of nothing but one function import?
Any thoughts on this requirement are appreciated, perhaps we are heading down the wrong path altogether....