Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Remove only allowing edit of Subscription when form is published.

  2. Move the Event Subscription on form edit to below where the option is selected otherwise you do not see the panel appear/disappear

  3. Add in events for status change and assignment


Friday March 8, 2024 - The previous fix introduced an issue where the name of the submit button api name has to = submit. I am investigating another fix to not depend on the name of the button to be submit. The following property name is wrong and needs to be submit in order for my code to work.

...

I have also created some documentation for the behavior fix of the copy submission in:
Expected Behaviour - Copy Submission should override submission status and submit status


Friday March 1, 2024 - Pull request fix for the allow edit functionality not calling the event when updating an existing submission that has been saved as a draft. There is a new issue found for the allow copy functionality that will be a bug indicated around setting the submitted boolean back to false.
https://github.com/bcgov/common-hosted-form-service/pull/1295 - The QA is now passed on this ticket from the Unity Side also fixes an issue:

Observations:

The bug is that if you create two forms in a row in Chefs and enable the "event subscription" feature for both forms, then in the second form the event subscription will be  already present in the event subscription text fields but you're unable to save.

High Level Purpose: Have CHEFS store endpoint urls/tokens in a postgres table. CHEFS can then have event driven api restful callout endpoints. The initial subscribed event will be for the form_submission. CHEFS will use these endpoints to make restful call outs to approved systems. The ability to create subscriptions will be restricted to government systems.

...