on ‎2025 Apr 29 1:49 PM
Dear experts,
I'm trying to implement an intent-based navigation from GUI to a Fiori app. I'm using well-known cl_lsapi_manager in my ABAP code for that purpose, but there's a problem: my FLP is configured to use SSL connection (SICF -> sap/bc/ui2/flp) and when lsapi_manager attempts to follow generated URL with parameters (the ones after #), it somehow loses them after runtime automatically replaces standard http connection with https, and as result I see FLP landing page with #Shell-home. And I have no idea how do deal with this issue...
Here's an example:
1) in my ABAP code (it's a hotspot handler in sALV) I generate an FLP URL:
DATA(lv_ibn_location) = cl_lsapi_manager=>create_flp_url(
object = lv_semantic_object "<- semantic object of the desired app
action = 'display' "<- semantic action
parameters = lt_parameters ). "<- some parameters2) this URL looks like this:
take a note that it has http connection with port 8002.
3) And then, for simplicity's sake, I just pass this URL to cl_gui_frontend_services=>execute , just trying to open it. A new browser window is triggered, this URL is passed, but then it gets replaced with https connection with a new port, and suddenly all hash values in the URL are gone (#<my_sem_obj>-display?InspectionLot=010000000405) and I'm landing on #Shell-home
Why is this happening? How do I prevent my parameters (not even parameters, but the entire hash value) from being ignored after this http->https transition? I need a flexible solution because different clients may have different FLP settings (some with standard http security protocol, the others with https with their own ports) and my solution should work without any workarounds, like just calling:
cl_lsapi_manager=>get_instance( )->navigate( location = lv_ibn_location )., which of course ends up with the same issue.
Any advices will be much appreciated.
Regards,
Mykyta
Request clarification before answering.
| User | Count |
|---|---|
| 7 | |
| 5 | |
| 4 | |
| 4 | |
| 3 | |
| 3 | |
| 3 | |
| 3 | |
| 2 | |
| 2 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.