Applications portal

For one of the tickets I worked, I resolved an issue where applicants could previously add more than two references despite the system limit, leading to confusion when they were unable to proceed after creating a third reference. To address this, I implemented an observer mutation to monitor the reference section and dynamically disable the "Add Reference" button when two references were present. This same logic re-enabled the button when only one reference was present, ensuring the functionality was seamless without requiring a page refresh. I then isolated the specific div to be monitored in order to optimise performance and avoid calling the function excessively.

Another significant ticket involved me implementing conditional logic to display specific questions based on the selected Business School course. This was achieved by using a show/hide mechanism and disabling the required state for certain fields, allowing users to progress through the form smoothly. I also modified the character limits and descriptions for specific fields. I deemed it best to adjust the character limit using JavaScript, as opposed to modifying the Dataverse column, as that approach ensured that the changes were not reset with each deployment or solution import. This method reduced the risk of forgetting the adjustments and was more efficient compared to manually updating the column, as pull requests for code changes are faster and more reliable.

I also focused on improving the user experience of the contact details form step. This involved relabelling the "Home phone" field to "Other phone number" and moving it to appear below the “Mobile phone” field to better align with user journey priorities and make the labelling consistent with other forms. The relabelling was implemented using JavaScript rather than modifying the column directly, to ensure consistency across documentation and prevent potential issues if the same form was used by other applications. Additionally, because it made more sense from a user flow perspective, I moved the "LinkedIn ID" field - which was previously on Page 5 - to the contact details form. To minimise disruption, I hid the field from its original page rather than deleting it, preserving functionality for other potential uses of the form.

Technologies used:

• Power Platform CLI - to streamline development and deployment tasks, connect environments and automate tasks.

• JS DataTables - to create interactive and feature-rich tables for web applications.

• Power Portal - as it allowed for custom validation using javascript/jquery in order to meet the specific requirements.

• Jira - for my team to manage the backlog, remain updated on each other’s tasks.

• Azure DevOps - to run deploy pipelines.

• VS Code - to merge branches.