From what I understand, the behavior you are reporting is working as designed. That line is implying there may or may not be more steps in this screen flow. This is because the rest of them may be hidden visually, but are present on the DOM should they need to be used.
The line you are inquiring about is nothing more than a border for the list items (screen flow steps). It is set in CSS. pyscreenflow71.css is an available rule, so you can customize a lot of the current behavior as you see fit, but you are bound by the current style classes set already. (Adding new style classes won't help you since there is no HTML to even use it).
Here is what is happening take a look at this screen shot. I've change the line color so it is clear what is defining and dictating this.
You could try setting it to none in pyscreenflow71, but then you will be missing this connecting line for EVERY step.
You can try and conditionalize it to for only the last step, but this is technically not the last step in your configuration. (There might be more, just hidden.)
In fact, when you are truly at the last step you will see we already set it to none.
I think in order to meet your need, we would need to introduce a new style class for a "potential last step", then you could modify it as you see fit.
So in summary, I do not believe what you are requesting is possible with the current HTML generation (out of your control), mixed with the CSS which dictates this feature (within your control).
(Surprise me though, maybe you or someone else can come up with something clever )
You could raise an SR if you still strongly feel this is a defect, and you wish for it to be formally evaluated by an SME to confirm my understanding.
Hopefully that will not be necessary, and the support community moderators can tap some SMEs to verify this behavior if that is what you are seeking.
If all you are looking for is to submit an enhancement request to make this feature more customizable to meet your needs, then the moderators can spin off enhancements here without needing an SR as well.
(Please note enhancement requests are submitted for consideration in future releases with no guarantee on time frames)
Or, if you are still seeking input from other people on ways to potentially achieve the behavior you seek in the current implementation of the product, then staying here in the product support community space is the most appropriate action. SRs are only to be used to investigate potential defects or deliver media.
Thank you for posting your query on PSC. This looks like an inactive post and hence, we suggest you create a new post for your query. Click on the Write a Post button that’s available on the top right pane of this page. Once created, please reply back here with the URL of the new post.
We have also sent you a private message opening up a communication channel in case you have any further questions.