And no doubt the icons for all will be jewels 💎💎💎

But they have to be dreaming of they think anyone will trust SAP tooling that recommends implementing SAP product. Even if it makes it easier.

I feel ya! The 99+ unread email flag is a permanent fixture on my inbox... And I'm currently sitting at about double your number 🤪

Would be great to see some SAP sourced discussion... Because that's missing everywhere except in person.

Bets on this being the last year we hear the WalkMe name and next year it's just "Joule".

How many... Was it a 4 digit number? This would be only way to inbox zero for me.

Very much so... And don't you think that Joule is going to want to leverage that?

Besides how long has SAP ever had a product acquisition without doing a rebrand?

WalkMe tech already extracted from previous browser plug in tooling and directly implanted into SAP Cloud Apps. So it's more the "let me show you how to do that" tool in the cloud app than "WalkMe". There is an obvious clash between Joule and that.

Joule "everywhere" edition (the product formerly known as WalkMe)

If WalkMe isn't rebranded into Joule and repackaged as the front end for all Joule interactions in next year, I will be surprised. You can't have both, it doesn't make sense.

The customer stories, as always, more inspiring. The concept of the "suite" sharing info to enable better AI very much a hand waving exercise it seems to me so far.

You should be able to have multiple source systems populating the BTP sub accounts, the email only need be unique per source. Same email for different IdPs seems to work.

And since employees are using Entra to log on, no need to have unique emails to allow password reset using email address...

But also using external learners, that do.... Bit of a bugger!

Will need to check if there is a workaround to that situation

Idea is that user has full on different Entra user id for privileged access and uses this to log into SAPSF/IAS to do admin like tasks. Which makes sense as can use additional logging/MFA/risk based access config/etc to control these users access. But they still have the same email address...

I think this is correct, but it might be a roadmap item to allow different uniqueness configuration for sub populations within IAS.

Probably worth clarifying what @hardingmatt.bsky.social means here by platform and application users as this is interesting use case.

Basically, yes, the standard way to populate users into the IAS attached to SAP SuccessFactors is to replicate them using the standard IPS replication from SAPSF to IAS, SAPSF tools like the embedded SAC, expect certain attributes to be populated in SAML asserts that Entra doesn't know about.