👤 Post by _Nils_Lorenz_ (Integration):
"Hands-On - SAP Note: 3716130 Change in Root Certification Authority for SAP Default Certificate"
🔗 Link: community.sap.com/t5/integration-blog-post...
I've little practical BPA experience, but coming from ABAP workflow - this is a pretty basic rqeuirement!
👤 Post by ThomasReiss (by SAP):
"SAP User Experience Q1/2026 Update – Part 9: UI Design and Technology for Web and Mobile"
🔗 Link: community.sap.com/t5/technology-blog-posts...
Amen … And thank you DJ for leading the charge and being so passionate about bringing first principles / foundational knowledge to the SAP development ecosystem. A lifetime achievement !
CAP/RAP - The other similar but different "choice" (though both have their place IMO going forward)
If CAP UI5 repo's using latest UI5 libraries (iframed), SAP Task Center and UI Integration Cards were easily deployed on S/4HANA FLP, the internal user choice might be easy for most customers...
I wonder if SAP Build Work Zone will ever get the same My Home and personalisation capabilities from S/4HANA FLP and whether all the other SAP "portals" like SuccessFactors will ever allow/be capable of proper central embedding? e.g. Can it be a central Launchpad?
👤 Post by MioYasutake (by Members):
"Fiori Elements Navigation Patterns Showcase"
🔗 Link: community.sap.com/t5/technology-blog-posts...
Another good blog post using Claude AI (though I'm exploring Gemini CLI to avoid having multiple AI tools but guessing I need to make the switch to learn/leverage better off others)
Still get chills when listening and singing along to the proper Muppet version of rainbow connection! #randomstatementfortheweek
Are you even a CAP developer if you call it CAPM? Or maybe you are against SAP naming guidelines and why they didn't call it CAPM - which I can relate to (I'm looking at you SAP Cloud ERP Private)...
I once worked for a time directly with a business user but kept up IT processes,, and we would take "pilots" live with very few users to shortcut the additional governance that a wider roll out would require - wider roll out takes longer but every now and then, a pilot would stick the landing!
This looks really interesting, but it should be for customers and partners as customers need to know this even more importantly than partners to ensure they manage their BTP landscape!
So with that in mind - 2-Tier is best provided you tightly control and standardise your non-prod usage (though I personally don't love replicated Dev and QAS role mapping to BTP with all different to Prod) - This will definitely avoid additional maintenance activities though!
👤 Post by WouterLemaire (by Members):
"UI for the BTP Application Vulnerability Report"
🔗 Link: community.sap.com/t5/technology-blog-posts...
e.g You could transform <AD Prod Group Name>_CISDEV to <AD Prod Group Name> in CIS groups to maintain similar mappings for BTP and only include _CISDEV groups in your Dev instance. Everything else would be mostly identical (except CIS tenant in BTP)
CIS best practice? If you don't have SuccessFactors (and need for a CIS tenant per SF instance), the recommendation is 2-tier (against 3-tier landscape), but I feel 3-tier might be better to minimise diff of prod, dev and qas for solutions over time and minimise people touching CIS. Thoughts?
👤 Post by ThomasReiss (by SAP):
"SAP UX Q1/2026 Update – Part 4: SAP SuccessFactors (AI, Joule and More)"
🔗 Link: community.sap.com/t5/technology-blog-posts...
Really not talked about enough - and especially not necessarily understood by customers with BTP solutions...
👤 Post by ThomasReiss (by SAP):
"SAP UX Q1/2026 Update – Part 2: SAP S/4HANA Cloud Public Edition 2602 and SAP Fiori Launchpad"
🔗 Link: community.sap.com/t5/technology-blog-posts...
Classic it depends argument anyway really... But I always want people to consider who supports it after the consultants leave... SAP internal support teams which are always too small to hire more people need to already do too much... So even a new node.js dev needs to do multiple SAP roles to exist
There's also a lot of nuance and different angles to consider that is way beyond this platform - for example if the developer is like your skill level with some SAP background on a public cloud ERP, then that's a different story altogether
Agree to disagree until there are actual useful consumable APIs on most customer systems...
Noting, this is from the perspective of a business who get consulting companies in to do the work integrated with SAP typically and they need to support it after they leave... Personally, I love CAP with Building Blocks/FE though V2 odata ERP backends still suck!
I call them an enterprise developer which are usually consultants and need to leave something behind the customer can support as they are not a software company (yet)... But that is very rare indeed...
But not understand BTP specifics, ERP, and Fiori!
A good set of arguments here... There is an argument of finding good modern and production hardened ABAPer's in the future but for now, it seems harder to find good modern and production hardened CAP'ers, especially who instil the practices to keep CAP safely running/patched!
One more - camera is actually worse than naked eye (movement is super fast) and covers half the sky!
Big week in Tassie - Big Aurora Australis show now and Foo Fighters on Saturday in Launie!
