QA Issue : Update BCSC user name when continuation in is filed
Describe the bug in current situation Business Bootstraps (temp reg) Discrepancies. Update the BCSC user name when a temp reg is filed.
Link bug to the User Story
Impact of this bug
Chance of Occurring (high/medium/low/very low) High
Pre Conditions: which Env, any pre-requesites or assumptions to execute steps?
Company Continuation Application
Steps to Reproduce Steps to reproduce the behavior:
- Go to '- Company Continuation Application - Reach till Staff approval pending
Actual/ observed behavior/ results
Submit person name with junk character ~Change button not available~ (tackled in 24010)
Expected behavior Submit person should be displayed ~Change button should be available and disabled~ (tackled in 24010)
Screenshots/ Visual Reference/ Source

@gunanagar can we get confirmation that this is different between dashboards. We have seen it happen in some other cases, but behavior is same between the existing and new dashboards, meaning data that comes to us for display is not selected on the UI.
@mstanton1 do we maybe want to do requirement/quality check and determine do we want to do something specific on this?
example of the same garbled looking data on both dashboards:
- new dashboard
- old dashboard
@hfekete good catch. Sounds like this may be a bug currently for some entities flows. For the comment on whether we want to do a requirement / quality check, I think we can just proceed to fix this. In any case where the logged on user has logged on with BCSC we should be using their name rather than the string of characters. Please let me know if you need any other info:)
@mstanton1 ok, I looked into what we get from the API, and it looks like we dont get anything that we can use in place of submitter other then this value:
yellow highlight comes from the one underscored red on right side, and we dont have any other value that could be used in place

Thanks for confirming @hfekete .
@OlgaPotiagalova @severinbeauvais our team was working to address the bug above (in the current entity dashboard and our entity dashboard) where the BCSC user name in the pending filing section is showing some sort of GUID rather than the actual name. It looks like an issue with your API as we can't see any other value to pull. Are you able to make an update in the API so we can pull the right data in our dashboard? If you create another ticket can you let us know the number of that ticket and we will add it as a blocker on this one.
This is a long-standing issue. We used to have a bug ticket for this but I haven't seen it in a long time, so I created a new bug ticket: ~24189~ 22305.
Given that this is been around since the beginning, we are likely to treat it as low priority unless you strongly object.
@severinbeauvais that works. No concerns with this being low priority / not handled quickly given that it's been around since the beginning. Thanks for creating your teams ticket and adding it as a blocker!
@hfekete removing this from our current sprint.
cc @fodiley
For the record, the submitter name is not decoded for bootstrap filings only (IA, registration, amalgamation and continuation in).
(Bootstrap filings are not a business yet.)