User Story description:
As a user, I want to see my CHEFS form directly embedded in the application I’m using and not be redirected to a new tab as I am currently.
Business Rationale:
Needing to manage multiple tabs can be confusing for a user, especially if there’s information in the form that the user needs to cross-reference while using the application.
Dependencies:
[List potential dependencies with other User Stories or Tasks]
# | Task or User Story | Type of Dependency |
1 |
|
|
2 |
|
|
3 |
|
|
4 |
|
|
Technical Details:
It’s currently possible to embed a public CHEFS form into any application using the <iframe> tag. Unfortunately if the form is IDIR or BCeID restricted then the form can only function embedded if SSO exists between the application and CHEFS.
Acceptance Criteria:
[List the Acceptance Criteria]
# | Description | Notes |
1 | Public form functions while embedded | The embedded form should function exactly the same as the non-embedded form. |
2 | Private form functions while embedded | IDIR and BCeID restricted forms. Will require SSO |
3 | Only the form is displayed | This means things like the CHEFS header and footer aren’t shown. Might need to somehow only return the formio container? |
4 |
|
|
5 |
|
|
Prototype/Mockups
A CHEFS form embedded in a web application (WorkBC Wage Subsidy)
Out of Scope:
Mobile app embedding
Contact(s):
Branko Bajic