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

The notification email not sending to the counterparty while creating a contract #377

Closed
mtmsuhail opened this issue Aug 10, 2020 · 2 comments
Assignees
Labels
status:QA Dev work is completed and issue is up for QA testing

Comments

@mtmsuhail
Copy link

Expected Behavior

The notification email should be sent to the counterparty while creating a contract

Current Behavior

The notification email not sending to the counterparty while creating a contract

Possible Solution

There is no configuration related issues present in test.jur.io, The issue seems to be present after the commit of cef146b on June 3rd 2020.
cef146b#diff-3a328648844ad094660e2be808ea1c2d

I am getting emails when I roll back the changes of rest/app/Models/Traits/ActivitiesTrait.php.

Hint: The code is expecting status_code of 36 or 39, but in my case the status_code is 0 or 1

@marcomarasco
Copy link
Contributor

marcomarasco commented Aug 21, 2020

@MirelXhafa @mtmsuhail
The commit you referring seems related to a fix for multiple records in Activities, that as been created after JBP Connex migration. Since Activites are triggers for Notifications, in order to handle those properly, Activities should be inserted at the proper moment due several conditions (the ones you see in commit updates).

I'm not sure about it, but until @frugge can have a look at this, you should try to return always a value instead of null at rest/app/Models/Traits/ActivitiesTrait.php on line 67.

Maybe you can return $activityCreated at line 67 and instead return null after line 63 (once $activityCreated->delete(); has been deleted)

@marcomarasco
Copy link
Contributor

@mtmsuhail @MirelXhafa @tyagishuchi1 did you have any news on this?

MirelXhafa added a commit that referenced this issue Aug 25, 2020
@mtmsuhail mtmsuhail added the status:QA Dev work is completed and issue is up for QA testing label Aug 26, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status:QA Dev work is completed and issue is up for QA testing
Projects
None yet
Development

No branches or pull requests

4 participants