Contracts - String format and pattern

I just need a bit of guidance. In my agentless email data action, I want to ensure that the sender, reply-to, and recipient email fields are "valid", as in they contain something@[subdomain.]domain.suffix

What formatting is needed for this validation? Can you share an example?

In your input contract you can click on the pencil for a your sting input, and configure a Pattern of
.+@.+\..+
which indicates that the input should include stuff@stuff.stuff
Note: This is only really for use by the UI that you are using to configure what will be sent to the data action, I don't think that the data action will check that pattern at run time.

It also appears that Architect isn't enforcing the pattern in the UI, which I think is a bug and am asking the Architect team about. Other tools like Scripter might enforce it in the UI.

--Jason

This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.