Error Codes and Messages - saayam-for-all/docs GitHub Wiki

In Saayam For All applications - web app and mobile app - all messages - whether it is a positive or negative/error message, should have this format: SAAYAM-:. E.g. SAAYAM-1: New help request creation is successful. Request with ID has been created.

Error message: 1. Error code 2. Error message 3. How the end user can resolve this error if this is an end user error 4. If this is a server side error, who to contact to get this error fixed. E.g. SAAYAM-251: New help request creation failed. Request subject contains foul language. Please fix the language and resubmit the request.

All end user facing messages need to support I18N (Internationalization) and L10N (Localization)

We divide the error/message codes into following ranges:

  • Front end client codes e.g 0-999

    • web app codes 0-499
      • Positive messages 0-249
      • Negative messages 250-499
    • mobile app codes - 500 - 999

  • Backend messages codes e.g 1000-5000

  • Lambda function codes 1000-1199

  • Volunteer micro service codes 1200-1399

  • Request micro service codes 1400-1599

  • ML micro service codes 1600-1799

Scrum Meeting - 4/22/2025

Minutes: 10 AM - 11:19

0.5 MVP Static Pages - identify mistakes in pages & receive feedback sayaamforall.org (developing home page) Architecture:

How are you developing application at sayaam for all ? GitHub devsecops

2 regions - North Virginia & Ireland In webapp javascript stays in one place

2 Goals for test-salaam.netflify.app Impress users who visit the page (Inform users about the organization- what we are good at & what we do) Receive donations & join the organization

Tasks to work on:

0.5 MVP Markups The YouTube video playing at the home page - https://www.youtube.com/watch?v=9CBLVoSSuwM&ab_channel=AlgoWorld

Marketing required on the home page: A good logo Convert it into a more interactive page

The toolbar is not visible on the contact page of the website

***Format for hhttps://deploy-preview-514--test-saayam.netlify.app/ page Example: https://www.riverislands.com/?utm_source=GoogleRiverIslandsWebsite&utm_medium=SearchAd&utm_campaign=SocialMediaRiverIslands&gad_source=1&gbraid=0AAAAAoZu_EUENFbObUKd61PnAo1gI5shC&gclid=Cj0KCQjw_JzABhC2ARIsAPe3ynp861M7iBOMopC7W-6KdCQbuFkQSpmTPZaTqrxJWOEdjZkR0g04NvQaAtuvEALw_wcB Functionality: Trying to achieve the picture to stop - cruise mode

Prod Meeting Notes: Finalize Names Match volunteering skills page Should be there in our MVP Review each text (such as essentials)

Wiki Documentation Process for Each Page Documentation Format: Use a three-column wiki table format:

Serial Number – Unique identifier for each step.

Page Name – The section of the page.

Details / User Story – Description of the control, expected behavior, and use case.

✅ Purpose: Create a clear and complete reference for every page in the application.

Used when filing bugs or analyzing issues, e.g., “In step 2 of ‘Create Help Request’, the system doesn’t behave as expected.”

Wiki should not refer to random text but to specific steps and controls using serial numbers.

Roles & Responsibility: Product Managers and Business Analysts must:

Go through every page and control.

Document how each field should function.

Describe the expected interaction by the end user.

Ensure the user story is clear for each field.

⚠️ **GitHub.com Fallback** ⚠️