# Use Case 2.6 Change remote PIN ## Overview | Aspect | Description | |------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------------------------------| | **Summary** | The user changes their PIN by first entering the current one, then choosing and confirming a new PIN that meets policy requirements. | | **Goal** | Changing the remote PIN. | | **Preconditions** | | | **Postconditions** | | | **Triggered by** | | | **Additional Documentation** | | | **Possible errors** | *None* | | **Logical Test Cases** | | --- ## Flow | # | Description | Next | |---------|-------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------| | **1** | **PRIMARY SCENARIO** | | | **1.1** | **System executes partial flow [PF2.4 Confirm a protected action](../partial-flows/PF2.4_ConfirmProtectedAction.md)** | | | 1.1a | Result: Confirm | 1.2 | | 1.1b | Result: Back | Back | | **1.2** | **System executes partial flow [PF2.9 Setup PIN](../partial-flows/PF2.9_SetupPin.md)** | | | 1.2a | Result: PIN setup succeeds | 1.3 | | 1.2b | Result: Back | Back | | **1.3** | **System displays screen 'PIN change success'** | | | 1.3a | User selects Dashboard | Go to: [UC7.1 Show all available cards](UC7.1_ShowAllAvailableCards.md) | | 1.3b | User selects Settings | End |