Ab#129136 Public forms app

[Maximo-reliefapps]

Description

First iteration of a public forms app. In the current state you can fill a form without authentication by passing its id as an url paramenter. If the id is not correctly formatted or no form exists with the ide you will be redirected to a "No form" page.

The way we achieve this no auth forms is by mocking the authentication service we provide, removing any real authentication, always returning a "Public" user. This works for all checks in the front, but the backend needs to be updated to support that. For testing you can use this branch

To run the app: npx nx run public-forms:serve:local-uat

Useful links

• AB 129139

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Improvement (refactor or addition to existing functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce.

• Created a simple form, used the new app to access it and fill it, checked in the back office if the record was created
• Try to access a non-existent form, no form page was displayed

Screenshots

Checklist:

( * == Mandatory )

• * I have set myself as assignee of the pull request
• * My code follows the style guidelines of this project
• * Linting does not generate new warnings
• * I have performed a self-review of my own code
• * I have put the ticket for review, adding the oort-frontend team to the list of reviewers
• * I have commented my code, particularly in hard-to-understand areas
• * I have put JSDoc comment in all required places
• * My changes generate no new warnings
• * I have included screenshots describing my changes if relevant
• * I have selected labels in the Pull Request, according to the changes with code brings
• I have made corresponding changes to the documentation ( if required )
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules

More explanation

https://www.loom.com/share/05a716d61b9744faaf51fb304c21d1e5?sid=f87cf896-582a-4f76-93ae-8ceed801b145