Closed (fixed)
Project:
Workflow Notifications
Version:
8.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
8 Jan 2018 at 02:27 UTC
Updated:
22 Jul 2025 at 17:14 UTC
Jump to comment: Most recent
Comments
Comment #2
saranya ashokkumar commented@johnv,
As soon as possible, I will update all your changes and let you know.
Comment #4
saranya ashokkumar commentedI have checked your patch and It looks fine. Thanks for your suggestion.
I have made some changes in routing.yml. Added param Converter for notification urls.
Because, Form
workflow_url_get_workflow()throwing error for workflow config pages Recoverable fatal error: Object of class Drupal\workflow\Entity\Workflow . So, I set Common parameters for all pages.Thanks!
Comment #5
saranya ashokkumar commented@johnv,
I have created issues for your suggestions. I will update my status in these below issues queues. Please review.
@todo: use WorkflowScheduledTransition::loadBetween();
@todo: use DEFINE CONSTANT.
@todo: add validation for email adresses.
$todo: use $transitions as parameter, and derive $trigger from that.
@todo: hide below code in WorkflowNotification::loadMultiple()
@todo: use $notifications[] = WorkflowNotification::LoadByProperties()
@todo: use $transition->isScheduled() instead? Or use a Factory.
@todo: next line has no effect.
@todo: the selection upon role is not working.
@todo ->condition('roles', $role, 'IN')
Comment #6
johnvNice,
if you have any problems with the workflow core methods/functions, I am happy to update them.
Also for example, the WorkflowScheduledTransitions::LoadBetween(), does not support the from_sid and to_sid filters. I can add that.
I also factored some functions and created a 'Trait', so there is less code. I guess you have found in in the code. (you need to use my latest dev version.)
What was your plan? To keep this as a separate module, or as a submodule of Workflow?
I guess a separate module is nicer. Also because we can incorporate the SMS notifications from Workflow SMS Notification
There is lots of features that can be enhanced in this field, so a separate module might be better.
See also https://www.drupal.org/project/scheduled_message
I'd be happy to be co-maintainer or let you co-maintain the main Workflow Module.
Your code looks very fine, perhaps we can make workflow_notifications.module file smaller by adding a helper class.
Comment #7
johnvWe may consider re-using the reknowned module Message. See the Message Stack documentation.
Comment #8
johnvOh, and I did review and test the complete module, except for the scheduled updates.
Comment #9
saranya ashokkumar commentedHi johnv,
I have added you as co-maintainer for workflow notification and I am also happy to be a co-maintainer for main workflow module.
Separate module is okay for me. I am ready to work on whatever you mention in comment #6. I will check all the link you mentioned above and let you know.
Comment #10
saranya ashokkumar commented@johnv,
Didn't get your point in comment #8. can you explain it?
Comment #11
johnvI meant that my review was not complete yet.
The hook_cron part was not tested by me.
Comment #12
saranya ashokkumar commentedHi johnv,
In comment #6, "we can incorporate the SMS notifications from Workflow SMS Notification" - will add the SMS notification features to this module or will use that module as dependent by calling API?
Comment #13
johnvSince the SMS notifications needs additional modules (SMS), it seems best to me that we create a submodule, as part of this module. Then the separate module workflow_sms_notifications can be removed.
See how workflow moduel works.
I found that is better maintainable in 1 module (main module + submodules).
Comment #14
saranya ashokkumar commentedCreated Issue for SMS Notifications Add SMS notifications Feature.
Comment #15
saranya ashokkumar commented@johnv,
I almost completed the sms notifications module as submodule, within two days I will update the status.
Comment #16
johnvok.
Comment #17
saranya ashokkumar commentedHi johnv,
Added SMS notification feature. please review!
Comment #18
johnvHi, It has been a long time!
I added many changed to the 3.0.x code base in [#i3534202] and issues from the same date.
Can you check and create a new version?
ITMT I will go through the issue queue.