Need unique IDs for Next/Back buttons to allow success tracking of Create patch template wizard

[andreasn]

I'm a UX researcher working on RHEL/HMS on consoledot.
I want to learn if there are any step at in a wizard where users get stuck and abandons the flow. Once that step is identified as a pitfall, I would set up usability test sessions with a smaller group of people and figure out what goes wrong in this particular step. I've done it for the Image Builder and Provision wizards so far, but now I want to do it with the patch template wizard as well.
I will use Pendo for tracking, but I need some unique IDs for the buttons for Pendo to hook up to at each step in the wizard.
Something along the lines of:

wizard-newtemplate-next-button
wizard-newtemplate-back-button
wizard-systems-next-button
wizard-systems-back-button
wizard-review-next-button
wizard-review-back-button

[andreasn]

@croissanne has some code for this that might be reusable here

[croissanne]

We used custom buttons for this https://github.com/RedHatInsights/image-builder-frontend/blob/main/src/Components/CreateImageWizard/formComponents/CustomButtons.js.

[ezr-ondrej]

We did the same for provisioning in, for more inspiration RHEnVision/provisioning-frontend#193 :)

[leSamo]

Hello, thank you for providing examples! We are in the process of reworking the Template wizard and we will include this change as well.

[leSamo]

This issue is blocked by data-driven-forms/react-forms#1379