How do we create a connected community that can learn and improve together?

• Sharing our experiences is an important piece of this puzzle, and Weeknotes are an accessible way to achieve this

• The Weeknotes goal is to share lessons learned and product updates using a consistent and easy-to-scan template every two weeks

• They are a first step to working in an open way that can enhance learning and continuous improvement
  

📙 CHEFS Team Weeknotes 2 

Creating a connected community that can learn and improve together  

Please share your comments and thoughts on the work below and how we can enhance the Weeknotes experience. We are listening. 

Has been fixed  

• Follow the guidelines outlined in the Security Threat and Risk Assessment (STRA) Statement of Acceptable Risks (SoAR) to ensure safety. 

New to the user  

• Enhancing transparency for our users by consistently monitoring and reporting across all channels. 

Has been improved 

• Enhanced support for multiple languages, making the platform more accessible and user-friendly for diverse speakers.  

  • You can find the details in our TechDocs Form Multilanguage. 

Future focus 

• The map component is nearing its release and now features polylines for enhanced functionality. 

  • For more information, please refer to the current documentation on our Map Component. 

• Tenancy Groups enable product teams to designate which team members can change their product's configuration. 

  • You can find an overview of the Tenancy Group. 

  • You can view a recorded discussion about the Tenancy Group from our Architecture Forum. 

Thank you for Collaborating 

Thanks to @Russell Vinegar's suggestions, we have made updates to enhance our Weeknotes. 

• Prevent Post-Submission Edits: Created a Weeknotes posting checklist 

• Shorter Titles:  

  • Weeknotes #1: 15.75 words per title 

  • Weeknotes #2: 3.2 words per title 

Want to create Weeknotes for your team? Use our Weeknotes Structure (below) and start sharing today!

📙 CHEFS Team Weeknotes 1

1. Has Been Fixed (Broke No More): Broken things that we fixed  

• The search tool for adding team members now works with BCeID users using just 4 characters in the search. 

• Fixed missing tools in our software updates to keep deployment systems working smoothly. For more information on JIRA, click here. 

• All backups now run on BCDevOps version 2.9.0, and verified backups have been successfully completed. For more information on JIRA, click here. 

2. New To The User (Brand New, Secondhand): These are the most exciting because they are new

• Users can now customize table columns on the previous submissions page, and these settings are saved, per the Ministry of Health's request in FIDER. For more information on JIRA, click here. 

• A new feature lets Form Designers call an External API securely without storing sensitive data like passwords or tokens in plain text. For more details, click here. 
  

3. Has Been Improved (Continuous Improvement Bucket): A conversation about anything and everything that makes the product faster and better 

• Thanks to the Ministry of Energy, Mines and Low Carbon Innovation (EMLI) and Responsible Mining and Competitiveness Division (MCAD), the original developers of this script, a standalone Python script is now available for downloading submissions with an API key. 

• The front-end Vue components have been upgraded to the Composition API for better organization, flexibility, and handling of complex components. 

• Cypress scripts were created to test form creation, role visibility, submissions, and status updates by mimicking user actions. 

4. Future Focus (Boldly Go Where No Common Component Has Gone Before) Feedback on things we have started building  

• The new map tool lets you place pins, draw circles, or outline areas to show locations or collect geographic information. To test this feature, click here. To look at the techdoc on Git Hub, click here. 

• We held our first Common Components Architecture Forum this quarter; click here for more information, including a summary of the morning and afternoon sessions. 
  

Want to create Weeknotes for your team? Use our Weeknotes Structure (below) and start sharing today!