Print button automatically disables after click

[Sh3zza]

Describe the bug
We have included a Print Declaration Summary button in the Summary review page for record.declare scope.
The button becomes automatically disabled after it is clicked.
We would like it to remain in Enabled state - as there may have been an issue with the printer or used incorrect paper, etc.

According to the System Integrator (SI - Deoitte), this behaviour is not configurable: the button cannot remain enabled after being clicked. However, from a user flow and usability perspective, the button should ideally remain enabled to allow multiple prints or reprints.

Expected Behaviour

Note: There is also an Upload button (Step 2) to upload the declaration page after it has been reviewed and signed. This is disabled by default and becomes enabled after the Print button (Step 1) is clicked. This functionality currently works.

• Step 1 button should remain enabled even after being clicked, allowing multiple prints if needed.
• Step 2 button should still only become enabled after Step 1 has been clicked at least once.

See default screenshot:

After clicking screenshot:

Code review

The button status is disabled when alreadyPrinted

Tech tasks

• Lets entirely remove this alreadyPrinted prop entirely in 1.9.1 so it cant be disabled

[euanmillar]

@Zangetsu101 alreadyPrinted was a country requirement (Madagascar) that should have been a configurable option:

opencrvs-core/packages/client/src/v2-events/features/events/registered-fields/AlphaPrintButton.tsx

Line 144 in f89e807

disabled={disabled || !certificateConfig || alreadyPrinted}

[Zangetsu101]

We should be able to safely remove this alreadyPrinted part as what's being achieved by it should already be possible via
ConditionalType.ENABLE.

[euanmillar]

@rikukissa Lets entirely remove this alreadyPrinted prop entirely in 1.9.1 so it cant be disabled

[Sh3zza]

@euanmillar @rikukissa - Just to clarify (based on above comments) -
AGREE that button should not be disabled based on "alreadyPrinted" prop (as we don't really know if printing was successful)
But still think we should be able to specify a button to be able to enabled or disabled based on regular conditional logic (print button could be disabled if mandatory fields are not completed).
ALSO -
We have a second button (Upload the signed declaration) - that is DISABLED by default, but enabled when PRINT button is selected. Not sure if the "ConditionalType.ENABLE" would need the "alreadyPrinted" prop. This part currently works in testing.

[Zangetsu101]

Even if we remove the alreadyPrinted prop, the buttion can still be disabled using the ConditionalType.ENABLE if needed