Skip to content

chore: Implement webchat pre-engagement form - fetch definitions [CHI-3618]#3865

Merged
gpaoloni merged 8 commits intomasterfrom
gian_CHI-3618
Feb 6, 2026
Merged

chore: Implement webchat pre-engagement form - fetch definitions [CHI-3618]#3865
gpaoloni merged 8 commits intomasterfrom
gian_CHI-3618

Conversation

@gpaoloni
Copy link
Collaborator

@gpaoloni gpaoloni commented Feb 4, 2026

Description

This PR

  • Refactors lambdas/packages/hrm-form-definitions/src/formDefinition/ (and plugin) to factor out code used to fetch definitions versions, in order to share between plugin and aselo webchat.
  • Introduces new /webchat/PreEngagementForm.json form definition file to centralize helpline customizations.
    • This file will be used in aselo webchat to define the pre engagement form.
    • Copied over all existing configurations from "old webchat" to the newer format.
  • Refactors aselo webchat app
    • initConfigThunk introduced to load the form definitions upon webchat initialization.
    • Stores form definition in Redux state.

Checklist

Other Related Issues

None

Verification steps

AFTER YOU MERGE

  1. Cut a release tag using the Github workflow. Wait for it to complete and notify in the #aselo-deploys Slack channel.
  2. Comment on the ticket with the release tag version AND any additional instructions required to configure an environment to test the changes.
  3. Only then move the ticket into the QA column in JIRA

You are responsible for ensuring the above steps are completed. If you move a ticket into QA without advising what version to test, the QA team will assume the latest tag has the changes. If it does not, the following confusion is on you! :-P

@gpaoloni gpaoloni requested a review from stephenhand February 5, 2026 20:30
@gpaoloni gpaoloni marked this pull request as ready for review February 5, 2026 20:30
Copy link
Collaborator

@stephenhand stephenhand left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great work here Gian. Couple of non blocking comments

} No newline at end of file
"environment": "development",
"aseloBackendUrl": "https://hrm-development.tl.techmatters.org",
"definitionVersion": "as-v1"
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should this be in common.json?

sessionDataHandler.setDeploymentKey(webchatConfig.deploymentKey);

store.dispatch(initConfig(webchatConfig));
await store.dispatch(initConfigThunk(webchatConfig) as any);
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we move the code above that loads the config into the thunk as well?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'll do this in a subsequent PR, as moving it now breaks some tests - it'll demand a few more minutes than just moving the code around.

@gpaoloni gpaoloni merged commit 6907b87 into master Feb 6, 2026
26 checks passed
@gpaoloni gpaoloni deleted the gian_CHI-3618 branch February 6, 2026 19:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants