This is specifically about the new rollout of the Cockpit and Task Real Time Rule action, but really this should be treated more as an example than a request to just fix one thing, hence the generic title.
The fact that Real Time Rules doesn’t support Custom Events is a pretty important detail that should have made it directly into the release notes. Custom events are supported on other action types so there wouldn’t be a reason to think they would not be supported and should be called out here:
If you follow the link to Events in Real-Time Rules you scroll down and see this:
No particular call out that Custom isn’t supported, it’s just not listed. It really should be explicitly mentioned it is not supported.
In my instance however, I have the option for custom:
Maybe they forgot to add it to the docs as a supported action? After all, the fact that it’s being rolled out incrementally was added later.
It’s not called out anywhere but it’s here on my list. No indication at this point it wouldn’t work. Until you try and add a field, then you see this:
I’ve already made a post here about it and I hope it’s already on the roadmap, but clarity in documentation is super important and I’m just not seeing that. There’s also discrepancies around the actual functionality of some fields in an object which isn’t a great place to be either.
An enterprise level platform needs accurate, reliable, and trustworthy documentation. With a quarterly release, time and resources need to be baked in to make sure that that happens.
