Summary:
- The system now provides more detailed and accurate error messages when credit checks fail or return incomplete data.
- This change helps to identify the root cause of errors, such as system errors, credit freezes, or blank credit reports.
- The new error reporting system prioritizes error types to provide more informative messages.
- This improvement enables better troubleshooting and resolution of issues related to credit checks.
- The system now returns a specific error code when a credit report is completed but contains no useful data.
Changelog:
Added:
- A new function to resolve and report errors related to credit checks.
Changed:
- The way the system handles and reports errors when credit checks fail or return incomplete data.
Fixed:
- Issues with incomplete or inaccurate error messages for credit checks.
Removed:
- None
Summary:
- The system can now receive and process failed payment notifications from GHL.
- Failed payment information is stored for future reference and auditing purposes.
- The system validates the format of incoming payment notifications to ensure they are correct.
- The system provides clear feedback when it successfully stores a failed payment notification or when it encounters an error.
Changelog:
Added:
- The ability to receive and store failed payment notifications from GHL.
Changed:
- The system's logging capabilities to include failed payment notifications.
Fixed:
- None
Removed:
- None
Summary:
- Improved handling of credit report errors, including "Credit Frozen" and "System Error" states
- Enhanced retry mechanism for fetching credit reports, reducing the likelihood of errors
- Updated industry field naming convention for consistency across the application
- Streamlined user experience for credit report updates and error handling
Changelog:
Added:
- Retry mechanism for fetching credit reports to handle temporary errors
Changed:
- Industry field naming convention from "industryTypeC" to "industryC" for consistency
- Credit report error handling to use a more robust and centralized approach
Fixed:
- Issues with credit report updates, including "Credit Frozen" and "System Error" states
- Inconsistent retry mechanisms for different error types
Removed:
- Redundant code and variables related to outdated credit report error handling approaches
Summary:
- The system now provides more accurate responses to user queries by considering strong knowledge base matches.
- Non-Q&A intents are handled more effectively, with canned responses provided only when no strong matches are found.
- The knowledge query engine is more robust, with better handling of configuration settings.
- The system ensures that required configuration settings, such as the Redis host and port, are properly set up before proceeding.
Changelog:
Added:
- Strong match detection for knowledge base queries
Changed:
- Handling of non-Q&A intents to provide more relevant responses
- Configuration setting checks to ensure required settings are present
Fixed:
- Issue with incomplete configuration settings causing errors
Removed:
- Dependency on a single Redis URL configuration setting, replaced by separate host and port settings
Summary:
- The system now uses predefined lists for industry and state fields, making it easier to select valid options.
- Users can no longer enter free-form text for these fields, reducing errors and inconsistencies.
- The update improves data quality and makes it easier to analyze and report on industry and state information.
- The change also enhances the overall user experience by providing a more intuitive and guided data entry process.
Changelog:
Added:
- Predefined lists for industry and state fields to improve data quality and consistency.
Changed:
- Industry and state fields now use dropdown menus with predefined options instead of free-form text entry.
Fixed:
- Reduced errors and inconsistencies in industry and state data entry.
Removed:
- Free-form text entry for industry and state fields, which was prone to errors and inconsistencies.
Summary:
- The system now uses a standardized list for business states, making it easier to select and manage states.
- A similar standardized list is used for business industries, improving data consistency and reducing errors.
- The changes improve the overall user experience by providing a more intuitive and efficient way to select business states and industries.
- The updates also enhance data accuracy and reduce the risk of incorrect or incomplete information.
Changelog:
Added:
- Logging capability for autosave features to track and resolve potential issues.
Changed:
- Business state and industry fields now use enum types, providing a more structured and standardized approach to data selection.
Fixed:
- No specific fixes are included in this update, but the changes improve overall system reliability and data integrity.
Removed:
- No features or functionality have been removed in this update.
Summary:
- The system now ensures that State and Industry fields can only accept specific, predefined values.
- This change enhances data consistency and reduces errors caused by invalid or inconsistent input.
- Users will now select from a list of valid options for State and Industry, making it easier to enter accurate information.
- The overall quality of the data collected will improve, allowing for better analysis and decision-making.
Changelog:
Added:
- Drop-down menus for State and Industry fields to guide users in selecting valid options.
Changed:
- The input type for State and Industry fields to restrict input to predefined values.
Fixed:
- Potential issues with data inconsistencies and errors due to invalid input.
Removed:
- The ability for users to enter free-form text for State and Industry fields, which could lead to inaccuracies.
Summary:
- The system now tracks when the onboarding status of a lead is updated.
- This update allows for more precise automation of workflows based on the timing of status changes.
- Automated reminders can be sent at specific times after a status change, improving follow-up efficiency.
- The change enables better management of lead onboarding processes by providing a clear timeline of status updates.
Changelog:
Added:
- The ability to track the date and time of onboarding status changes for leads.
Changed:
- The lead onboarding process now includes automated tracking of status updates.
Fixed:
- None
Removed:
- None
Summary:
- The system now logs which method was used to find a lead, making it easier to track and understand the lead search process.
- Lead search logs now include more detailed information, such as the match method used to find the lead.
- The lead search process has been updated to try multiple methods to find a lead, including searching by email, phone, and GHL contact ID.
- The system now provides more accurate and detailed logging of lead search results, including the lead ID, GHL contact ID, and match method.
Changelog:
Added:
- Logging of the match method used to find a lead
Changed:
- Lead search process to try multiple methods to find a lead
- Lead search logs to include more detailed information
Fixed:
- None
Removed:
- None
Summary:
- The system now accurately reflects the status of canceled subscriptions.
- Canceled subscriptions are properly marked to prevent further payments.
- The update ensures consistency in handling canceled subscriptions.
- This change improves the overall management of subscription statuses.
Changelog:
Added:
- A new status update for canceled subscriptions to prevent payment events.
Changed:
- The way the system handles canceled subscriptions for consistency.
Fixed:
- Inconsistent handling of canceled subscriptions.
Removed:
- None
Summary:
- The system now keeps the loading screen active after payment until the credit report pull is complete, preventing the paywall from appearing prematurely.
- This change improves the user experience by reducing flashes of the paywall and providing a smoother payment process.
- The system now correctly handles the payment return pending state, ensuring that the loader remains active until the credit report pull is finished.
- The payment return pending flag is now cleared only when the credit report pull is complete or when payment fails, ensuring that the system remains in the correct state.
Changelog:
Added:
- A new state to track whether the system is reloading after payment.
Changed:
- The payment return pending flag is now cleared only when the credit report pull is complete or when payment fails.
- The system now waits for the credit report pull to finish before clearing the payment return pending flag.
Fixed:
- The paywall no longer flashes prematurely after payment.
- The system now correctly handles the payment return pending state.
Removed:
- The automatic clearing of the payment return pending flag after a 5-second delay.
Summary:
- The dashboard now loads more efficiently, reducing the time it takes to display user information.
- The system no longer displays a credit report processing message with unnecessary details.
- Payment return delays are now handled more effectively, improving the overall user experience.
- Access to certain routes is now enforced more consistently, ensuring that users can only access authorized areas.
Changelog:
Added:
- A delay to ensure that payment return webhooks can settle before proceeding with user requests.
Changed:
- The way the system handles credit report processing, removing unnecessary message details.
- The payment return delay mechanism to clear the pending flag after the delay.
Fixed:
- Inconsistent access enforcement for certain routes, ensuring that users can only access authorized areas.
Removed:
- Unnecessary code related to subscription status and payment return pending checks.
Summary:
- The system now displays workflow runs related to a lead, including those triggered on the lead itself and on related modules.
- Users can view the type of relation between the lead and the workflow run, such as direct or related.
- The system provides more detailed information about each workflow run, including the date it was entered and modified.
- The new functionality improves the visibility of workflow runs and their relationships to leads, making it easier to track and manage workflows.
Changelog:
Added:
- A new field to display the type of relation between a lead and a workflow run.
- A new function to retrieve workflow runs related to a lead, including those triggered on related modules.
Changed:
- The layout of the leads subpanel to include the new relation field and other relevant information.
- The way the system retrieves data for the leads subpanel to include related workflow runs.
Fixed:
- No fixes are included in this update.
Removed:
- No features or fields were removed in this update.
Summary:
- A new knowledge base feature has been added to the system, allowing users to ask questions and receive answers.
- The knowledge base includes a chatbot that can respond to user queries.
- An admin panel has been created for managing knowledge base entries, including adding, editing, and deactivating entries.
- A feedback system has been implemented, enabling users to provide feedback on the knowledge base entries.
- A jobs page has been added to track upload and sync processing history.
Changelog:
Added:
- Knowledge base feature with chatbot functionality
- Admin panel for managing knowledge base entries
- Feedback system for users to provide feedback on knowledge base entries
- Jobs page for tracking upload and sync processing history
Changed:
- None
Fixed:
- None
Removed:
- None
Summary:
- The workflow subpanel now correctly links to the workflow detail view.
- This change improves the overall user experience by providing direct access to relevant workflow information.
- It enhances the efficiency of workflow management by reducing the number of clicks required to view workflow details.
- The fix ensures that users can quickly and easily access the information they need to manage workflows effectively.
Changelog:
Added:
- Direct link to workflow detail view from the subpanel.
Changed:
- The way the subpanel links to the workflow detail view for improved usability.
Fixed:
- The issue with the subpanel link not opening the correct workflow detail view.
Removed:
- None
Summary:
- Improved accuracy in prequalification analysis labels
- Enhanced clarity in opportunity status change notifications
- Consistent language used for prequalification reports and analyses
- Better readability in system-generated messages
Changelog:
Added:
- None
Changed:
- Prequalification analysis labels for better understanding
Fixed:
- Inconsistent language in prequalification analysis labels
Removed:
- None
Summary:
- The form's conditional logic has been simplified and made more efficient.
- Fields can now be shown or hidden based on specific conditions, improving the user experience.
- The form's validation has been improved to handle conditional requirements.
- The Google Maps API integration has been updated for better performance and usability.
Changelog:
Added:
- A new function to evaluate conditional logic for showing or hiding fields.
- Support for appending options to select fields.
- Improved error handling for Google Maps API integration.
Changed:
- The form's conditional logic has been refactored for better performance and readability.
- The Google Maps API integration has been updated to use a more efficient approach.
- The form's validation logic has been improved to handle conditional requirements.
Fixed:
- Issues with the form's conditional logic have been resolved.
- Problems with the Google Maps API integration have been fixed.
Removed:
- Redundant code has been removed to improve performance and readability.
Summary:
- A new "Pending Subscription" status has been added to the system to track leads who have completed onboarding but have not yet made a successful payment.
- When a lead completes onboarding, their status will be set to "Pending Subscription" instead of "Active".
- The status will be updated to "Active" once a successful payment is made through GHL.
- This change improves the tracking and management of leads throughout the subscription process.
- It also prevents leads from being sent new invites while they are pending subscription.
- The system now handles cases where a lead's payment is pending or has failed, keeping their status as "Pending Subscription".
- This update enhances the overall user experience by providing a more accurate and up-to-date representation of a lead's status.
Changelog:
Added:
- "Pending Subscription" status to track leads who have completed onboarding but have not yet made a successful payment.
Changed:
- The status of leads who complete onboarding is now set to "Pending Subscription" instead of "Active".
- The system's handling of lead statuses has been updated to reflect the new "Pending Subscription" status.
Fixed:
- Issues with lead status tracking and management have been resolved with the introduction of the "Pending Subscription" status.
Removed:
- None
Summary:
- The system now captures who ordered a prequalification report and logs it in the activity stream.
- Prequalification analysis runs are now distinguished from prequalification report orders in the activity stream.
- The activity stream now provides more detailed information about prequalification events, such as who ran the analysis.
- The language used in the activity stream has been updated to better reflect the actions taken during the prequalification process.
Changelog:
Added:
- New activity stream entries for prequalification report orders and prequalification analysis runs.
Changed:
- The way prequalification events are logged in the activity stream to provide more detailed information.
- The language used in the activity stream to better reflect the actions taken during the prequalification process.
Fixed:
- None
Removed:
- None
Summary:
- The alignment of uploaded documents has been corrected for better visibility and organization.
- This change improves the overall user experience when uploading and viewing documents.
- The update ensures that documents are displayed in a more consistent and readable format.
- The fix enhances the usability of the document upload feature, making it easier to manage and access documents.
Changelog:
Added:
- None
Changed:
- The spacing and alignment of uploaded documents have been adjusted for better display.
Fixed:
- The alignment issue with uploaded documents has been resolved.
Removed:
- None
Summary:
- The system now correctly associates leads with their corresponding accounts
- Lead information is more accurately passed to the password reset process
- The password reset process for leads has been improved for better functionality
- The overall lead management system has been enhanced for more efficient processing
Changelog:
Added:
- Improved lead identification in the password reset process
Changed:
- The way lead information is passed to the password reset process
Fixed:
- Inaccurate lead association issue
Removed:
- None
Summary:
- The DC process now sorts records by date entered in descending order for easier tracking of recent activities.
- The delete action has been removed from the DC process to prevent accidental data loss.
- The description field has been edited to improve data entry and display.
- The system now automatically assigns a created by user if one is not specified, ensuring that all records have an associated user.
Changelog:
Added:
- A new view for the AOW Processed module to improve data display and filtering.
- A new hook to populate the job queue position for the dc_serialization_job_queue module.
- A new function to get the activity stream user name based on the user ID.
Changed:
- The sort order for the dc_serialization_job_queue module has been changed to sort by date entered in descending order.
- The description field for the dc_serialization_job_queue module has been edited to improve data entry and display.
- The created by user assignment logic has been updated to automatically assign a user if one is not specified.
Fixed:
- The system now correctly handles cases where the created by user is not specified, preventing errors and data inconsistencies.
Removed:
- The delete action has been removed from the DC process to prevent accidental data loss.
Summary:
- Job queue display names have been updated for clarity and consistency.
- The changes improve the organization and readability of job queue items.
- This update enhances the overall user experience by providing more descriptive and accurate job names.
- The new display names include more specific details about the type of job and the related data.
Changelog:
Added:
- More descriptive job names for credit reports, including the type of report and the bureau used.
Changed:
- Job queue display names have been updated to include more specific details about the job type and related data.
- The format of job names has been standardized for consistency.
Fixed:
- None
Removed:
- None
Summary:
- Dates and times are now displayed in the user's local timezone, improving readability and understanding.
- The system can parse and format dates in various formats, making it more flexible and user-friendly.
- Tasks are now saved with the correct date and time, taking into account the user's timezone.
- The display of dates and times has been standardized across the system, reducing confusion and inconsistencies.
- Notes, messages, and documents are now displayed with their creation dates in the user's local timezone.
Changelog:
Added:
- New functions to format and parse dates and times in the user's local timezone.
Changed:
- The way dates and times are displayed and saved in the system, to take into account the user's timezone.
- The task saving process, to use the new date and time formatting functions.
Fixed:
- Inconsistencies in the display of dates and times across the system.
Removed:
- Old code that handled dates and times in a less flexible and less user-friendly way.
Summary:
- Improved lead tracking with additional workflow information
- Enhanced credit reporting and status updates
- Better organization of lead data with new subpanel layouts
- Increased auditability of lead interactions and changes
Changelog:
Added:
- New subpanel for tracking AOW processed workflows
- Additional fields for credit reporting and status updates
Changed:
- Updated field labels for clarity and consistency
- Improved audit logging for lead interactions and changes
Fixed:
- Removed redundant and unused language files
Removed:
- Unused language files for credit frozen flag and onboarding completed status
Summary:
- The system now displays a loading screen when credit report processing is in progress.
- Users will see a message indicating that their credit report is being processed.
- The system suppresses certain modals, such as paywall and SSN correction, while credit report processing is ongoing.
- After payment confirmation, the dashboard data is refreshed to reflect the updated status.
Changelog:
Added:
- Credit report processing handling to the dashboard layout.
- A loading screen with a message indicating credit report processing.
Changed:
- The system now polls for updates while credit report processing is in progress.
- The dashboard access controller now checks for credit report processing status.
Fixed:
- None
Removed:
- None
Summary:
- The system now provides a more concise response when a credit report is being processed.
- Users will no longer be instructed to try again shortly when a report is in progress.
- The change improves the clarity of the message displayed to users.
- It enhances the overall user experience by providing a more straightforward notification.
Changelog:
Added:
- None
Changed:
- The response message for credit report processing
Fixed:
- None
Removed:
- The instruction to try again shortly from the response message
Summary:
- The system now checks if a credit report is being processed for a lead before attempting to retrieve the report.
- If a report is in progress, the system returns a message indicating that the report is being processed and to try again shortly.
- This change improves the user experience by providing more accurate and up-to-date information about the status of credit reports.
- The system also handles cases where a report has been completed but no account data is available, providing a more robust and reliable reporting process.
Changelog:
Added:
- A new feature to check if a credit report is being processed for a lead.
Changed:
- The way the system handles report retrieval to include checks for report processing status.
Fixed:
- Issues with report handling that could lead to incomplete or inaccurate information.
Removed:
- None
Summary:
- The system now sends more detailed information about leads to external services.
- This change helps improve the synchronization of lead data with other applications.
- It enables better tracking and management of leads from different sources.
- The update enhances the overall integration of the lead management system with other tools.
Changelog:
Added:
- The origin field is now included in the data sent to external services.
Changed:
- The system now checks the status of leads to determine the origin field value.
Fixed:
- No fixes are included in this update.
Removed:
- No features or functionality have been removed in this update.
Summary:
- The system now handles subscription status updates more efficiently, without requiring a specific product ID.
- Payment success is now the primary trigger for checking FICO scores and updating subscription access levels.
- The system will automatically retrieve the latest subscription status, even if a product ID is not available.
- This change aims to reduce errors and improve the overall user experience by streamlining the subscription status update process.
Changelog:
Added:
- Automatic retrieval of the latest subscription status, regardless of product ID.
Changed:
- The condition for checking FICO scores and updating subscription access levels now relies solely on payment success.
- The system's query for retrieving subscription information has been modified to prioritize non-empty product IDs and retrieve the latest subscription status.
Fixed:
- Issues related to missing product IDs, which previously prevented the system from updating subscription access levels.
Removed:
- The requirement for a specific product ID to update subscription access levels.
Summary:
- The onboarding process now has an additional condition to determine the next status.
- Leads are now directed to either 'Onboarding' or 'active' status based on their current status.
- This change improves the automation of lead status updates.
- It enhances the overall efficiency of the onboarding process by reducing manual interventions.
Changelog:
Added:
- A conditional check to determine the lead status during onboarding.
Changed:
- The way leads are assigned a status after verification.
Fixed:
- Inconsistent status updates for leads during onboarding.
Removed:
- Automatic assignment of 'Onboarding' status without considering the lead's current status.
Summary:
- The onboarding process for new users has been enhanced to include additional steps and checks.
- Access control has been improved with the introduction of a centralized modal orchestrator.
- The system now handles multiple modal windows more efficiently, ensuring only one modal is shown at a time based on priority.
- Users are now prompted to add their phone number as part of the onboarding process, improving security and communication.
Changelog:
Added:
- A new impersonation panel to manage user access and simulate different scenarios.
- A phone number addition modal to enhance user security and communication.
- Support for blank credit report handling and SSN correction.
Changed:
- The logic for determining when to show the onboarding process has been updated to include more scenarios.
- The access modal orchestrator now prioritizes modals based on their urgency and importance.
Fixed:
- Issues with multiple modals being shown at the same time have been resolved.
- The onboarding process now correctly handles different user scenarios and edge cases.
Removed:
- Redundant code and unnecessary modal logic have been removed to improve system efficiency.
Summary:
- Users can now update their Social Security Number (SSN) and pull a new report.
- The system checks for valid user authentication before allowing SSN updates.
- The update process includes validation to ensure the SSN is in the correct format.
- The system handles cases where no credit data is found in the report.
Changelog:
Added:
- Functionality to update a user's SSN and pull a new report.
Changed:
- User report handling to include cases where no credit data is available.
Fixed:
- None
Removed:
- None
Summary:
- The prequalification process for leads is now more streamlined, focusing on a single method of signature verification.
- The system no longer checks for specific acknowledgement fields related to PQ Portal, making the process more efficient.
- Leads are now considered to have completed signature requirements if they have a GHL-style signature document attached.
- The removal of redundant checks and hooks improves overall system performance and reduces complexity.
Changelog:
Added:
- None
Changed:
- The method for determining if a lead has completed signature requirements has been updated to rely solely on the presence of a GHL-style signature document.
Fixed:
- None
Removed:
- The PQ Portal prequal hook and related functions, which are no longer necessary with the updated signature verification process.
Summary:
- The system now checks for empty credit reports that have been completed but contain no account data.
- If such a report is found, the system returns an error message instead of the report data.
- A new API endpoint has been added to update a lead's SSN and queue a new credit report pull.
- The update SSN endpoint accepts the lead ID and new SSN as parameters and returns a success message if the update is successful.
- The system now handles cases where the submitted SSN is invalid or unchanged.
Changelog:
Added:
- A new function to check if a completed credit report has no account data.
- A new API endpoint to update a lead's SSN and queue a new credit report pull.
Changed:
- The customer portal data retrieval API now checks for empty completed credit reports and returns an error message if found.
- The API documentation has been updated to reflect the changes.
Fixed:
- The system now correctly handles cases where the submitted SSN is invalid or unchanged.
Removed:
- None
Summary:
- The system now checks for empty credit reports and returns an error message if no account data is found.
- This change helps prevent further processing of incomplete credit reports.
- A new function has been added to update a lead's SSN and trigger a new credit report pull.
- The update SSN function also validates the SSN format to ensure it is 9 digits long.
Changelog:
Added:
- A check for empty credit reports to prevent processing of incomplete data
- A function to update a lead's SSN and queue a new credit report pull
Changed:
- The system's behavior when encountering a completed credit report with no account data
Fixed:
- The issue of incomplete credit reports being processed without error messages
Removed:
- None
Summary:
- The Customer Portal has been merged into the PQ Portal, streamlining user management.
- Swagger endpoints have been reorganized by flow for better navigation and understanding.
- New features for lead verification and signup have been added, improving the onboarding process.
- Error handling has been enhanced for better user experience and debugging.
Changelog:
Added:
- Lead verification and signup features
- Email verification with OTP for lead registration
Changed:
- Customer Portal merged into PQ Portal
- Swagger endpoints reorganized by flow
Fixed:
- Improved error handling for various endpoints
Removed:
- Redundant endpoints for broker details and count
Summary:
- The system now automatically updates the "Years in Business" field when the "Date Est" field is changed.
- This update is based on the estimated year the business started and the current year.
- The calculation ensures that the "Years in Business" field reflects the correct number of years since the business started.
- The automatic update improves data accuracy and reduces manual entry errors.
Changelog:
Added:
- Automatic update of "Years in Business" field based on "Date Est" changes.
Changed:
- The system's behavior when updating the "Date Est" field now includes synchronizing the "Years in Business" field.
Fixed:
- Inconsistent or outdated "Years in Business" data due to manual entry errors.
Removed:
- None
Summary:
- Simplified the onboarding process with clearer consent labels and disclosures
- Enhanced user experience with more intuitive electronic signature and credit pull disclaimer acceptance
- Improved data accuracy by pre-filling user information where possible
- Streamlined the submission process with automated updates to user modules
Changelog:
Added:
- New consent labels for electronic signature and credit pull disclaimer
- Automated build of onboarding consent payload
Changed:
- Improved checkbox labels for electronic signature and credit pull disclaimer
- Updated user module updates to include additional business financial information
Fixed:
- None
Removed:
- Redundant code and unnecessary user module updates
Summary:
- The system can now handle consent documents, allowing for better management of user agreements.
- Users can view and interact with consent documents in a more user-friendly way.
- The system can generate PDF versions of consent documents for easy sharing and printing.
- This change improves compliance with regulatory requirements and enhances the overall user experience.
Changelog:
Added:
- Consent document handling feature
Changed:
- System behavior to accommodate consent document management
Fixed:
- No fixes are included in this change
Removed:
- No features or functionality were removed in this change
Summary:
- The contract panel now has improved responsiveness for better viewing on different screen sizes.
- Font sizes in the contract panel have been adjusted for easier reading.
- The layout of the contract panel has been fixed to prevent fields from overflowing and merging.
- The design of the contract panel has been enhanced for a more user-friendly experience.
Changelog:
Added:
- Improved responsiveness for the contract panel on various screen sizes.
Changed:
- Font sizes in the contract panel for better readability.
- Layout of the contract panel to prevent field overflows.
Fixed:
- Issue with fields merging and overflowing in the contract panel.
Removed:
- None
Summary:
- Enhanced error messages for Google sign-in failures to provide clearer explanations of what went wrong
- Added more specific error handling for different types of Google sign-in errors, such as account existence or unknown issues
- Improved user experience by providing more informative and actionable error messages
- Updated the sign-in process to handle errors in a more user-friendly way
Changelog:
Added:
- New error handling system for Google sign-in errors
- More detailed error messages for different types of sign-in errors
Changed:
- The way errors are displayed to users during the Google sign-in process
- The sign-in process now handles errors in a more user-friendly way
Fixed:
- Issues with unclear or unhelpful error messages during Google sign-in
Removed:
- Old error handling system for Google sign-in errors
Summary:
- Enhanced error handling for Google sign-in to provide more informative error messages
- Added intent-based authentication to differentiate between login and signup flows
- Improved database connection handling with enhanced error logging
- Updated configuration settings for MongoDB connection
Changelog:
Added:
- Support for intent-based Google authentication
- Error logging for database connections
Changed:
- Google authentication error handling to provide more specific error messages
- Database connection configuration settings
Fixed:
- Improved error handling for Google sign-in to prevent generic error messages
- Updated database connection error handling to provide more informative error messages
Removed:
- None
Summary:
- Enhanced lead search functionality to improve matching accuracy
- Added ability to search for leads by email and phone number in addition to GHL contact ID
- Improved search logic to prioritize most recently modified leads
- Increased efficiency in lead search process to reduce errors and improve overall system performance
Changelog:
Added:
- New search parameters for email and phone number to improve lead matching
Changed:
- Lead search logic to prioritize email and phone number matches over GHL contact ID
- Search process to use most recently modified leads for better accuracy
Fixed:
- Issues with lead search not finding matches due to limited search parameters
Removed:
- None
Summary:
- Improved API documentation with standardized examples for better understanding
- Enhanced readability of API requests and responses with compact examples
- Simplified representation of complex data structures for easier consumption
- Increased consistency in API documentation for reduced confusion
Changelog:
Added:
- Generic placeholders for sensitive information in API examples
Changed:
- API documentation examples to use compact and standardized formats
- Representation of session IDs and other identifiers in API examples
Fixed:
- Inconsistencies in API documentation examples
Removed:
- Specific session IDs and sensitive information from API examples
Summary:
- The customer portal signup and login features are no longer available in the documentation.
- This change helps keep the system up-to-date by removing outdated features.
- It improves the overall user experience by reducing clutter and focusing on current functionality.
- The removal of these features does not affect existing customer portal functionality.
Changelog:
Removed:
- Customer portal signup feature from documentation
- Customer portal login feature from documentation
Changed:
- Documentation to reflect current system capabilities
Fixed:
- None
Added:
- None
Summary:
- The layout for selecting discount offers has been improved for better user experience.
- The discount offer selection field now adjusts its width based on the type of offer chosen.
- The layout is more responsive and consistent with other parts of the system.
- The changes make it easier to use and understand the discount offer selection process.
Changelog:
Added:
- A new function to synchronize the discount offer plan layout.
Changed:
- The width of the discount offer selection field is now adjusted dynamically.
- The layout of the discount offer plan section has been updated for consistency.
Fixed:
- Issues with the layout of the discount offer selection field have been resolved.
Removed:
- Hardcoded width settings for the discount offer selection field.
Summary:
- The system now tracks changes to subscription access levels for better auditing and security.
- Lead access levels are calculated based on their FICO scores, ensuring more accurate and personalized access control.
- The system can now automatically fetch prequal reports when a lead is eligible, streamlining the subscription process.
- Lead updates are now handled more efficiently, reducing the risk of data inconsistencies and errors.
Changelog:
Added:
- Automatic prequal report fetching for eligible leads
Changed:
- Lead access levels are now calculated based on FICO scores
- Lead updates are now handled through a more efficient and reliable method
Fixed:
- Issues with lead updates and data consistency have been resolved
Removed:
- Redundant lead update queries have been removed to improve system efficiency
Summary:
- Improved error messaging for Google sign-in failures
- Enhanced referral code handling after successful login
- Simplified phone number verification process
- Added Google Connect button for easier sign-up and login
- Introduced a trouble signing in/up link for user support
Changelog:
Added:
- Google Connect button for sign-up and login
- Trouble signing in/up link for user support
Changed:
- Error messaging for Google sign-in failures
- Referral code handling after successful login
- Phone number verification process
Fixed:
- None
Removed:
- Explicit mode parameter in phone number verification routes
Summary:
- Improved Google authentication flow to handle both new and existing users.
- Added support for referral codes and custom fingerprints during Google login.
- Enhanced user creation and update logic for better data consistency.
- Introduced validation for email addresses and signup data to prevent errors.
- Updated login success handling to ensure seamless user experience.
Changelog:
Added:
- Support for referral codes during Google login.
- Custom fingerprint handling for Google login devices.
- Validation for email addresses and signup data.
- New functions for handling Google direct login, signup flow, and referral codes.
Changed:
- Google authentication flow to handle both new and existing users.
- User creation and update logic for better data consistency.
- Login success handling to ensure seamless user experience.
Fixed:
- Issues with email existence checks and custom signup flow.
- Problems with device persistence and CRM session ID storage.
Removed:
- Redundant code and unnecessary functions.
Summary:
- The system now tracks changes to lead credit pull disclaimers and digital signature acknowledgments.
- This change improves the ability to monitor and audit lead interactions.
- It enhances data integrity by keeping a record of all changes made to these fields.
- The update supports better compliance and risk management by providing a clear audit trail.
Changelog:
Added:
- Auditing capability for lead credit pull disclaimers and digital signature acknowledgments.
Changed:
- The way the system handles tracking of lead interactions, now including auditing for specific fields.
Fixed:
- None
Removed:
- None
Summary:
- The system now allows better access to API documentation for developers.
- Previously hidden API entry points are now visible and accessible.
- This change improves the overall usability of the system for integrations.
- It enables easier discovery and use of API features for external applications.
Changelog:
Added:
- Visibility to previously hidden API entry points
Changed:
- System configuration to allow better access to API documentation
Fixed:
- Issue with API entry point being hidden from view
Removed:
- None
Summary:
- The layout for selecting discount offers has been improved for better user experience.
- The width of the discount offer selection field has been standardized for consistency.
- The display of discount offer information has been made more compact and organized.
- The overall design of the discount offer section has been refined for easier navigation.
Changelog:
Added:
- A more consistent and compact layout for discount offer information.
Changed:
- The width of the discount offer selection field to improve consistency.
- The display of discount offer custom labels to improve readability.
Fixed:
- Inconsistent spacing and sizing issues in the discount offer section.
Removed:
- Unnecessary styling options to simplify the design and improve maintainability.
Summary:
- Improved organization of API documentation for easier navigation and understanding
- Added categorization of API endpoints using tags for better discoverability
- Enhanced documentation structure to reduce complexity and improve readability
- Removed outdated or redundant API endpoints to simplify the documentation
Changelog:
Added:
- New tags for categorizing API endpoints, such as SuiteCRM Default API v4, Authentication, and Broker Portal
- Tag groups for organizing related API endpoints together
Changed:
- API endpoint documentation to include tags for categorization and improved descriptions
- Organization of API endpoints to reduce complexity and improve readability
Fixed:
- Removed redundant or outdated API endpoints to simplify the documentation
Removed:
- The /sendtoCentrex API endpoint, which is no longer needed or supported
Summary:
- Improved handling of contract-out fields for BFA agreements
- Enhanced support for BFA Full Pay and Payment Plan documents
- Simplified storage and management of contract-out field values
- Updated UI to match custom discount input and upfront fee field widths
- Introduced JSON storage for contract-out field values keyed by document template name
Changelog:
Added:
- Contract-out fields for BFA Full Pay and Payment Plan documents
- JSON storage for contract-out field values
- New utility functions for managing contract-out fields
Changed:
- Improved handling of contract-out fields for BFA agreements
- Updated UI styling for custom discount input and upfront fee fields
Fixed:
- Issues with persisting contract-out field values after sending documents
Removed:
- Legacy code for handling contract-out fields
Summary:
- Passwords are no longer logged, reducing the risk of sensitive information exposure.
- Passwords are removed from data after verification, minimizing the chance of unauthorized access.
- The system now handles incorrect passwords more securely, without logging sensitive details.
- Overall security and compliance have been enhanced by removing unnecessary password logging and storage.
Changelog:
Added:
- Enhanced password handling for improved security.
Changed:
- Password verification process to prevent logging of sensitive information.
- Data processing to remove passwords after verification.
Fixed:
- Security vulnerability related to password logging and storage.
Removed:
- Unnecessary logging of passwords and sensitive data.
Summary:
- The system now records SMS two-factor authentication messages sent to leads as notes in their profiles.
- This change improves the tracking and auditing of SMS messages related to two-factor authentication.
- It provides a clear record of when SMS messages were sent, which can be useful for troubleshooting and customer support.
- The new functionality enhances the overall security and transparency of the lending process.
Changelog:
Added:
- The ability to log SMS OTP messages as lead notes.
Changed:
- The way the system handles SMS two-factor authentication messages for leads.
Fixed:
- No fixes are included in this change.
Removed:
- No features or functionality were removed in this change.
Summary:
- The system now considers the age of a record when merging changes, providing more control over data updates.
- Records less than one year old have protected fields that are not overwritten if the incoming value differs, with attempted changes logged in a note.
- Records older than one year have protected fields updated with incoming values, and any replaced values are saved in a note for reference.
- The audit notes for these changes are now more descriptive and clearly indicate whether the record was updated or the changes were logged.
Changelog:
Added:
- New logic to determine if a record is older than one year and apply different merge rules accordingly.
- More descriptive audit notes for changes made to records.
Changed:
- The way protected fields are handled during record updates, considering the record's age.
- The naming and content of audit notes to better reflect the changes made.
Fixed:
- None
Removed:
- None
Summary:
- The system can now verify if a lead has completed the custom lead signup process.
- This check is done by providing the lead's email address and a valid portal session.
- The system returns a status indicating whether the lead has completed the signup process.
- This feature improves the overall customer portal experience by allowing for more accurate tracking of lead engagement.
- It also enhances security by verifying the existence of portal credentials for a given email address.
Changelog:
Added:
- A new API endpoint to check if a lead has completed the custom lead signup process.
Changed:
- The system's ability to track lead engagement has been enhanced with the addition of the lead signup completion check.
Fixed:
- None
Removed:
- None
Summary:
- The system now integrates with Monevo to match lenders with potential borrowers.
- This integration enables the submission of applications to Monevo and retrieval of offer results.
- The system handles building the request payload from a lead and submitting the application.
- The integration also includes polling the results endpoint to fetch offers until they are generated or a limit is reached.
- Error handling has been implemented to manage potential issues with the Monevo API.
- The system can now parse XML responses from Monevo and extract relevant information such as offers and summaries.
Changelog:
Added:
- Monevo lender matching integration
Changed:
- None
Fixed:
- None
Removed:
- None
Summary:
- The system now prevents users from changing the Fico score field once a score has been set.
- This change helps maintain data integrity and accuracy.
- It ensures that Fico scores are not altered accidentally or intentionally after they have been determined.
- The protection applies to all Fico score fields, including Experian, Transunion, and Equifax.
Changelog:
Added:
- Protection for Fico score fields to prevent editing once a score is set.
Changed:
- Fico score fields now display a message indicating that they cannot be changed once a score is set.
Fixed:
- None
Removed:
- Ability for users to edit Fico score fields after a score has been set.
Summary:
- The system now supports an alternate prequalification signature path using PQ Portal acknowledgement fields.
- This change allows leads to complete prequalification requirements without needing a traditional signature document.
- The new functionality checks for the completion of PQ Portal acknowledgement fields and triggers prequal report pulls when eligible.
- The system also prevents duplicate job queue creation when the same lead is eligible for prequal report pulls multiple times.
Changelog:
Added:
- Support for PQ Portal acknowledgement fields as an alternate prequal signature path.
- A new logic hook to trigger prequal report pulls when PQ Portal acknowledgement fields are completed.
Changed:
- The prequalification logic to include checks for PQ Portal acknowledgement fields.
- The document logic hook to use the new maybeTriggerPrequalReportForLead function.
Fixed:
- Duplicate job queue creation when the same lead is eligible for prequal report pulls multiple times.
Removed:
- None
Summary:
- The system now allows for dynamic tracking of Swagger API documentation in git.
- Each server environment can have its own unique Swagger API URL.
- The Swagger API documentation can be easily updated for different environments.
- The system provides a flexible way to manage API documentation across various environments.
Changelog:
Added:
- Ability to track Swagger API documentation in git with per-environment server URL.
- Environment variable file (.env) to store server-specific API URLs and descriptions.
Changed:
- The way Swagger API documentation is served, now using a dynamic configuration.
- The default server URL is now overridden by the .env file.
Fixed:
- Removed hardcoded server URLs from the Swagger API documentation.
Removed:
- Hardcoded server URLs for staging and production environments from the Swagger API documentation.
Summary:
- The system now saves lead profiles with additional information when a user logs in.
- This change improves the accuracy of lead tracking and management.
- It also enhances the overall user experience by providing more detailed user data.
- The update enables better integration with customer relationship management tools.
Changelog:
Added:
- Ability to save lead profiles with status information.
Changed:
- The method used to create CRM entries now includes note-saving functionality.
Fixed:
- No fixes are included in this update.
Removed:
- No features or functionalities were removed in this update.
Summary:
- The login page no longer offers Google as a sign-in option.
- Users will have one less method to log in to their accounts.
- This change simplifies the login process by reducing the number of sign-in options.
- The removal of Google sign-in is intended to improve the overall user experience.
Changelog:
Added:
- No new features were added in this update.
Changed:
- The login page has been updated to remove an existing sign-in option.
Fixed:
- No bugs were fixed in this update.
Removed:
- The Google sign-in option has been removed from the login page.
Summary:
- The system now tracks API documentation in git, allowing for better version control and management of API changes.
- This change improves the transparency and accessibility of API documentation for developers and stakeholders.
- It enables easier collaboration and review of API documentation, reducing errors and inconsistencies.
- The tracking of API documentation in git also facilitates auditing and compliance with regulatory requirements.
Changelog:
Added:
- API documentation tracking in git
Changed:
- Git ignore settings to allow tracking of API documentation files
Fixed:
- None
Removed:
- None
Summary:
- Improved validation for lead signup portal status to prevent duplicate signups
- Enhanced error handling for various portal status scenarios, such as active, onboarding, verification pending, and canceled
- Added checks to ensure portal signup is allowed based on the lead's portal status
- Improved logging and messaging for failed signup attempts
Changelog:
Added:
- Validation checks for lead portal status during signup
- Error handling for different portal status scenarios
Changed:
- Improved logic for determining if portal signup is allowed based on the lead's portal status
- Enhanced logging and messaging for failed signup attempts
Fixed:
- Issue with duplicate signups due to lack of portal status validation
Removed:
- None
Summary:
- Improves the display of history records for leads by fixing an issue where the record count was incorrect.
- Ensures that the pagination of history records works correctly, even after deleting records or using the browser's back button.
- Enhances the overall user experience by providing accurate record counts and proper pagination.
- Fixes a problem where the subpanel would show an incorrect offset, resulting in an empty list of records.
Changelog:
Added:
- A custom class to handle the display of history records for leads, which fixes the offset issue.
Changed:
- The way the subpanel handles pagination for history records, to ensure accurate record counts and proper pagination.
Fixed:
- An issue where the subpanel would show an incorrect offset, resulting in an empty list of records.
- A problem where the record count was incorrect after deleting records or using the browser's back button.
Removed:
- None
Summary:
- The website's title has been updated to better reflect its purpose and features.
- The onboarding process has been improved to provide a more seamless experience for users.
- User data is now updated more efficiently after completing the onboarding process.
- The system's buttons have been made more accessible by improving their visual cues for disabled states.
Changelog:
Added:
- A new API call to complete the onboarding process for users.
Changed:
- The way user data is updated after onboarding completion.
- The styling of buttons to improve accessibility.
Fixed:
- No fixes are included in this update.
Removed:
- The "onboardingCompletedC" field is no longer sent separately, as it is now updated internally.
Summary:
- Improved user authentication and registration processes
- Enhanced email validation and checking for existing user accounts
- Updated user onboarding process with a new completion endpoint
- Removed unnecessary dependencies and code for better performance
- Improved error handling for user authentication and registration
Changelog:
Added:
- New endpoint for completing user onboarding
- Email existence check to prevent duplicate user accounts
Changed:
- User registration process to use a custom lead signup service
- User authentication to use a more secure and efficient method
Fixed:
- Issues with user authentication and registration error handling
- Problems with email validation and checking for existing user accounts
Removed:
- Unused dependencies and code for better performance and security
- Referrals count field from partner data for simplified partner management
Summary:
- The system now prioritizes using a person's date of birth for identification when available.
- This change aims to reduce the reliance on Social Security Numbers for identification purposes.
- The system will automatically fall back to using the SSN if the date of birth is not available.
- This update improves the handling of sensitive personal information and enhances overall system flexibility.
Changelog:
Added:
- A new feature to automatically determine the best identifier (date of birth or SSN) for each person.
Changed:
- The default identifier used by the system is now the date of birth instead of the SSN.
- The system's logic for handling missing identifiers has been updated to prioritize date of birth.
Fixed:
- Issues related to missing identifiers have been resolved by implementing a fallback mechanism.
Removed:
- Redundant code related to identifier handling has been removed to simplify the system.
Summary:
- The system now checks the status of a lead before sending an email invitation to the customer portal.
- If the lead's status is active, the system will not send an email invitation to prevent duplicate invitations.
- The system also handles other statuses such as inactive, sent invite, verification pending, onboarding, and canceled, and provides appropriate messages for each status.
- The goal of this change is to improve the efficiency and accuracy of the email invitation process and prevent unnecessary emails from being sent to leads.
Changelog:
Added:
- A new validation process to check the lead's status before sending an email invitation.
Changed:
- The system's behavior when a lead's status is active or other specific statuses, to prevent unnecessary email invitations.
Fixed:
- The issue of duplicate email invitations being sent to leads with an active status.
Removed:
- The previous behavior of sending email invitations regardless of the lead's status.
Summary:
- The system now tracks the onboarding status of portal users, allowing for better management of the onboarding process.
- A new status called "Onboarding" has been added to reflect the current state of a user's onboarding process.
- The system can now mark a user's onboarding as complete, updating their status to "active" and indicating that they have finished the onboarding process.
- This change enables more efficient tracking and completion of the onboarding process for portal users.
Changelog:
Added:
- A new onboarding status to track the current state of a user's onboarding process.
- A feature to mark a user's onboarding as complete.
Changed:
- The default status for new portal users is now "Onboarding" instead of "active".
- The system now updates a user's status to "active" when their onboarding is marked as complete.
Fixed:
- None
Removed:
- None
Summary:
- Improves the accuracy of Bitbucket pull request diff URLs to ensure correct changelog updates.
- Enhances the security and reliability of curl requests for Bitbucket API interactions.
- Increases the efficiency of database queries by removing unnecessary limits.
- Simplifies the authentication process for Bitbucket API tokens.
Changelog:
Added:
- A new function to resolve pull request diff URLs directly from the Bitbucket API.
Changed:
- The way Bitbucket API tokens are decoded and used for authentication.
- The curl request options to improve connection timeouts and response handling.
Fixed:
- An issue where the diff URL was not being correctly retrieved from the payload.
- A problem with the curl request authentication that could cause errors.
Removed:
- A test file that is no longer needed after verification of the Bitbucket changelog automation.
Summary:
- A test is being conducted to verify the changelog automation process.
- The goal is to confirm that the system can receive and process updates correctly.
- This test will help ensure that changes are properly recorded and tracked.
- The test is a one-time verification and will be removed after completion.
Changelog:
Added:
- A test marker to verify the changelog automation process.
Changed:
- None
Fixed:
- None
Removed:
- None
Summary:
- The application is now accessible in all environments, not just staging.
- Users can now use the application without restrictions based on the environment.
- The filtering functionality remains unchanged and is still available to users.
- The overall user experience has been improved by removing unnecessary restrictions.
Changelog:
Added:
- Accessibility to the application in all environments.
Changed:
- Environment-based restrictions have been removed.
Fixed:
- None
Removed:
- Restriction that limited the application to only the staging environment.
Summary:
- Simplified the offers page by removing unnecessary filters
- Enhanced the onboarding process by adding required fields for first and last name
- Updated the support email address for better assistance
- Improved the upgrade modal by adding a logout option for users coming from onboarding
- Refactored the code to improve performance and readability
Changelog:
Added:
- First and last name fields to the onboarding form
- Logout option to the upgrade modal for users coming from onboarding
Changed:
- Removed credit range filter from the offers page
- Updated support email address to support@lendinggenie.ai
- Improved the upgrade modal payment step
Fixed:
- None
Removed:
- Credit range filter from the offers page
- Unused code and variables to improve performance and readability
Summary:
- The detailed view of bank information has been simplified
- Removal of specific bank details improves data organization
- The change affects how bank trade information is displayed
- The update focuses on streamlining the user interface
Changelog:
Removed:
- Detailed trade information for multiple banks, including American Express, Bank of America, Capital One, Chase, Citibank, US Bank, and Wells Fargo
Summary:
- The system now supports a new feature called Offer Wall Generic, which provides a platform for managing offers and promotions.
- A new module has been added to handle Offer Wall Generic information, accessible only to the administrator.
- The system now includes a dropdown list for bank names, allowing users to select from a predefined list of banks.
- The system also includes categories and credit range options for Offer Wall Generic, enabling more targeted and personalized offers.
- A new relationship has been established between leads and Offer Wall Generic, allowing for more effective management of leads and offers.
- The system now supports card thumbnails, enabling users to view images of cards.
Changelog:
Added:
- Offer Wall Generic module
- Bank name dropdown list
- Categories and credit range options for Offer Wall Generic
- Relationship between leads and Offer Wall Generic
- Card thumbnail feature
Changed:
- Administration menu to include Offer Wall Generic information
Fixed:
- No fixes are included in this update
Removed:
- No features or modules have been removed in this update
Summary:
- Enhanced lead tracking by introducing a new relationship between leads and education records
- Allows for the tracking of video progress for each education record associated with a lead
- Provides a new API endpoint to update education video progress for a lead
- Provides a new API endpoint to retrieve education progress for a lead
Changelog:
Added:
- New relationship between leads and education records to track video progress
- API endpoint to update education video progress for a lead
- API endpoint to retrieve education progress for a lead
Changed:
- Existing database schema to accommodate the new relationship and video progress tracking
Fixed:
- No fixes are included in this change
Removed:
- No features or functionality were removed in this change
Summary:
- Improved security by switching to Bitbucket API tokens for authentication
- Enhanced compatibility with Bitbucket's latest authentication methods
- Simplified configuration by using a single API token for authentication
- Increased reliability by handling authentication errors more effectively
Changelog:
Added:
- Support for Bitbucket API tokens for authentication
Changed:
- Authentication method from app passwords to API tokens
- Configuration requirements to use Bitbucket email and API token
Fixed:
- Compatibility issues with deprecated app passwords
Removed:
- Dependent on deprecated Bitbucket app passwords for authentication
Summary:
- The display of credit ranges for offers has been removed to simplify the user interface.
- Password requirements have been updated to ensure they are between 8 and 16 characters long for better security.
- The system now enforces stronger password policies for all users.
- The overall user experience has been improved by reducing clutter and enhancing security measures.
Changelog:
Added:
- Maximum password length validation to enhance security.
Changed:
- Password requirements to ensure they are within a specific length range.
- The way offer details are displayed to users.
Fixed:
- Inconsistent password validation rules.
Removed:
- Display of credit ranges for offers.
Summary:
- The prequalification process has been improved to provide clearer information about the steps involved.
- Users can now edit their previous answers during the prequalification process.
- The system now displays a progress bar showing the current step and total number of steps.
- The prequalification chat interface has been updated for better user experience.
- The upgrade modal has been modified to display a payment link after pre-qualification.
Changelog:
Added:
- The ability for users to edit their previous answers during the prequalification process.
- A progress bar showing the current step and total number of steps in the prequalification process.
- A payment link in the upgrade modal after pre-qualification.
Changed:
- The prequalification chat interface for better user experience.
- The upgrade modal to display a payment link after pre-qualification.
Fixed:
- No fixes are mentioned in the provided diff.
Removed:
- No removals are mentioned in the provided diff.
Summary:
- The link to the credit authorization agreement has been updated to reflect a new website.
- This change helps to ensure that users are directed to the correct location for credit authorization information.
- The update improves the overall user experience by providing a more accurate and reliable link.
- This modification is part of an effort to maintain compliance with relevant regulations and agreements.
Changelog:
Added:
- A new link to the credit authorization agreement on the Deliver Capital website.
Changed:
- The existing link to the credit authorization agreement has been updated to point to the new Deliver Capital website.
Fixed:
- The issue of outdated links to the credit authorization agreement has been resolved.
Removed:
- The old link to the Lendio credit authorization agreement has been removed.
Summary:
- The signup process has been simplified and improved for a better user experience.
- Users can now sign up using a whitelisted link, streamlining the process for eligible users.
- The system can now handle invalid or expired links, providing a clear error message to users.
- The overall design and layout of the signup page have been updated for consistency and clarity.
- Loading indicators have been standardized throughout the application for a more cohesive feel.
Changelog:
Added:
- Support for whitelisted signup links to simplify the signup process for eligible users.
- An invalid link screen to handle cases where users attempt to sign up with an invalid or expired link.
Changed:
- The signup page design and layout for improved consistency and clarity.
- Loading indicators throughout the application for a more standardized and cohesive feel.
Fixed:
- Various minor issues and inconsistencies in the signup and verification processes.
Removed:
- Redundant code and unnecessary complexity from the signup process.
Summary:
- The login page has been removed and its functionality is now handled by the root page.
- The redirect behavior after login has been improved for a better user experience.
- Referral codes are now properly saved and cleared during the signup process.
- The prequalification modal has been replaced with a new prequalification component.
- The signup process now includes the option to enter a referral code.
- Error handling for login and signup processes has been improved.
- The overall authentication flow has been streamlined for easier use.
Changelog:
Added:
- New page for handling redirects after login
- Option to enter a referral code during signup
- Improved error handling for authentication processes
Changed:
- Login page removed and its functionality handled by the root page
- Redirect behavior after login improved
- Prequalification modal replaced with a new prequalification component
Fixed:
- Referral codes are now properly saved and cleared during signup
- Improved error handling for login and signup processes
Removed:
- Old login page
- Old prequalification modal component
Summary:
- The system now automatically sets portal access levels based on FICO scores from reports.
- Email invitations for portal access are sent to customers after their first successful subscription.
- The system checks for specific conditions before sending email invitations, such as report completion and automated report status.
- Portal access and email invitations are only sent for TransUnion reports with no system errors.
Changelog:
Added:
- A new feature to send email invitations for portal access after the first successful subscription.
- A check for TransUnion reports with no system errors before sending email invitations.
Changed:
- The system now automatically sets portal access levels based on FICO scores from reports.
- The conditions for sending email invitations have been updated to include report completion and automated report status.
Fixed:
- No specific fixes are mentioned, but the updates improve the overall functionality of portal access and email invitations.
Removed:
- No features or functionalities have been removed in this update.
Summary:
- The system now captures more accurate customer information during registration.
- Customer portal sign-ups are more efficient and reliable.
- The system can better track customer interactions and history.
- Registration processes are more streamlined, reducing potential errors.
Changelog:
Added:
- The ability to associate a unique identifier with customer portal registrations.
Changed:
- The way customer information is collected and stored during registration.
Fixed:
- Inaccuracies in customer data capture during the registration process.
Removed:
- None
Summary:
- The system now automatically sorts lists by the date they were entered, making it easier to find recent items.
- Users can filter search results to only show items assigned to them, improving their ability to manage their workload.
- The search function has been enhanced to allow for range searches on dates, such as start and renewal dates.
- The layout of the search form has been improved for better usability, with clear labels and organized fields.
Changelog:
Added:
- New search filters for start and renewal dates
- Ability to filter by assigned user
- Range search functionality for dates
Changed:
- Default sort order for lists is now by date entered
- Search form layout has been improved
Fixed:
- No fixes are included in this update
Removed:
- No features or functionality have been removed
Summary:
- The loan application process now requires a lead to be created before accessing certain tabs.
- This change ensures that sensitive information is only accessible when a lead is properly set up.
- The application will now automatically unlock relevant tabs after a lead is created.
- This improvement enhances the overall workflow and organization of the loan application process.
- The change prevents premature access to financial and document-related tabs.
Changelog:
Added:
- Automatic unlocking of tabs after lead creation
Changed:
- The condition for accessing certain tabs now requires a valid lead
Fixed:
- Inconsistent access to tabs based on loan type selection
Removed:
- The ability to access certain tabs solely based on loan type selection
Summary:
- The application now only unlocks certain tabs after a lead has been created, improving the workflow.
- This change prevents users from accessing tabs prematurely, reducing potential errors.
- The update ensures that tabs are only accessible when relevant information is available.
- The application's overall user experience has been improved by streamlining the tab unlocking process.
Changelog:
Added:
- A check to ensure that a lead exists before unlocking certain tabs.
Changed:
- The condition for unlocking tabs, now requiring a lead to be created.
Fixed:
- An issue where tabs could be accessed too early in the process.
Removed:
- The ability to unlock tabs solely based on selecting a loan type.
Summary:
- Users can now update their Social Security Number (SSN) through a dedicated page.
- The update process includes input validation and formatting to ensure accurate data entry.
- A confirmation message is displayed after a successful update, and users can close the page to return to the main portal.
- The system checks if a user has already submitted their SSN to prevent duplicate entries.
- Error handling is implemented to notify users of any issues during the update process.
- The page is designed to be user-friendly, with a simple and intuitive interface.
Changelog:
Added:
- A new page for updating Social Security Numbers
- Input validation and formatting for SSN entries
- Confirmation messaging for successful updates
- Error handling for update issues
Changed:
- The system now checks for existing SSN submissions to prevent duplicates
- The update process includes a confirmation step to ensure user awareness
Fixed:
- Improved handling of invalid or incomplete SSN entries
Removed:
- None
Summary:
- The system now tracks the source of Social Security Numbers (SSN) for leads.
- This change allows for better management and reporting of lead information.
- The system can now record whether a credit report was fetched using an SSN or Date of Birth (DOB).
- This update improves data accuracy and provides more detailed information for lead management and reporting.
Changelog:
Added:
- SSN source tracking for leads
- Option to record the type of identifier used to fetch credit reports (SSN or DOB)
Changed:
- Updated lead management to include SSN source information
- Modified credit report fetching to record the type of identifier used
Fixed:
- No fixes are included in this update
Removed:
- No features or functionality were removed in this update
Summary:
- The way loan amounts are calculated has been improved for accuracy.
- A new rule has been added to adjust the calculation based on the credit limit.
- This change affects how personal loan amounts are determined for customers.
- The update ensures that loan amounts are displayed in a clear and readable format.
Changelog:
Added:
- A conditional multiplier to adjust loan amount calculations based on credit limit.
Changed:
- The formula used to calculate personal loan amounts to make it more accurate.
Fixed:
- The display of loan amounts to ensure they are formatted correctly with commas.
Removed:
- None
Summary:
- The prequalification modal is now accessible from multiple locations on the landing page.
- A new prequalification modal host component has been added to manage the modal's state.
- The impersonation mode now defaults to "bypass" instead of "user".
- The dashboard tour will not start when impersonating a user.
- The landing hero section has been updated to use the new prequalification modal store.
- The prequalification modal can now be opened and closed programmatically.
Changelog:
Added:
- Prequalification modal host component
- Prequalification modal store
Changed:
- Impersonation mode default
- Landing hero section to use prequalification modal store
- Dashboard tour to not start when impersonating a user
Fixed:
- None
Removed:
- Direct links to open the prequalification modal have been replaced with a programmatic approach
Summary:
- Improved security checks to verify the origin of requests, reducing the risk of unauthorized access.
- Enhanced host verification to allow for more flexible and accurate checks.
- Increased reliability of lead synchronization by accommodating different server configurations.
- Better handling of empty or missing referer information to prevent false negatives.
Changelog:
Added:
- Additional host verification methods to improve security and flexibility.
Changed:
- Host verification logic to accept matches on multiple server variables, improving accuracy.
Fixed:
- Issue with empty or missing referer information causing false negatives.
Removed:
- None
Summary:
- Added Google sign-in functionality to the login page, allowing users to sign in with their Google account.
- Improved the login experience by providing an alternative sign-in method.
- Enhanced security by leveraging Google's authentication system.
- Removed the sign-up page, streamlining the user registration process.
Changelog:
Added:
- Google sign-in button on the login page
- Google sign-in functionality to handle authentication
Changed:
- Login page to include Google sign-in option
- Authentication flow to handle Google sign-in
Fixed:
- None
Removed:
- Sign-up page
Summary:
- Added support for Google OAuth login to simplify user authentication.
- Introduced admin authorization to restrict access to certain features.
- Enhanced login functionality with improved error handling and user experience.
- Added enumeration options for better data management and filtering.
Changelog:
Added:
- Google OAuth login feature
- Admin authorization middleware
- Enumeration options for data management
Changed:
- Improved login functionality with enhanced error handling
- Updated user authentication and authorization logic
Fixed:
- Various bug fixes and improvements for better system stability
Removed:
- None
Summary:
- Improved security for lead login by introducing session-assisted and lead ID-based authentication methods
- Enhanced password management for portal users, including validation and error handling
- Increased robustness in handling lead credentials and session creation
- Better logging and error messaging for debugging and user feedback
Changelog:
Added:
- New authentication modes for leads, including session-assisted and lead ID-based login
- Validation for required parameters in password update requests
- Improved error handling and logging for password update failures
Changed:
- Existing lead login functionality to support new authentication modes
- Password update process to use a valid portal session ID
- Error messaging and logging to provide clearer feedback
Fixed:
- Issues with lead authentication and password updates
- Insecure password handling and potential vulnerabilities
Removed:
- None
Summary:
- The list of loan purposes has been expanded to provide more specific options for customers.
- This change allows customers to more accurately describe the intended use of their loan.
- The updated options will help improve data collection and analysis for loan purposes.
- The new options will also enhance the overall user experience by providing more relevant and descriptive choices.
Changelog:
Added:
- New loan purpose options, including Expansion, Working Capital, Payroll, and others.
Changed:
- The loan purpose list now includes more specific and detailed options.
Fixed:
- None
Removed:
- None
Summary:
- The system now removes empty options from dropdown lists, improving user experience.
- This change helps prevent confusion by hiding unnecessary options.
- Data quality is improved by excluding empty values from responses.
- The overall usability of the system is enhanced by providing more relevant options.
Changelog:
Added:
- Ability to filter out empty enum options from responses.
Changed:
- The way enum options are retrieved and returned to users.
Fixed:
- Issue with empty options being displayed in dropdown lists.
Removed:
- Empty options from enum values returned by the system.
Summary:
- The system now includes a new lead status called "LG App" to categorize leads from this source.
- Leads with the "LG App" status are automatically tagged with "Synced to GHL - LG App" for easier tracking.
- The system checks if a lead is new and has required fields (first name, last name, email) before syncing it with GoHighLevel (GHL).
- The syncing process now only runs for requests originating from allowed hosts, enhancing security.
- Two new lead sources, "CreditCon 2026" and "Lending Genie", have been added to the system.
Changelog:
Added:
- New lead status "LG App"
- New lead sources "CreditCon 2026" and "Lending Genie"
- Automatic tagging of "LG App" leads with "Synced to GHL - LG App"
Changed:
- Syncing process now checks for allowed hosts and required lead fields
Fixed:
- None
Removed:
- None
Summary:
- The list of loan types available for selection has been revised.
- Credit card is no longer considered a loan type.
- This change helps to better categorize and differentiate between loan types.
- It improves the overall accuracy and consistency of loan type classifications.
Changelog:
Added:
- None
Changed:
- Loan type categorization for better accuracy
Fixed:
- Inconsistent loan type classification
Removed:
- Credit card as a loan type option
Summary:
- The system now includes Credit Card as a loan type option for users to select.
- This addition provides more flexibility and accuracy in loan type classification.
- Users can now specify Credit Card as the loan type, improving data consistency.
- The update enhances the overall user experience by providing a more comprehensive list of loan types.
Changelog:
Added:
- Credit Card as a loan type option
Changed:
- The list of available loan types to include Credit Card
Fixed:
- None
Removed:
- None
Summary:
- The way leads are categorized by their state of formation has been improved for better accuracy.
- The options for lead formation states have been updated to provide more relevant choices.
- The user experience for editing leads has been enhanced by removing unnecessary features.
- The overall quality of lead data is expected to increase due to these changes.
Changelog:
Added:
- More accurate lead formation state options
Changed:
- The way lead formation states are categorized
Fixed:
- Inaccurate lead formation state options
Removed:
- Unnecessary phone mask script from the lead edit view
Releaseddc763-repo/dc_crm
#4774 ProductionPT Git User
Change Overview
Summary:
- The system now provides more detailed and accurate error messages when credit checks fail or return incomplete data.
- This change helps to identify the root cause of errors, such as system errors, credit freezes, or blank credit reports.
- The new error reporting system prioritizes error types to provide more informative messages.
- This improvement enables better troubleshooting and resolution of issues related to credit checks.
- The system now returns a specific error code when a credit report is completed but contains no useful data.
Changelog:
Added:
- A new function to resolve and report errors related to credit checks.
Changed:
- The way the system handles and reports errors when credit checks fail or return incomplete data.
Fixed:
- Issues with incomplete or inaccurate error messages for credit checks.
Removed:
- None
Releaseddc763-repo/dc_crm
#4779 ProductionBilal Alam
Change Overview
Summary:
- The system can now receive and process failed payment notifications from GHL.
- Failed payment information is stored for future reference and auditing purposes.
- The system validates the format of incoming payment notifications to ensure they are correct.
- The system provides clear feedback when it successfully stores a failed payment notification or when it encounters an error.
Changelog:
Added:
- The ability to receive and store failed payment notifications from GHL.
Changed:
- The system's logging capabilities to include failed payment notifications.
Fixed:
- None
Removed:
- None
Releaseddc763-repo/dc_crm
#4777 ProductionBilal Alam
Change Overview
Summary:
- The system now uses predefined lists for industry and state fields, making it easier to select valid options.
- Users can no longer enter free-form text for these fields, reducing errors and inconsistencies.
- The update improves data quality and makes it easier to analyze and report on industry and state information.
- The change also enhances the overall user experience by providing a more intuitive and guided data entry process.
Changelog:
Added:
- Predefined lists for industry and state fields to improve data quality and consistency.
Changed:
- Industry and state fields now use dropdown menus with predefined options instead of free-form text entry.
Fixed:
- Reduced errors and inconsistencies in industry and state data entry.
Removed:
- Free-form text entry for industry and state fields, which was prone to errors and inconsistencies.
Releaseddc763-repo/dc_crm
#4771 ProductionPT Git User
Change Overview
Summary:
- The system now logs which method was used to find a lead, making it easier to track and understand the lead search process.
- Lead search logs now include more detailed information, such as the match method used to find the lead.
- The lead search process has been updated to try multiple methods to find a lead, including searching by email, phone, and GHL contact ID.
- The system now provides more accurate and detailed logging of lead search results, including the lead ID, GHL contact ID, and match method.
Changelog:
Added:
- Logging of the match method used to find a lead
Changed:
- Lead search process to try multiple methods to find a lead
- Lead search logs to include more detailed information
Fixed:
- None
Removed:
- None
Releaseddc763-repo/dc_crm
#4768 ProductionPT Git User
Change Overview
Summary:
- The system now accurately reflects the status of canceled subscriptions.
- Canceled subscriptions are properly marked to prevent further payments.
- The update ensures consistency in handling canceled subscriptions.
- This change improves the overall management of subscription statuses.
Changelog:
Added:
- A new status update for canceled subscriptions to prevent payment events.
Changed:
- The way the system handles canceled subscriptions for consistency.
Fixed:
- Inconsistent handling of canceled subscriptions.
Removed:
- None
Releaseddc763-repo/dc_crm
#4773 ProductionPT Git User
Change Overview
Summary:
- The system now tracks when the onboarding status of a lead is updated.
- This update allows for more precise automation of workflows based on the timing of status changes.
- Automated reminders can be sent at specific times after a status change, improving follow-up efficiency.
- The change enables better management of lead onboarding processes by providing a clear timeline of status updates.
Changelog:
Added:
- The ability to track the date and time of onboarding status changes for leads.
Changed:
- The lead onboarding process now includes automated tracking of status updates.
Fixed:
- None
Removed:
- None
Releaseddc763-repo/dc_crm
#4766 ProductionBilal Alam
Change Overview
Summary:
- The system now displays workflow runs related to a lead, including those triggered on the lead itself and on related modules.
- Users can view the type of relation between the lead and the workflow run, such as direct or related.
- The system provides more detailed information about each workflow run, including the date it was entered and modified.
- The new functionality improves the visibility of workflow runs and their relationships to leads, making it easier to track and manage workflows.
Changelog:
Added:
- A new field to display the type of relation between a lead and a workflow run.
- A new function to retrieve workflow runs related to a lead, including those triggered on related modules.
Changed:
- The layout of the leads subpanel to include the new relation field and other relevant information.
- The way the system retrieves data for the leads subpanel to include related workflow runs.
Fixed:
- No fixes are included in this update.
Removed:
- No features or fields were removed in this update.
Releaseddc763-repo/dc_crm
#4764 ProductionBilal Alam
Change Overview
Summary:
- The workflow subpanel now correctly links to the workflow detail view.
- This change improves the overall user experience by providing direct access to relevant workflow information.
- It enhances the efficiency of workflow management by reducing the number of clicks required to view workflow details.
- The fix ensures that users can quickly and easily access the information they need to manage workflows effectively.
Changelog:
Added:
- Direct link to workflow detail view from the subpanel.
Changed:
- The way the subpanel links to the workflow detail view for improved usability.
Fixed:
- The issue with the subpanel link not opening the correct workflow detail view.
Removed:
- None
Releaseddc763-repo/dc_crm
#4758 ProductionBilal Alam
Change Overview
Summary:
- A new "Pending Subscription" status has been added to the system to track leads who have completed onboarding but have not yet made a successful payment.
- When a lead completes onboarding, their status will be set to "Pending Subscription" instead of "Active".
- The status will be updated to "Active" once a successful payment is made through GHL.
- This change improves the tracking and management of leads throughout the subscription process.
- It also prevents leads from being sent new invites while they are pending subscription.
- The system now handles cases where a lead's payment is pending or has failed, keeping their status as "Pending Subscription".
- This update enhances the overall user experience by providing a more accurate and up-to-date representation of a lead's status.
Changelog:
Added:
- "Pending Subscription" status to track leads who have completed onboarding but have not yet made a successful payment.
Changed:
- The status of leads who complete onboarding is now set to "Pending Subscription" instead of "Active".
- The system's handling of lead statuses has been updated to reflect the new "Pending Subscription" status.
Fixed:
- Issues with lead status tracking and management have been resolved with the introduction of the "Pending Subscription" status.
Removed:
- None
Releaseddc763-repo/dc_crm
#4755 ProductionBilal Alam
Change Overview
Summary:
- The alignment of uploaded documents has been corrected for better visibility and organization.
- This change improves the overall user experience when uploading and viewing documents.
- The update ensures that documents are displayed in a more consistent and readable format.
- The fix enhances the usability of the document upload feature, making it easier to manage and access documents.
Changelog:
Added:
- None
Changed:
- The spacing and alignment of uploaded documents have been adjusted for better display.
Fixed:
- The alignment issue with uploaded documents has been resolved.
Removed:
- None
Releaseddc763-repo/dc_crm
#4759 ProductionPT Git User
Change Overview
Summary:
- The system now captures who ordered a prequalification report and logs it in the activity stream.
- Prequalification analysis runs are now distinguished from prequalification report orders in the activity stream.
- The activity stream now provides more detailed information about prequalification events, such as who ran the analysis.
- The language used in the activity stream has been updated to better reflect the actions taken during the prequalification process.
Changelog:
Added:
- New activity stream entries for prequalification report orders and prequalification analysis runs.
Changed:
- The way prequalification events are logged in the activity stream to provide more detailed information.
- The language used in the activity stream to better reflect the actions taken during the prequalification process.
Fixed:
- None
Removed:
- None
Releaseddc763-repo/dc_crm
#4760 ProductionPT Git User
Change Overview
Summary:
- Improved accuracy in prequalification analysis labels
- Enhanced clarity in opportunity status change notifications
- Consistent language used for prequalification reports and analyses
- Better readability in system-generated messages
Changelog:
Added:
- None
Changed:
- Prequalification analysis labels for better understanding
Fixed:
- Inconsistent language in prequalification analysis labels
Removed:
- None
Releaseddc763-repo/dc_crm
#4752 ProductionPT Git User
Change Overview
Summary:
- The system now correctly associates leads with their corresponding accounts
- Lead information is more accurately passed to the password reset process
- The password reset process for leads has been improved for better functionality
- The overall lead management system has been enhanced for more efficient processing
Changelog:
Added:
- Improved lead identification in the password reset process
Changed:
- The way lead information is passed to the password reset process
Fixed:
- Inaccurate lead association issue
Removed:
- None
Releaseddc763-repo/dc_crm
#4727 ProductionBilal Alam
Change Overview
Summary:
- Job queue display names have been updated for clarity and consistency.
- The changes improve the organization and readability of job queue items.
- This update enhances the overall user experience by providing more descriptive and accurate job names.
- The new display names include more specific details about the type of job and the related data.
Changelog:
Added:
- More descriptive job names for credit reports, including the type of report and the bureau used.
Changed:
- Job queue display names have been updated to include more specific details about the job type and related data.
- The format of job names has been standardized for consistency.
Fixed:
- None
Removed:
- None
Releaseddc763-repo/dc_crm
#4749 ProductionBilal Alam
Change Overview
Summary:
- The DC process now sorts records by date entered in descending order for easier tracking of recent activities.
- The delete action has been removed from the DC process to prevent accidental data loss.
- The description field has been edited to improve data entry and display.
- The system now automatically assigns a created by user if one is not specified, ensuring that all records have an associated user.
Changelog:
Added:
- A new view for the AOW Processed module to improve data display and filtering.
- A new hook to populate the job queue position for the dc_serialization_job_queue module.
- A new function to get the activity stream user name based on the user ID.
Changed:
- The sort order for the dc_serialization_job_queue module has been changed to sort by date entered in descending order.
- The description field for the dc_serialization_job_queue module has been edited to improve data entry and display.
- The created by user assignment logic has been updated to automatically assign a user if one is not specified.
Fixed:
- The system now correctly handles cases where the created by user is not specified, preventing errors and data inconsistencies.
Removed:
- The delete action has been removed from the DC process to prevent accidental data loss.
Releaseddc763-repo/dc_crm
#4745 ProductionBilal Alam
Change Overview
Summary:
- Dates and times are now displayed in the user's local timezone, improving readability and understanding.
- The system can parse and format dates in various formats, making it more flexible and user-friendly.
- Tasks are now saved with the correct date and time, taking into account the user's timezone.
- The display of dates and times has been standardized across the system, reducing confusion and inconsistencies.
- Notes, messages, and documents are now displayed with their creation dates in the user's local timezone.
Changelog:
Added:
- New functions to format and parse dates and times in the user's local timezone.
Changed:
- The way dates and times are displayed and saved in the system, to take into account the user's timezone.
- The task saving process, to use the new date and time formatting functions.
Fixed:
- Inconsistencies in the display of dates and times across the system.
Removed:
- Old code that handled dates and times in a less flexible and less user-friendly way.
Releaseddc763-repo/dc_crm
#4743 ProductionBilal Alam
Change Overview
Summary:
- Improved lead tracking with additional workflow information
- Enhanced credit reporting and status updates
- Better organization of lead data with new subpanel layouts
- Increased auditability of lead interactions and changes
Changelog:
Added:
- New subpanel for tracking AOW processed workflows
- Additional fields for credit reporting and status updates
Changed:
- Updated field labels for clarity and consistency
- Improved audit logging for lead interactions and changes
Fixed:
- Removed redundant and unused language files
Removed:
- Unused language files for credit frozen flag and onboarding completed status
Releaseddc763-repo/dc_crm
#4740 ProductionBilal Alam
Change Overview
Summary:
- The system now provides a more concise response when a credit report is being processed.
- Users will no longer be instructed to try again shortly when a report is in progress.
- The change improves the clarity of the message displayed to users.
- It enhances the overall user experience by providing a more straightforward notification.
Changelog:
Added:
- None
Changed:
- The response message for credit report processing
Fixed:
- None
Removed:
- The instruction to try again shortly from the response message
Releaseddc763-repo/dc_crm
#4731 ProductionBilal Alam
Change Overview
Summary:
- The onboarding process now has an additional condition to determine the next status.
- Leads are now directed to either 'Onboarding' or 'active' status based on their current status.
- This change improves the automation of lead status updates.
- It enhances the overall efficiency of the onboarding process by reducing manual interventions.
Changelog:
Added:
- A conditional check to determine the lead status during onboarding.
Changed:
- The way leads are assigned a status after verification.
Fixed:
- Inconsistent status updates for leads during onboarding.
Removed:
- Automatic assignment of 'Onboarding' status without considering the lead's current status.
Releaseddc763-repo/dc_crm
#4733 ProductionPT Git User
Change Overview
Summary:
- The system now handles subscription status updates more efficiently, without requiring a specific product ID.
- Payment success is now the primary trigger for checking FICO scores and updating subscription access levels.
- The system will automatically retrieve the latest subscription status, even if a product ID is not available.
- This change aims to reduce errors and improve the overall user experience by streamlining the subscription status update process.
Changelog:
Added:
- Automatic retrieval of the latest subscription status, regardless of product ID.
Changed:
- The condition for checking FICO scores and updating subscription access levels now relies solely on payment success.
- The system's query for retrieving subscription information has been modified to prioritize non-empty product IDs and retrieve the latest subscription status.
Fixed:
- Issues related to missing product IDs, which previously prevented the system from updating subscription access levels.
Removed:
- The requirement for a specific product ID to update subscription access levels.
Releaseddc763-repo/dc_crm
#4736 ProductionBilal Alam
Change Overview
Summary:
- The system now sends more detailed information about leads to external services.
- This change helps improve the synchronization of lead data with other applications.
- It enables better tracking and management of leads from different sources.
- The update enhances the overall integration of the lead management system with other tools.
Changelog:
Added:
- The origin field is now included in the data sent to external services.
Changed:
- The system now checks the status of leads to determine the origin field value.
Fixed:
- No fixes are included in this update.
Removed:
- No features or functionality have been removed in this update.
Releaseddc763-repo/dc_crm
#4738 ProductionBilal Alam
Change Overview
Summary:
- The system now checks if a credit report is being processed for a lead before attempting to retrieve the report.
- If a report is in progress, the system returns a message indicating that the report is being processed and to try again shortly.
- This change improves the user experience by providing more accurate and up-to-date information about the status of credit reports.
- The system also handles cases where a report has been completed but no account data is available, providing a more robust and reliable reporting process.
Changelog:
Added:
- A new feature to check if a credit report is being processed for a lead.
Changed:
- The way the system handles report retrieval to include checks for report processing status.
Fixed:
- Issues with report handling that could lead to incomplete or inaccurate information.
Removed:
- None
Releaseddc763-repo/dc_crm
#4722 ProductionBilal Alam
Change Overview
Summary:
- The Customer Portal has been merged into the PQ Portal, streamlining user management.
- Swagger endpoints have been reorganized by flow for better navigation and understanding.
- New features for lead verification and signup have been added, improving the onboarding process.
- Error handling has been enhanced for better user experience and debugging.
Changelog:
Added:
- Lead verification and signup features
- Email verification with OTP for lead registration
Changed:
- Customer Portal merged into PQ Portal
- Swagger endpoints reorganized by flow
Fixed:
- Improved error handling for various endpoints
Removed:
- Redundant endpoints for broker details and count
Releaseddc763-repo/dc_crm
#4728 ProductionBilal Alam
Change Overview
Summary:
- The system now checks for empty credit reports and returns an error message if no account data is found.
- This change helps prevent further processing of incomplete credit reports.
- A new function has been added to update a lead's SSN and trigger a new credit report pull.
- The update SSN function also validates the SSN format to ensure it is 9 digits long.
Changelog:
Added:
- A check for empty credit reports to prevent processing of incomplete data
- A function to update a lead's SSN and queue a new credit report pull
Changed:
- The system's behavior when encountering a completed credit report with no account data
Fixed:
- The issue of incomplete credit reports being processed without error messages
Removed:
- None
Releaseddc763-repo/dc_crm
#4725 ProductionBilal Alam
Change Overview
Summary:
- The prequalification process for leads is now more streamlined, focusing on a single method of signature verification.
- The system no longer checks for specific acknowledgement fields related to PQ Portal, making the process more efficient.
- Leads are now considered to have completed signature requirements if they have a GHL-style signature document attached.
- The removal of redundant checks and hooks improves overall system performance and reduces complexity.
Changelog:
Added:
- None
Changed:
- The method for determining if a lead has completed signature requirements has been updated to rely solely on the presence of a GHL-style signature document.
Fixed:
- None
Removed:
- The PQ Portal prequal hook and related functions, which are no longer necessary with the updated signature verification process.
Releaseddc763-repo/dc_crm
#4720 ProductionPT Git User
Change Overview
Summary:
- The system now automatically updates the "Years in Business" field when the "Date Est" field is changed.
- This update is based on the estimated year the business started and the current year.
- The calculation ensures that the "Years in Business" field reflects the correct number of years since the business started.
- The automatic update improves data accuracy and reduces manual entry errors.
Changelog:
Added:
- Automatic update of "Years in Business" field based on "Date Est" changes.
Changed:
- The system's behavior when updating the "Date Est" field now includes synchronizing the "Years in Business" field.
Fixed:
- Inconsistent or outdated "Years in Business" data due to manual entry errors.
Removed:
- None
Releaseddc763-repo/dc_crm
#4715 ProductionBilal Alam
Change Overview
Summary:
- The system now checks for empty credit reports that have been completed but contain no account data.
- If such a report is found, the system returns an error message instead of the report data.
- A new API endpoint has been added to update a lead's SSN and queue a new credit report pull.
- The update SSN endpoint accepts the lead ID and new SSN as parameters and returns a success message if the update is successful.
- The system now handles cases where the submitted SSN is invalid or unchanged.
Changelog:
Added:
- A new function to check if a completed credit report has no account data.
- A new API endpoint to update a lead's SSN and queue a new credit report pull.
Changed:
- The customer portal data retrieval API now checks for empty completed credit reports and returns an error message if found.
- The API documentation has been updated to reflect the changes.
Fixed:
- The system now correctly handles cases where the submitted SSN is invalid or unchanged.
Removed:
- None
Releaseddc763-repo/dc_crm
#4717 ProductionPT Git User
Change Overview
Summary:
- The contract panel now has improved responsiveness for better viewing on different screen sizes.
- Font sizes in the contract panel have been adjusted for easier reading.
- The layout of the contract panel has been fixed to prevent fields from overflowing and merging.
- The design of the contract panel has been enhanced for a more user-friendly experience.
Changelog:
Added:
- Improved responsiveness for the contract panel on various screen sizes.
Changed:
- Font sizes in the contract panel for better readability.
- Layout of the contract panel to prevent field overflows.
Fixed:
- Issue with fields merging and overflowing in the contract panel.
Removed:
- None
Releaseddc763-repo/dc_crm
#4714 ProductionPT Git User
Change Overview
Summary:
- Enhanced lead search functionality to improve matching accuracy
- Added ability to search for leads by email and phone number in addition to GHL contact ID
- Improved search logic to prioritize most recently modified leads
- Increased efficiency in lead search process to reduce errors and improve overall system performance
Changelog:
Added:
- New search parameters for email and phone number to improve lead matching
Changed:
- Lead search logic to prioritize email and phone number matches over GHL contact ID
- Search process to use most recently modified leads for better accuracy
Fixed:
- Issues with lead search not finding matches due to limited search parameters
Removed:
- None
Releaseddc763-repo/dc_crm
#4712 ProductionBilal Alam
Change Overview
Summary:
- Improved API documentation with standardized examples for better understanding
- Enhanced readability of API requests and responses with compact examples
- Simplified representation of complex data structures for easier consumption
- Increased consistency in API documentation for reduced confusion
Changelog:
Added:
- Generic placeholders for sensitive information in API examples
Changed:
- API documentation examples to use compact and standardized formats
- Representation of session IDs and other identifiers in API examples
Fixed:
- Inconsistencies in API documentation examples
Removed:
- Specific session IDs and sensitive information from API examples
Releaseddc763-repo/dc_crm
#4710 ProductionBilal Alam
Change Overview
Summary:
- The customer portal signup and login features are no longer available in the documentation.
- This change helps keep the system up-to-date by removing outdated features.
- It improves the overall user experience by reducing clutter and focusing on current functionality.
- The removal of these features does not affect existing customer portal functionality.
Changelog:
Removed:
- Customer portal signup feature from documentation
- Customer portal login feature from documentation
Changed:
- Documentation to reflect current system capabilities
Fixed:
- None
Added:
- None
Releaseddc763-repo/dc_crm
#4706 ProductionBilal Alam
Change Overview
Summary:
- The layout for selecting discount offers has been improved for better user experience.
- The discount offer selection field now adjusts its width based on the type of offer chosen.
- The layout is more responsive and consistent with other parts of the system.
- The changes make it easier to use and understand the discount offer selection process.
Changelog:
Added:
- A new function to synchronize the discount offer plan layout.
Changed:
- The width of the discount offer selection field is now adjusted dynamically.
- The layout of the discount offer plan section has been updated for consistency.
Fixed:
- Issues with the layout of the discount offer selection field have been resolved.
Removed:
- Hardcoded width settings for the discount offer selection field.
Releaseddc763-repo/dc_crm
#4703 ProductionBilal Alam
Change Overview
Summary:
- The system now tracks changes to subscription access levels for better auditing and security.
- Lead access levels are calculated based on their FICO scores, ensuring more accurate and personalized access control.
- The system can now automatically fetch prequal reports when a lead is eligible, streamlining the subscription process.
- Lead updates are now handled more efficiently, reducing the risk of data inconsistencies and errors.
Changelog:
Added:
- Automatic prequal report fetching for eligible leads
Changed:
- Lead access levels are now calculated based on FICO scores
- Lead updates are now handled through a more efficient and reliable method
Fixed:
- Issues with lead updates and data consistency have been resolved
Removed:
- Redundant lead update queries have been removed to improve system efficiency
Releaseddc763-repo/dc_crm
#4700 ProductionBilal Alam
Change Overview
Summary:
- The system now tracks changes to lead credit pull disclaimers and digital signature acknowledgments.
- This change improves the ability to monitor and audit lead interactions.
- It enhances data integrity by keeping a record of all changes made to these fields.
- The update supports better compliance and risk management by providing a clear audit trail.
Changelog:
Added:
- Auditing capability for lead credit pull disclaimers and digital signature acknowledgments.
Changed:
- The way the system handles tracking of lead interactions, now including auditing for specific fields.
Fixed:
- None
Removed:
- None
Releaseddc763-repo/dc_crm
#4698 ProductionBilal Alam
Change Overview
Summary:
- The system now allows better access to API documentation for developers.
- Previously hidden API entry points are now visible and accessible.
- This change improves the overall usability of the system for integrations.
- It enables easier discovery and use of API features for external applications.
Changelog:
Added:
- Visibility to previously hidden API entry points
Changed:
- System configuration to allow better access to API documentation
Fixed:
- Issue with API entry point being hidden from view
Removed:
- None
Releaseddc763-repo/dc_crm
#4696 ProductionBilal Alam
Change Overview
Summary:
- The layout for selecting discount offers has been improved for better user experience.
- The width of the discount offer selection field has been standardized for consistency.
- The display of discount offer information has been made more compact and organized.
- The overall design of the discount offer section has been refined for easier navigation.
Changelog:
Added:
- A more consistent and compact layout for discount offer information.
Changed:
- The width of the discount offer selection field to improve consistency.
- The display of discount offer custom labels to improve readability.
Fixed:
- Inconsistent spacing and sizing issues in the discount offer section.
Removed:
- Unnecessary styling options to simplify the design and improve maintainability.
Releaseddc763-repo/dc_crm
#4687 ProductionBilal Alam
Change Overview
Summary:
- The system now records SMS two-factor authentication messages sent to leads as notes in their profiles.
- This change improves the tracking and auditing of SMS messages related to two-factor authentication.
- It provides a clear record of when SMS messages were sent, which can be useful for troubleshooting and customer support.
- The new functionality enhances the overall security and transparency of the lending process.
Changelog:
Added:
- The ability to log SMS OTP messages as lead notes.
Changed:
- The way the system handles SMS two-factor authentication messages for leads.
Fixed:
- No fixes are included in this change.
Removed:
- No features or functionality were removed in this change.
Releaseddc763-repo/dc_crm
#4694 ProductionBilal Alam
Change Overview
Summary:
- Improved organization of API documentation for easier navigation and understanding
- Added categorization of API endpoints using tags for better discoverability
- Enhanced documentation structure to reduce complexity and improve readability
- Removed outdated or redundant API endpoints to simplify the documentation
Changelog:
Added:
- New tags for categorizing API endpoints, such as SuiteCRM Default API v4, Authentication, and Broker Portal
- Tag groups for organizing related API endpoints together
Changed:
- API endpoint documentation to include tags for categorization and improved descriptions
- Organization of API endpoints to reduce complexity and improve readability
Fixed:
- Removed redundant or outdated API endpoints to simplify the documentation
Removed:
- The /sendtoCentrex API endpoint, which is no longer needed or supported
Releaseddc763-repo/dc_crm
#4690 ProductionBilal Alam
Change Overview
Summary:
- Passwords are no longer logged, reducing the risk of sensitive information exposure.
- Passwords are removed from data after verification, minimizing the chance of unauthorized access.
- The system now handles incorrect passwords more securely, without logging sensitive details.
- Overall security and compliance have been enhanced by removing unnecessary password logging and storage.
Changelog:
Added:
- Enhanced password handling for improved security.
Changed:
- Password verification process to prevent logging of sensitive information.
- Data processing to remove passwords after verification.
Fixed:
- Security vulnerability related to password logging and storage.
Removed:
- Unnecessary logging of passwords and sensitive data.
Releaseddc763-repo/dc_crm
#4691 ProductionPT Git User
Change Overview
Summary:
- Improved handling of contract-out fields for BFA agreements
- Enhanced support for BFA Full Pay and Payment Plan documents
- Simplified storage and management of contract-out field values
- Updated UI to match custom discount input and upfront fee field widths
- Introduced JSON storage for contract-out field values keyed by document template name
Changelog:
Added:
- Contract-out fields for BFA Full Pay and Payment Plan documents
- JSON storage for contract-out field values
- New utility functions for managing contract-out fields
Changed:
- Improved handling of contract-out fields for BFA agreements
- Updated UI styling for custom discount input and upfront fee fields
Fixed:
- Issues with persisting contract-out field values after sending documents
Removed:
- Legacy code for handling contract-out fields
Releaseddc763-repo/dc_crm
#4682 ProductionBilal Alam
Change Overview
Summary:
- The system can now verify if a lead has completed the custom lead signup process.
- This check is done by providing the lead's email address and a valid portal session.
- The system returns a status indicating whether the lead has completed the signup process.
- This feature improves the overall customer portal experience by allowing for more accurate tracking of lead engagement.
- It also enhances security by verifying the existence of portal credentials for a given email address.
Changelog:
Added:
- A new API endpoint to check if a lead has completed the custom lead signup process.
Changed:
- The system's ability to track lead engagement has been enhanced with the addition of the lead signup completion check.
Fixed:
- None
Removed:
- None
Releaseddc763-repo/dc_crm
#4678 ProductionBilal Alam
Change Overview
Summary:
- The system now integrates with Monevo to match lenders with potential borrowers.
- This integration enables the submission of applications to Monevo and retrieval of offer results.
- The system handles building the request payload from a lead and submitting the application.
- The integration also includes polling the results endpoint to fetch offers until they are generated or a limit is reached.
- Error handling has been implemented to manage potential issues with the Monevo API.
- The system can now parse XML responses from Monevo and extract relevant information such as offers and summaries.
Changelog:
Added:
- Monevo lender matching integration
Changed:
- None
Fixed:
- None
Removed:
- None
Releaseddc763-repo/dc_crm
#4684 ProductionBilal Alam
Change Overview
Summary:
- The system now considers the age of a record when merging changes, providing more control over data updates.
- Records less than one year old have protected fields that are not overwritten if the incoming value differs, with attempted changes logged in a note.
- Records older than one year have protected fields updated with incoming values, and any replaced values are saved in a note for reference.
- The audit notes for these changes are now more descriptive and clearly indicate whether the record was updated or the changes were logged.
Changelog:
Added:
- New logic to determine if a record is older than one year and apply different merge rules accordingly.
- More descriptive audit notes for changes made to records.
Changed:
- The way protected fields are handled during record updates, considering the record's age.
- The naming and content of audit notes to better reflect the changes made.
Fixed:
- None
Removed:
- None
Releaseddc763-repo/dc_crm
#4672 ProductionBilal Alam
Change Overview
Summary:
- The system now allows for dynamic tracking of Swagger API documentation in git.
- Each server environment can have its own unique Swagger API URL.
- The Swagger API documentation can be easily updated for different environments.
- The system provides a flexible way to manage API documentation across various environments.
Changelog:
Added:
- Ability to track Swagger API documentation in git with per-environment server URL.
- Environment variable file (.env) to store server-specific API URLs and descriptions.
Changed:
- The way Swagger API documentation is served, now using a dynamic configuration.
- The default server URL is now overridden by the .env file.
Fixed:
- Removed hardcoded server URLs from the Swagger API documentation.
Removed:
- Hardcoded server URLs for staging and production environments from the Swagger API documentation.
Releaseddc763-repo/dc_crm
#4675 ProductionBilal Alam
Change Overview
Summary:
- The system now supports an alternate prequalification signature path using PQ Portal acknowledgement fields.
- This change allows leads to complete prequalification requirements without needing a traditional signature document.
- The new functionality checks for the completion of PQ Portal acknowledgement fields and triggers prequal report pulls when eligible.
- The system also prevents duplicate job queue creation when the same lead is eligible for prequal report pulls multiple times.
Changelog:
Added:
- Support for PQ Portal acknowledgement fields as an alternate prequal signature path.
- A new logic hook to trigger prequal report pulls when PQ Portal acknowledgement fields are completed.
Changed:
- The prequalification logic to include checks for PQ Portal acknowledgement fields.
- The document logic hook to use the new maybeTriggerPrequalReportForLead function.
Fixed:
- Duplicate job queue creation when the same lead is eligible for prequal report pulls multiple times.
Removed:
- None
Releaseddc763-repo/dc_crm
#4679 ProductionBilal Alam
Change Overview
Summary:
- The system now prevents users from changing the Fico score field once a score has been set.
- This change helps maintain data integrity and accuracy.
- It ensures that Fico scores are not altered accidentally or intentionally after they have been determined.
- The protection applies to all Fico score fields, including Experian, Transunion, and Equifax.
Changelog:
Added:
- Protection for Fico score fields to prevent editing once a score is set.
Changed:
- Fico score fields now display a message indicating that they cannot be changed once a score is set.
Fixed:
- None
Removed:
- Ability for users to edit Fico score fields after a score has been set.
Releaseddc763-repo/dc_crm
#4664 ProductionPT Git User
Change Overview
Summary:
- Improves the display of history records for leads by fixing an issue where the record count was incorrect.
- Ensures that the pagination of history records works correctly, even after deleting records or using the browser's back button.
- Enhances the overall user experience by providing accurate record counts and proper pagination.
- Fixes a problem where the subpanel would show an incorrect offset, resulting in an empty list of records.
Changelog:
Added:
- A custom class to handle the display of history records for leads, which fixes the offset issue.
Changed:
- The way the subpanel handles pagination for history records, to ensure accurate record counts and proper pagination.
Fixed:
- An issue where the subpanel would show an incorrect offset, resulting in an empty list of records.
- A problem where the record count was incorrect after deleting records or using the browser's back button.
Removed:
- None
Releaseddc763-repo/dc_crm
#4665 ProductionBilal Alam
Change Overview
Summary:
- Improved validation for lead signup portal status to prevent duplicate signups
- Enhanced error handling for various portal status scenarios, such as active, onboarding, verification pending, and canceled
- Added checks to ensure portal signup is allowed based on the lead's portal status
- Improved logging and messaging for failed signup attempts
Changelog:
Added:
- Validation checks for lead portal status during signup
- Error handling for different portal status scenarios
Changed:
- Improved logic for determining if portal signup is allowed based on the lead's portal status
- Enhanced logging and messaging for failed signup attempts
Fixed:
- Issue with duplicate signups due to lack of portal status validation
Removed:
- None
Releaseddc763-repo/dc_crm
#4668 ProductionBilal Alam
Change Overview
Summary:
- The system now tracks API documentation in git, allowing for better version control and management of API changes.
- This change improves the transparency and accessibility of API documentation for developers and stakeholders.
- It enables easier collaboration and review of API documentation, reducing errors and inconsistencies.
- The tracking of API documentation in git also facilitates auditing and compliance with regulatory requirements.
Changelog:
Added:
- API documentation tracking in git
Changed:
- Git ignore settings to allow tracking of API documentation files
Fixed:
- None
Removed:
- None
Releaseddc763-repo/dc_crm
#4660 ProductionPT Git User
Change Overview
Summary:
- The system now prioritizes using a person's date of birth for identification when available.
- This change aims to reduce the reliance on Social Security Numbers for identification purposes.
- The system will automatically fall back to using the SSN if the date of birth is not available.
- This update improves the handling of sensitive personal information and enhances overall system flexibility.
Changelog:
Added:
- A new feature to automatically determine the best identifier (date of birth or SSN) for each person.
Changed:
- The default identifier used by the system is now the date of birth instead of the SSN.
- The system's logic for handling missing identifiers has been updated to prioritize date of birth.
Fixed:
- Issues related to missing identifiers have been resolved by implementing a fallback mechanism.
Removed:
- Redundant code related to identifier handling has been removed to simplify the system.
Releaseddc763-repo/dc_crm
#4654 ProductionBilal Alam
Change Overview
Summary:
- The system now tracks the onboarding status of portal users, allowing for better management of the onboarding process.
- A new status called "Onboarding" has been added to reflect the current state of a user's onboarding process.
- The system can now mark a user's onboarding as complete, updating their status to "active" and indicating that they have finished the onboarding process.
- This change enables more efficient tracking and completion of the onboarding process for portal users.
Changelog:
Added:
- A new onboarding status to track the current state of a user's onboarding process.
- A feature to mark a user's onboarding as complete.
Changed:
- The default status for new portal users is now "Onboarding" instead of "active".
- The system now updates a user's status to "active" when their onboarding is marked as complete.
Fixed:
- None
Removed:
- None
Releaseddc763-repo/dc_crm
#4657 ProductionBilal Alam
Change Overview
Summary:
- The system now checks the status of a lead before sending an email invitation to the customer portal.
- If the lead's status is active, the system will not send an email invitation to prevent duplicate invitations.
- The system also handles other statuses such as inactive, sent invite, verification pending, onboarding, and canceled, and provides appropriate messages for each status.
- The goal of this change is to improve the efficiency and accuracy of the email invitation process and prevent unnecessary emails from being sent to leads.
Changelog:
Added:
- A new validation process to check the lead's status before sending an email invitation.
Changed:
- The system's behavior when a lead's status is active or other specific statuses, to prevent unnecessary email invitations.
Fixed:
- The issue of duplicate email invitations being sent to leads with an active status.
Removed:
- The previous behavior of sending email invitations regardless of the lead's status.
Releaseddc763-repo/dc_crm
#4631 ProductionBilal Alam
Change Overview
Summary:
- The detailed view of bank information has been simplified
- Removal of specific bank details improves data organization
- The change affects how bank trade information is displayed
- The update focuses on streamlining the user interface
Changelog:
Removed:
- Detailed trade information for multiple banks, including American Express, Bank of America, Capital One, Chase, Citibank, US Bank, and Wells Fargo
Releaseddc763-repo/dc_crm
#4627 ProductionBilal Alam
Change Overview
Summary:
- Improved security by switching to Bitbucket API tokens for authentication
- Enhanced compatibility with Bitbucket's latest authentication methods
- Simplified configuration by using a single API token for authentication
- Increased reliability by handling authentication errors more effectively
Changelog:
Added:
- Support for Bitbucket API tokens for authentication
Changed:
- Authentication method from app passwords to API tokens
- Configuration requirements to use Bitbucket email and API token
Fixed:
- Compatibility issues with deprecated app passwords
Removed:
- Dependent on deprecated Bitbucket app passwords for authentication
Releaseddc763-repo/dc_crm
#4650 ProductionBilal Alam
Change Overview
Summary:
- A test is being conducted to verify the changelog automation process.
- The goal is to confirm that the system can receive and process updates correctly.
- This test will help ensure that changes are properly recorded and tracked.
- The test is a one-time verification and will be removed after completion.
Changelog:
Added:
- A test marker to verify the changelog automation process.
Changed:
- None
Fixed:
- None
Removed:
- None
Releaseddc763-repo/dc_crm
#4652 ProductionBilal Alam
Change Overview
Summary:
- Improves the accuracy of Bitbucket pull request diff URLs to ensure correct changelog updates.
- Enhances the security and reliability of curl requests for Bitbucket API interactions.
- Increases the efficiency of database queries by removing unnecessary limits.
- Simplifies the authentication process for Bitbucket API tokens.
Changelog:
Added:
- A new function to resolve pull request diff URLs directly from the Bitbucket API.
Changed:
- The way Bitbucket API tokens are decoded and used for authentication.
- The curl request options to improve connection timeouts and response handling.
Fixed:
- An issue where the diff URL was not being correctly retrieved from the payload.
- A problem with the curl request authentication that could cause errors.
Removed:
- A test file that is no longer needed after verification of the Bitbucket changelog automation.
Releaseddc763-repo/dc_crm
#4628 ProductionBilal Alam
Change Overview
Summary:
- The system now supports a new feature called Offer Wall Generic, which provides a platform for managing offers and promotions.
- A new module has been added to handle Offer Wall Generic information, accessible only to the administrator.
- The system now includes a dropdown list for bank names, allowing users to select from a predefined list of banks.
- The system also includes categories and credit range options for Offer Wall Generic, enabling more targeted and personalized offers.
- A new relationship has been established between leads and Offer Wall Generic, allowing for more effective management of leads and offers.
- The system now supports card thumbnails, enabling users to view images of cards.
Changelog:
Added:
- Offer Wall Generic module
- Bank name dropdown list
- Categories and credit range options for Offer Wall Generic
- Relationship between leads and Offer Wall Generic
- Card thumbnail feature
Changed:
- Administration menu to include Offer Wall Generic information
Fixed:
- No fixes are included in this update
Removed:
- No features or modules have been removed in this update
Releaseddc763-repo/dc_crm
#4624 ProductionBilal Alam
Change Overview
Summary:
- Enhanced lead tracking by introducing a new relationship between leads and education records
- Allows for the tracking of video progress for each education record associated with a lead
- Provides a new API endpoint to update education video progress for a lead
- Provides a new API endpoint to retrieve education progress for a lead
Changelog:
Added:
- New relationship between leads and education records to track video progress
- API endpoint to update education video progress for a lead
- API endpoint to retrieve education progress for a lead
Changed:
- Existing database schema to accommodate the new relationship and video progress tracking
Fixed:
- No fixes are included in this change
Removed:
- No features or functionality were removed in this change
Releaseddc763-repo/dc_crm
#4622 ProductionBilal Alam
Change Overview
Summary:
- The system now automatically sets portal access levels based on FICO scores from reports.
- Email invitations for portal access are sent to customers after their first successful subscription.
- The system checks for specific conditions before sending email invitations, such as report completion and automated report status.
- Portal access and email invitations are only sent for TransUnion reports with no system errors.
Changelog:
Added:
- A new feature to send email invitations for portal access after the first successful subscription.
- A check for TransUnion reports with no system errors before sending email invitations.
Changed:
- The system now automatically sets portal access levels based on FICO scores from reports.
- The conditions for sending email invitations have been updated to include report completion and automated report status.
Fixed:
- No specific fixes are mentioned, but the updates improve the overall functionality of portal access and email invitations.
Removed:
- No features or functionalities have been removed in this update.
Releaseddc763-repo/dc_crm
#4620 ProductionBilal Alam
Change Overview
Summary:
- The system now captures more accurate customer information during registration.
- Customer portal sign-ups are more efficient and reliable.
- The system can better track customer interactions and history.
- Registration processes are more streamlined, reducing potential errors.
Changelog:
Added:
- The ability to associate a unique identifier with customer portal registrations.
Changed:
- The way customer information is collected and stored during registration.
Fixed:
- Inaccuracies in customer data capture during the registration process.
Removed:
- None
Releaseddc763-repo/dc_crm
#4613 ProductionPT Git User
Change Overview
Summary:
- The way loan amounts are calculated has been improved for accuracy.
- A new rule has been added to adjust the calculation based on the credit limit.
- This change affects how personal loan amounts are determined for customers.
- The update ensures that loan amounts are displayed in a clear and readable format.
Changelog:
Added:
- A conditional multiplier to adjust loan amount calculations based on credit limit.
Changed:
- The formula used to calculate personal loan amounts to make it more accurate.
Fixed:
- The display of loan amounts to ensure they are formatted correctly with commas.
Removed:
- None
Releaseddc763-repo/dc_crm
#4615 ProductionPT Git User
Change Overview
Summary:
- The system now tracks the source of Social Security Numbers (SSN) for leads.
- This change allows for better management and reporting of lead information.
- The system can now record whether a credit report was fetched using an SSN or Date of Birth (DOB).
- This update improves data accuracy and provides more detailed information for lead management and reporting.
Changelog:
Added:
- SSN source tracking for leads
- Option to record the type of identifier used to fetch credit reports (SSN or DOB)
Changed:
- Updated lead management to include SSN source information
- Modified credit report fetching to record the type of identifier used
Fixed:
- No fixes are included in this update
Removed:
- No features or functionality were removed in this update
Releaseddc763-repo/dc_crm
#4618 ProductionBilal Alam
Change Overview
Summary:
- The system now automatically sorts lists by the date they were entered, making it easier to find recent items.
- Users can filter search results to only show items assigned to them, improving their ability to manage their workload.
- The search function has been enhanced to allow for range searches on dates, such as start and renewal dates.
- The layout of the search form has been improved for better usability, with clear labels and organized fields.
Changelog:
Added:
- New search filters for start and renewal dates
- Ability to filter by assigned user
- Range search functionality for dates
Changed:
- Default sort order for lists is now by date entered
- Search form layout has been improved
Fixed:
- No fixes are included in this update
Removed:
- No features or functionality have been removed
Releaseddc763-repo/dc_crm
#4610 ProductionBilal Alam
Change Overview
Summary:
- The list of loan purposes has been expanded to provide more specific options for customers.
- This change allows customers to more accurately describe the intended use of their loan.
- The updated options will help improve data collection and analysis for loan purposes.
- The new options will also enhance the overall user experience by providing more relevant and descriptive choices.
Changelog:
Added:
- New loan purpose options, including Expansion, Working Capital, Payroll, and others.
Changed:
- The loan purpose list now includes more specific and detailed options.
Fixed:
- None
Removed:
- None
Releaseddc763-repo/dc_crm
#4465 ProductionBilal Alam
Change Overview
Summary:
- Improved security for lead login by introducing session-assisted and lead ID-based authentication methods
- Enhanced password management for portal users, including validation and error handling
- Increased robustness in handling lead credentials and session creation
- Better logging and error messaging for debugging and user feedback
Changelog:
Added:
- New authentication modes for leads, including session-assisted and lead ID-based login
- Validation for required parameters in password update requests
- Improved error handling and logging for password update failures
Changed:
- Existing lead login functionality to support new authentication modes
- Password update process to use a valid portal session ID
- Error messaging and logging to provide clearer feedback
Fixed:
- Issues with lead authentication and password updates
- Insecure password handling and potential vulnerabilities
Removed:
- None
Releaseddc763-repo/dc_crm
#4608 ProductionBilal Alam
Change Overview
Summary:
- The system now removes empty options from dropdown lists, improving user experience.
- This change helps prevent confusion by hiding unnecessary options.
- Data quality is improved by excluding empty values from responses.
- The overall usability of the system is enhanced by providing more relevant options.
Changelog:
Added:
- Ability to filter out empty enum options from responses.
Changed:
- The way enum options are retrieved and returned to users.
Fixed:
- Issue with empty options being displayed in dropdown lists.
Removed:
- Empty options from enum values returned by the system.
Releaseddc763-repo/dc_crm
#4612 ProductionBilal Alam
Change Overview
Summary:
- Improved security checks to verify the origin of requests, reducing the risk of unauthorized access.
- Enhanced host verification to allow for more flexible and accurate checks.
- Increased reliability of lead synchronization by accommodating different server configurations.
- Better handling of empty or missing referer information to prevent false negatives.
Changelog:
Added:
- Additional host verification methods to improve security and flexibility.
Changed:
- Host verification logic to accept matches on multiple server variables, improving accuracy.
Fixed:
- Issue with empty or missing referer information causing false negatives.
Removed:
- None
Releaseddc763-repo/dc_crm
#4606 ProductionBilal Alam
Change Overview
Summary:
- The system now includes a new lead status called "LG App" to categorize leads from this source.
- Leads with the "LG App" status are automatically tagged with "Synced to GHL - LG App" for easier tracking.
- The system checks if a lead is new and has required fields (first name, last name, email) before syncing it with GoHighLevel (GHL).
- The syncing process now only runs for requests originating from allowed hosts, enhancing security.
- Two new lead sources, "CreditCon 2026" and "Lending Genie", have been added to the system.
Changelog:
Added:
- New lead status "LG App"
- New lead sources "CreditCon 2026" and "Lending Genie"
- Automatic tagging of "LG App" leads with "Synced to GHL - LG App"
Changed:
- Syncing process now checks for allowed hosts and required lead fields
Fixed:
- None
Removed:
- None
Releaseddc763-repo/dc_crm
#4600 ProductionBilal Alam
Change Overview
Summary:
- The way leads are categorized by their state of formation has been improved for better accuracy.
- The options for lead formation states have been updated to provide more relevant choices.
- The user experience for editing leads has been enhanced by removing unnecessary features.
- The overall quality of lead data is expected to increase due to these changes.
Changelog:
Added:
- More accurate lead formation state options
Changed:
- The way lead formation states are categorized
Fixed:
- Inaccurate lead formation state options
Removed:
- Unnecessary phone mask script from the lead edit view
Releaseddc763-repo/dc_crm
#4602 ProductionBilal Alam
Change Overview
Summary:
- The system now includes Credit Card as a loan type option for users to select.
- This addition provides more flexibility and accuracy in loan type classification.
- Users can now specify Credit Card as the loan type, improving data consistency.
- The update enhances the overall user experience by providing a more comprehensive list of loan types.
Changelog:
Added:
- Credit Card as a loan type option
Changed:
- The list of available loan types to include Credit Card
Fixed:
- None
Removed:
- None
Releaseddc763-repo/dc_crm
#4604 ProductionBilal Alam
Change Overview
Summary:
- The list of loan types available for selection has been revised.
- Credit card is no longer considered a loan type.
- This change helps to better categorize and differentiate between loan types.
- It improves the overall accuracy and consistency of loan type classifications.
Changelog:
Added:
- None
Changed:
- Loan type categorization for better accuracy
Fixed:
- Inconsistent loan type classification
Removed:
- Credit card as a loan type option
Summary:
- Improved handling of credit report errors, including "Credit Frozen" and "System Error" states
- Enhanced retry mechanism for fetching credit reports, reducing the likelihood of errors
- Updated industry field naming convention for consistency across the application
- Streamlined user experience for credit report updates and error handling
Changelog:
Added:
- Retry mechanism for fetching credit reports to handle temporary errors
Changed:
- Industry field naming convention from "industryTypeC" to "industryC" for consistency
- Credit report error handling to use a more robust and centralized approach
Fixed:
- Issues with credit report updates, including "Credit Frozen" and "System Error" states
- Inconsistent retry mechanisms for different error types
Removed:
- Redundant code and variables related to outdated credit report error handling approaches
Summary:
- The system now keeps the loading screen active after payment until the credit report pull is complete, preventing the paywall from appearing prematurely.
- This change improves the user experience by reducing flashes of the paywall and providing a smoother payment process.
- The system now correctly handles the payment return pending state, ensuring that the loader remains active until the credit report pull is finished.
- The payment return pending flag is now cleared only when the credit report pull is complete or when payment fails, ensuring that the system remains in the correct state.
Changelog:
Added:
- A new state to track whether the system is reloading after payment.
Changed:
- The payment return pending flag is now cleared only when the credit report pull is complete or when payment fails.
- The system now waits for the credit report pull to finish before clearing the payment return pending flag.
Fixed:
- The paywall no longer flashes prematurely after payment.
- The system now correctly handles the payment return pending state.
Removed:
- The automatic clearing of the payment return pending flag after a 5-second delay.
Summary:
- A new knowledge base feature has been added to the system, allowing users to ask questions and receive answers.
- The knowledge base includes a chatbot that can respond to user queries.
- An admin panel has been created for managing knowledge base entries, including adding, editing, and deactivating entries.
- A feedback system has been implemented, enabling users to provide feedback on the knowledge base entries.
- A jobs page has been added to track upload and sync processing history.
Changelog:
Added:
- Knowledge base feature with chatbot functionality
- Admin panel for managing knowledge base entries
- Feedback system for users to provide feedback on knowledge base entries
- Jobs page for tracking upload and sync processing history
Changed:
- None
Fixed:
- None
Removed:
- None
Summary:
- The dashboard now loads more efficiently, reducing the time it takes to display user information.
- The system no longer displays a credit report processing message with unnecessary details.
- Payment return delays are now handled more effectively, improving the overall user experience.
- Access to certain routes is now enforced more consistently, ensuring that users can only access authorized areas.
Changelog:
Added:
- A delay to ensure that payment return webhooks can settle before proceeding with user requests.
Changed:
- The way the system handles credit report processing, removing unnecessary message details.
- The payment return delay mechanism to clear the pending flag after the delay.
Fixed:
- Inconsistent access enforcement for certain routes, ensuring that users can only access authorized areas.
Removed:
- Unnecessary code related to subscription status and payment return pending checks.
Summary:
- The form's conditional logic has been simplified and made more efficient.
- Fields can now be shown or hidden based on specific conditions, improving the user experience.
- The form's validation has been improved to handle conditional requirements.
- The Google Maps API integration has been updated for better performance and usability.
Changelog:
Added:
- A new function to evaluate conditional logic for showing or hiding fields.
- Support for appending options to select fields.
- Improved error handling for Google Maps API integration.
Changed:
- The form's conditional logic has been refactored for better performance and readability.
- The Google Maps API integration has been updated to use a more efficient approach.
- The form's validation logic has been improved to handle conditional requirements.
Fixed:
- Issues with the form's conditional logic have been resolved.
- Problems with the Google Maps API integration have been fixed.
Removed:
- Redundant code has been removed to improve performance and readability.
Summary:
- The system now displays a loading screen when credit report processing is in progress.
- Users will see a message indicating that their credit report is being processed.
- The system suppresses certain modals, such as paywall and SSN correction, while credit report processing is ongoing.
- After payment confirmation, the dashboard data is refreshed to reflect the updated status.
Changelog:
Added:
- Credit report processing handling to the dashboard layout.
- A loading screen with a message indicating credit report processing.
Changed:
- The system now polls for updates while credit report processing is in progress.
- The dashboard access controller now checks for credit report processing status.
Fixed:
- None
Removed:
- None
Summary:
- The onboarding process for new users has been enhanced to include additional steps and checks.
- Access control has been improved with the introduction of a centralized modal orchestrator.
- The system now handles multiple modal windows more efficiently, ensuring only one modal is shown at a time based on priority.
- Users are now prompted to add their phone number as part of the onboarding process, improving security and communication.
Changelog:
Added:
- A new impersonation panel to manage user access and simulate different scenarios.
- A phone number addition modal to enhance user security and communication.
- Support for blank credit report handling and SSN correction.
Changed:
- The logic for determining when to show the onboarding process has been updated to include more scenarios.
- The access modal orchestrator now prioritizes modals based on their urgency and importance.
Fixed:
- Issues with multiple modals being shown at the same time have been resolved.
- The onboarding process now correctly handles different user scenarios and edge cases.
Removed:
- Redundant code and unnecessary modal logic have been removed to improve system efficiency.
Summary:
- Simplified the onboarding process with clearer consent labels and disclosures
- Enhanced user experience with more intuitive electronic signature and credit pull disclaimer acceptance
- Improved data accuracy by pre-filling user information where possible
- Streamlined the submission process with automated updates to user modules
Changelog:
Added:
- New consent labels for electronic signature and credit pull disclaimer
- Automated build of onboarding consent payload
Changed:
- Improved checkbox labels for electronic signature and credit pull disclaimer
- Updated user module updates to include additional business financial information
Fixed:
- None
Removed:
- Redundant code and unnecessary user module updates
Summary:
- Enhanced error messages for Google sign-in failures to provide clearer explanations of what went wrong
- Added more specific error handling for different types of Google sign-in errors, such as account existence or unknown issues
- Improved user experience by providing more informative and actionable error messages
- Updated the sign-in process to handle errors in a more user-friendly way
Changelog:
Added:
- New error handling system for Google sign-in errors
- More detailed error messages for different types of sign-in errors
Changed:
- The way errors are displayed to users during the Google sign-in process
- The sign-in process now handles errors in a more user-friendly way
Fixed:
- Issues with unclear or unhelpful error messages during Google sign-in
Removed:
- Old error handling system for Google sign-in errors
Summary:
- Improved error messaging for Google sign-in failures
- Enhanced referral code handling after successful login
- Simplified phone number verification process
- Added Google Connect button for easier sign-up and login
- Introduced a trouble signing in/up link for user support
Changelog:
Added:
- Google Connect button for sign-up and login
- Trouble signing in/up link for user support
Changed:
- Error messaging for Google sign-in failures
- Referral code handling after successful login
- Phone number verification process
Fixed:
- None
Removed:
- Explicit mode parameter in phone number verification routes
Summary:
- The login page no longer offers Google as a sign-in option.
- Users will have one less method to log in to their accounts.
- This change simplifies the login process by reducing the number of sign-in options.
- The removal of Google sign-in is intended to improve the overall user experience.
Changelog:
Added:
- No new features were added in this update.
Changed:
- The login page has been updated to remove an existing sign-in option.
Fixed:
- No bugs were fixed in this update.
Removed:
- The Google sign-in option has been removed from the login page.
Summary:
- The website's title has been updated to better reflect its purpose and features.
- The onboarding process has been improved to provide a more seamless experience for users.
- User data is now updated more efficiently after completing the onboarding process.
- The system's buttons have been made more accessible by improving their visual cues for disabled states.
Changelog:
Added:
- A new API call to complete the onboarding process for users.
Changed:
- The way user data is updated after onboarding completion.
- The styling of buttons to improve accessibility.
Fixed:
- No fixes are included in this update.
Removed:
- The "onboardingCompletedC" field is no longer sent separately, as it is now updated internally.
Summary:
- The application is now accessible in all environments, not just staging.
- Users can now use the application without restrictions based on the environment.
- The filtering functionality remains unchanged and is still available to users.
- The overall user experience has been improved by removing unnecessary restrictions.
Changelog:
Added:
- Accessibility to the application in all environments.
Changed:
- Environment-based restrictions have been removed.
Fixed:
- None
Removed:
- Restriction that limited the application to only the staging environment.
Summary:
- Simplified the offers page by removing unnecessary filters
- Enhanced the onboarding process by adding required fields for first and last name
- Updated the support email address for better assistance
- Improved the upgrade modal by adding a logout option for users coming from onboarding
- Refactored the code to improve performance and readability
Changelog:
Added:
- First and last name fields to the onboarding form
- Logout option to the upgrade modal for users coming from onboarding
Changed:
- Removed credit range filter from the offers page
- Updated support email address to support@lendinggenie.ai
- Improved the upgrade modal payment step
Fixed:
- None
Removed:
- Credit range filter from the offers page
- Unused code and variables to improve performance and readability
Summary:
- The display of credit ranges for offers has been removed to simplify the user interface.
- Password requirements have been updated to ensure they are between 8 and 16 characters long for better security.
- The system now enforces stronger password policies for all users.
- The overall user experience has been improved by reducing clutter and enhancing security measures.
Changelog:
Added:
- Maximum password length validation to enhance security.
Changed:
- Password requirements to ensure they are within a specific length range.
- The way offer details are displayed to users.
Fixed:
- Inconsistent password validation rules.
Removed:
- Display of credit ranges for offers.
Summary:
- The prequalification process has been improved to provide clearer information about the steps involved.
- Users can now edit their previous answers during the prequalification process.
- The system now displays a progress bar showing the current step and total number of steps.
- The prequalification chat interface has been updated for better user experience.
- The upgrade modal has been modified to display a payment link after pre-qualification.
Changelog:
Added:
- The ability for users to edit their previous answers during the prequalification process.
- A progress bar showing the current step and total number of steps in the prequalification process.
- A payment link in the upgrade modal after pre-qualification.
Changed:
- The prequalification chat interface for better user experience.
- The upgrade modal to display a payment link after pre-qualification.
Fixed:
- No fixes are mentioned in the provided diff.
Removed:
- No removals are mentioned in the provided diff.
Summary:
- The login page has been removed and its functionality is now handled by the root page.
- The redirect behavior after login has been improved for a better user experience.
- Referral codes are now properly saved and cleared during the signup process.
- The prequalification modal has been replaced with a new prequalification component.
- The signup process now includes the option to enter a referral code.
- Error handling for login and signup processes has been improved.
- The overall authentication flow has been streamlined for easier use.
Changelog:
Added:
- New page for handling redirects after login
- Option to enter a referral code during signup
- Improved error handling for authentication processes
Changed:
- Login page removed and its functionality handled by the root page
- Redirect behavior after login improved
- Prequalification modal replaced with a new prequalification component
Fixed:
- Referral codes are now properly saved and cleared during signup
- Improved error handling for login and signup processes
Removed:
- Old login page
- Old prequalification modal component
Summary:
- The link to the credit authorization agreement has been updated to reflect a new website.
- This change helps to ensure that users are directed to the correct location for credit authorization information.
- The update improves the overall user experience by providing a more accurate and reliable link.
- This modification is part of an effort to maintain compliance with relevant regulations and agreements.
Changelog:
Added:
- A new link to the credit authorization agreement on the Deliver Capital website.
Changed:
- The existing link to the credit authorization agreement has been updated to point to the new Deliver Capital website.
Fixed:
- The issue of outdated links to the credit authorization agreement has been resolved.
Removed:
- The old link to the Lendio credit authorization agreement has been removed.
Summary:
- The signup process has been simplified and improved for a better user experience.
- Users can now sign up using a whitelisted link, streamlining the process for eligible users.
- The system can now handle invalid or expired links, providing a clear error message to users.
- The overall design and layout of the signup page have been updated for consistency and clarity.
- Loading indicators have been standardized throughout the application for a more cohesive feel.
Changelog:
Added:
- Support for whitelisted signup links to simplify the signup process for eligible users.
- An invalid link screen to handle cases where users attempt to sign up with an invalid or expired link.
Changed:
- The signup page design and layout for improved consistency and clarity.
- Loading indicators throughout the application for a more standardized and cohesive feel.
Fixed:
- Various minor issues and inconsistencies in the signup and verification processes.
Removed:
- Redundant code and unnecessary complexity from the signup process.
Summary:
- Added Google sign-in functionality to the login page, allowing users to sign in with their Google account.
- Improved the login experience by providing an alternative sign-in method.
- Enhanced security by leveraging Google's authentication system.
- Removed the sign-up page, streamlining the user registration process.
Changelog:
Added:
- Google sign-in button on the login page
- Google sign-in functionality to handle authentication
Changed:
- Login page to include Google sign-in option
- Authentication flow to handle Google sign-in
Fixed:
- None
Removed:
- Sign-up page
Summary:
- The prequalification modal is now accessible from multiple locations on the landing page.
- A new prequalification modal host component has been added to manage the modal's state.
- The impersonation mode now defaults to "bypass" instead of "user".
- The dashboard tour will not start when impersonating a user.
- The landing hero section has been updated to use the new prequalification modal store.
- The prequalification modal can now be opened and closed programmatically.
Changelog:
Added:
- Prequalification modal host component
- Prequalification modal store
Changed:
- Impersonation mode default
- Landing hero section to use prequalification modal store
- Dashboard tour to not start when impersonating a user
Fixed:
- None
Removed:
- Direct links to open the prequalification modal have been replaced with a programmatic approach
Summary:
- The system now provides more accurate responses to user queries by considering strong knowledge base matches.
- Non-Q&A intents are handled more effectively, with canned responses provided only when no strong matches are found.
- The knowledge query engine is more robust, with better handling of configuration settings.
- The system ensures that required configuration settings, such as the Redis host and port, are properly set up before proceeding.
Changelog:
Added:
- Strong match detection for knowledge base queries
Changed:
- Handling of non-Q&A intents to provide more relevant responses
- Configuration setting checks to ensure required settings are present
Fixed:
- Issue with incomplete configuration settings causing errors
Removed:
- Dependency on a single Redis URL configuration setting, replaced by separate host and port settings
Summary:
- Users can now update their Social Security Number (SSN) and pull a new report.
- The system checks for valid user authentication before allowing SSN updates.
- The update process includes validation to ensure the SSN is in the correct format.
- The system handles cases where no credit data is found in the report.
Changelog:
Added:
- Functionality to update a user's SSN and pull a new report.
Changed:
- User report handling to include cases where no credit data is available.
Fixed:
- None
Removed:
- None
Summary:
- The system can now handle consent documents, allowing for better management of user agreements.
- Users can view and interact with consent documents in a more user-friendly way.
- The system can generate PDF versions of consent documents for easy sharing and printing.
- This change improves compliance with regulatory requirements and enhances the overall user experience.
Changelog:
Added:
- Consent document handling feature
Changed:
- System behavior to accommodate consent document management
Fixed:
- No fixes are included in this change
Removed:
- No features or functionality were removed in this change
Summary:
- Enhanced error handling for Google sign-in to provide more informative error messages
- Added intent-based authentication to differentiate between login and signup flows
- Improved database connection handling with enhanced error logging
- Updated configuration settings for MongoDB connection
Changelog:
Added:
- Support for intent-based Google authentication
- Error logging for database connections
Changed:
- Google authentication error handling to provide more specific error messages
- Database connection configuration settings
Fixed:
- Improved error handling for Google sign-in to prevent generic error messages
- Updated database connection error handling to provide more informative error messages
Removed:
- None
Summary:
- Improved Google authentication flow to handle both new and existing users.
- Added support for referral codes and custom fingerprints during Google login.
- Enhanced user creation and update logic for better data consistency.
- Introduced validation for email addresses and signup data to prevent errors.
- Updated login success handling to ensure seamless user experience.
Changelog:
Added:
- Support for referral codes during Google login.
- Custom fingerprint handling for Google login devices.
- Validation for email addresses and signup data.
- New functions for handling Google direct login, signup flow, and referral codes.
Changed:
- Google authentication flow to handle both new and existing users.
- User creation and update logic for better data consistency.
- Login success handling to ensure seamless user experience.
Fixed:
- Issues with email existence checks and custom signup flow.
- Problems with device persistence and CRM session ID storage.
Removed:
- Redundant code and unnecessary functions.
Summary:
- The system now saves lead profiles with additional information when a user logs in.
- This change improves the accuracy of lead tracking and management.
- It also enhances the overall user experience by providing more detailed user data.
- The update enables better integration with customer relationship management tools.
Changelog:
Added:
- Ability to save lead profiles with status information.
Changed:
- The method used to create CRM entries now includes note-saving functionality.
Fixed:
- No fixes are included in this update.
Removed:
- No features or functionalities were removed in this update.
Summary:
- Improved user authentication and registration processes
- Enhanced email validation and checking for existing user accounts
- Updated user onboarding process with a new completion endpoint
- Removed unnecessary dependencies and code for better performance
- Improved error handling for user authentication and registration
Changelog:
Added:
- New endpoint for completing user onboarding
- Email existence check to prevent duplicate user accounts
Changed:
- User registration process to use a custom lead signup service
- User authentication to use a more secure and efficient method
Fixed:
- Issues with user authentication and registration error handling
- Problems with email validation and checking for existing user accounts
Removed:
- Unused dependencies and code for better performance and security
- Referrals count field from partner data for simplified partner management
Summary:
- Added support for Google OAuth login to simplify user authentication.
- Introduced admin authorization to restrict access to certain features.
- Enhanced login functionality with improved error handling and user experience.
- Added enumeration options for better data management and filtering.
Changelog:
Added:
- Google OAuth login feature
- Admin authorization middleware
- Enumeration options for data management
Changed:
- Improved login functionality with enhanced error handling
- Updated user authentication and authorization logic
Fixed:
- Various bug fixes and improvements for better system stability
Removed:
- None
Releaseddc763-repo/dc_lead_application
#664 ProductionBilal Alam
Change Overview
Summary:
- The system now uses a standardized list for business states, making it easier to select and manage states.
- A similar standardized list is used for business industries, improving data consistency and reducing errors.
- The changes improve the overall user experience by providing a more intuitive and efficient way to select business states and industries.
- The updates also enhance data accuracy and reduce the risk of incorrect or incomplete information.
Changelog:
Added:
- Logging capability for autosave features to track and resolve potential issues.
Changed:
- Business state and industry fields now use enum types, providing a more structured and standardized approach to data selection.
Fixed:
- No specific fixes are included in this update, but the changes improve overall system reliability and data integrity.
Removed:
- No features or functionality have been removed in this update.
Releaseddc763-repo/dc_lead_application
#659 ProductionBilal Alam
Change Overview
Summary:
- Users can now update their Social Security Number (SSN) through a dedicated page.
- The update process includes input validation and formatting to ensure accurate data entry.
- A confirmation message is displayed after a successful update, and users can close the page to return to the main portal.
- The system checks if a user has already submitted their SSN to prevent duplicate entries.
- Error handling is implemented to notify users of any issues during the update process.
- The page is designed to be user-friendly, with a simple and intuitive interface.
Changelog:
Added:
- A new page for updating Social Security Numbers
- Input validation and formatting for SSN entries
- Confirmation messaging for successful updates
- Error handling for update issues
Changed:
- The system now checks for existing SSN submissions to prevent duplicates
- The update process includes a confirmation step to ensure user awareness
Fixed:
- Improved handling of invalid or incomplete SSN entries
Removed:
- None
Releaseddc763-repo/dc_lead_application
#661 ProductionPT Git User
Change Overview
Summary:
- The application now only unlocks certain tabs after a lead has been created, improving the workflow.
- This change prevents users from accessing tabs prematurely, reducing potential errors.
- The update ensures that tabs are only accessible when relevant information is available.
- The application's overall user experience has been improved by streamlining the tab unlocking process.
Changelog:
Added:
- A check to ensure that a lead exists before unlocking certain tabs.
Changed:
- The condition for unlocking tabs, now requiring a lead to be created.
Fixed:
- An issue where tabs could be accessed too early in the process.
Removed:
- The ability to unlock tabs solely based on selecting a loan type.
Releaseddc763-repo/dc_lead_application
#661 ProductionPT Git User
Change Overview
Summary:
- The loan application process now requires a lead to be created before accessing certain tabs.
- This change ensures that sensitive information is only accessible when a lead is properly set up.
- The application will now automatically unlock relevant tabs after a lead is created.
- This improvement enhances the overall workflow and organization of the loan application process.
- The change prevents premature access to financial and document-related tabs.
Changelog:
Added:
- Automatic unlocking of tabs after lead creation
Changed:
- The condition for accessing certain tabs now requires a valid lead
Fixed:
- Inconsistent access to tabs based on loan type selection
Removed:
- The ability to access certain tabs solely based on loan type selection
Releaseddc763-repo/dc_broker_portal
#423 ProductionBilal Alam
Change Overview
Summary:
- The system now ensures that State and Industry fields can only accept specific, predefined values.
- This change enhances data consistency and reduces errors caused by invalid or inconsistent input.
- Users will now select from a list of valid options for State and Industry, making it easier to enter accurate information.
- The overall quality of the data collected will improve, allowing for better analysis and decision-making.
Changelog:
Added:
- Drop-down menus for State and Industry fields to guide users in selecting valid options.
Changed:
- The input type for State and Industry fields to restrict input to predefined values.
Fixed:
- Potential issues with data inconsistencies and errors due to invalid input.
Removed:
- The ability for users to enter free-form text for State and Industry fields, which could lead to inaccuracies.