I added a new table called the Emergency Task table, and I extended it to the Service Task. The reason behind this creation is that I saw that the Service Task is an OOB table; it was created by the system, and I think it would be hard to customize it in the future.
I also edited the target tables of "Response Dispatch Flow" and "Response Dispatch Subflow" from Service Task to Emergency Task.
I also check if there are notifications that might be affected by these changes, and I don't think all notifications created are WF-related.
Testing is also done on my end, and it works just as before, although the service task WF is still attached when the record in the emergency table is created. I'm planning to create a new WF after this pull, or do I need to fix it first?
Hi Hacktoberfest team,
Changes on this pull request:
I added a new table called the Emergency Task table, and I extended it to the Service Task. The reason behind this creation is that I saw that the Service Task is an OOB table; it was created by the system, and I think it would be hard to customize it in the future.
I also edited the target tables of "Response Dispatch Flow" and "Response Dispatch Subflow" from Service Task to Emergency Task.
I also check if there are notifications that might be affected by these changes, and I don't think all notifications created are WF-related.
Testing is also done on my end, and it works just as before, although the service task WF is still attached when the record in the emergency table is created. I'm planning to create a new WF after this pull, or do I need to fix it first?
Thanks team.