Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Front End Validation for Email Regex Validation #25

Open
gutsy opened this issue Jul 8, 2020 · 12 comments
Open

Front End Validation for Email Regex Validation #25

gutsy opened this issue Jul 8, 2020 · 12 comments
Labels
enhancement New feature or request good first issue Good for newcomers

Comments

@gutsy
Copy link
Contributor

gutsy commented Jul 8, 2020

Followup on #14

Submitting form currently will show an error message and prevent it from sending data to Sign, but there is no indicator before the form is submitted.

@gutsy gutsy added enhancement New feature or request good first issue Good for newcomers labels Jul 8, 2020
@umuur
Copy link

umuur commented Jul 8, 2020

Hi there, can I claim this issue?

@gutsy
Copy link
Contributor Author

gutsy commented Jul 8, 2020 via email

@umuur
Copy link

umuur commented Jul 16, 2020

@gutsy I couldn't move forward due to #27. Do you have any idea about it?

@gutsy
Copy link
Contributor Author

gutsy commented Jul 16, 2020

@umuur I ended up just running it locally, I haven't touched Digital Ocean yet. Did you make sure that the required options were set up in the config file? Are there any errors coming back from when it tries to get the workflows?

@umuur
Copy link

umuur commented Jul 16, 2020

@gutsy I've just tried locally, I'm getting the error below:

(node:882) UnhandledPromiseRejectionWarning: FetchError: invalid json response body at http://127.0.0.1/api/rest/v5/workflows reason: Unexpected token < in JSON at position 0
    at /mnt/c/Users/umurd/dynamic-workflow/node_modules/node-fetch/lib/index.js:272:32
    at <anonymous>
    at process._tickCallback (internal/process/next_tick.js:188:7)
(node:882) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 2)
(node:882) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

@gutsy
Copy link
Contributor Author

gutsy commented Jul 16, 2020

is this set on the config file?

x-api-user: ""

Can just be an empty string.

@umuur
Copy link

umuur commented Jul 16, 2020

@gutsy it was x-api-user: ""

I tried x-api-user:"email:[email protected]" but I got the same error.

@gutsy
Copy link
Contributor Author

gutsy commented Jul 16, 2020

And you have the integration property set under enterprise?

@umuur
Copy link

umuur commented Jul 16, 2020

@gutsy Yes, It is set to my Adobe Sign integration key which has all privileges.

@gutsy
Copy link
Contributor Author

gutsy commented Jul 17, 2020

I am not sure, then. @nwcell @gkolluri could either of you help troubleshoot this with him? I haven't seen this error yet.

@umuur
Copy link

umuur commented Jul 18, 2020

Adobe Sign Integration Key which I'm using is belongs to trial account. Does this can be the issue?

@nwcell
Copy link
Contributor

nwcell commented Jul 19, 2020

@umuur, can you share the payload that you are getting in response w/ that error?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

3 participants