Forum Discussion
Hi mfeltscher
I wouldn't be able to illustrate the inner workings of the platform, this would be more a question for our engineering department. Even so, I am not sure they would be sharing internal platform implementation details, unless they form part of a standard platform customization point.
I understand what you say, however there is no explicit feature in the UI that allows a user to mark a notification read or unread. Also, the REST API does not currently offer a call to retrieve unread notifications (the question was also asked here).
Kind Regards,
Hi PaoloT
Could you please get in touch with the engineering department to get some more information on how this is done by Lithium?
Thanks,
Moreno
- PaoloT11 years agoLithium Alumni (Retired)
Hi mfeltscher
For this type of request, I suggest you get in touch with our Support department - however, as I have mentioned I am not sure whether internal implementation details will be shared externally.
Kind Regards,
- cblown11 years agoBoss
Just a question on this topic.
Wouldn't it make sense for Lithium Engineering to build out a full API for Notifications first and then simply build the out-of-the-box component via this API rather than directly coding them? What is the reasoning here, other than it being much faster to program?
Custom Components and OOTB components should be 1:1.
Looking at this idea here -- http://community.lithium.com/t5/Product-ideas/quot-API-first-quot-development/idi-p/79260 it supposed to be partially delivered - and V2 looks to be going in this direction.. albeit slowly.
As a principle this idea has huge merit, Lithium should be sitting up and taking note of just how many users are getting "not via the API" responses here in the Community.
Thanks
Related Content
- 11 years ago
- 11 years ago
- 7 months ago
- 10 months ago