Skip to content

Conversation

@hetangmodi-crest
Copy link
Contributor

Issue number:

PR Type

What kind of change does this PR introduce?

  • Feature
  • Bug Fix
  • Refactoring (no functional or API changes)
  • Documentation Update
  • Maintenance (dependency updates, CI, etc.)

Summary

Changes

Fixed password field placeholder behaviour in UCC account configuration forms. When editing existing accounts, encrypted fields (like passwords) now display masked values ("******") to indicate that a password is already set, instead of always showing empty fields.

User experience

Before:

  • When editing an existing account, password fields were always blank
  • Users couldn't distinguish between accounts with no password set vs. accounts with existing passwords
  • Confusion about whether passwords needed to be re-entered during account editing

After:

  • When editing an existing account with a set password, the password field shows "******" as a placeholder
  • When creating a new account or editing an account without a password, the field remains empty
  • Clear visual indication to users about password status without compromising security

Checklist

If an item doesn't apply to your changes, leave it unchecked.

Review

  • self-review - I have performed a self-review of this change according to the development guidelines
  • Changes are documented. The documentation is understandable, examples work (more info)
  • PR title and description follows the contributing principles
  • meeting - I have scheduled a meeting or recorded a demo to explain these changes (if there is a video, put a link below and in the ticket)

Tests

See the testing doc.

  • Unit - tests have been added/modified to cover the changes
  • Smoke - tests have been added/modified to cover the changes
  • UI - tests have been added/modified to cover the changes
  • coverage - I have checked the code coverage of my changes (see more)

Demo/meeting:

Reviewers are encouraged to request meetings or demos if any part of the change is unclear

@hetangmodi-crest
Copy link
Contributor Author

Raised a PR in SmartX for the above CI failures.

@hetangmodi-crest hetangmodi-crest marked this pull request as ready for review November 20, 2025 09:34
@hetangmodi-crest hetangmodi-crest requested review from a team as code owners November 20, 2025 09:34
@hetangmodi-crest hetangmodi-crest merged commit 8dd7f30 into develop Nov 27, 2025
168 of 170 checks passed
@hetangmodi-crest hetangmodi-crest deleted the feat/preserve-masked-value-for-encrypted-fields branch November 27, 2025 12:14
@github-actions github-actions bot locked and limited conversation to collaborators Nov 27, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants