Skip to content
This repository has been archived by the owner on Jan 20, 2024. It is now read-only.

Custom response messages for validate route #3

Open
eliotharper opened this issue Apr 23, 2020 · 3 comments
Open

Custom response messages for validate route #3

eliotharper opened this issue Apr 23, 2020 · 3 comments
Assignees
Labels
documentation Improvements or additions to documentation enhancement New feature or request

Comments

@eliotharper
Copy link

In the April 2018 release, support for custom validations were added to response payload for the validate route. However, I understand this is not actually true. Are you able to add this support? It's a common use case that you want to serve back a descriptive error message to the user (with a reason) in this scenario where validation fails.

@smashew
Copy link
Contributor

smashew commented Apr 23, 2020

I'm going to do some research and get back to you on this.

@smashew
Copy link
Contributor

smashew commented Apr 24, 2020

So we did some looking internally. The information that is passed back does not get persisted anywhere and is not connected up in the UI such that a user would be able to view the information. The Information does go into Developer Log, but that wouldn't immediately be actionable for a user.

We are taking a look internally about how we could satisfy this use case and what that process would look like.

I'd like to keep this issue open so we can use it as a method of posting updates until we develop a plan and release software that enables this use case. :)

@smashew smashew added documentation Improvements or additions to documentation enhancement New feature or request labels Apr 24, 2020
@smashew smashew self-assigned this Apr 24, 2020
@fib-at-isobar
Copy link

Hello @smashew,
do you please have any news on this?

DougMidgley pushed a commit to DougMidgley/sfmc-example-jb-custom-activity that referenced this issue Jun 21, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
documentation Improvements or additions to documentation enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants