a!safeLink not working as expected

As per Appian 21.1 (https://docs.appian.com/suite/help/21.1/Web_Link_Component.html) now we should be able to open the link on same tab.

I tried testing this but the link opens in new tab regardless of the value that is set to the parameter openLinkIn

Test Code in 21.1.

a!sectionLayout(
   contents: {
       a!linkField(
              links: {
                   a!safeLink(
                   label: "Safe Link",
                   uri:"">https://appian.com/",
                   openLinkIn:"SAME_TAB"
                )
            }
        )
     }
)

  Discussion posts and replies are publicly visible

Parents
  • 0
    Certified Senior Developer

    Absolutely! Here's a shorter solution and troubleshooting steps:

    Problem: The a!safeLink component isn't opening the link in the same tab, even with openLinkIn: "SAME_TAB" setting.

    Potential Causes:

    • Browser settings
    • Appian Caching
    • Custom code conflicts

    Troubleshooting:

    1. Try different browsers (Chrome, Firefox, Edge)
    2. Clear your browser cache.
    3. Look for any custom CSS or JavaScript that might be changing link behavior.

    Workaround:

    If none of the above works, temporarily use this workaround to force opening in a new tab:

    Code:

    a!safeLink(
    label: "Safe Link",
    uri: "">https://appian.com/",
    openLinkIn: "SAME_TAB"
    )

  • 0
    Certified Senior Developer
    in reply to Srinivas

     

    Thanks for quick response. a!link function is not available.

  • Their response is nothing but a ChatGPT regurgitation of what's already been discussed much earlier in this thread, as Stefan pointed out, and is incorrect since the posted answer contains the nonexistent function "a!link()" where they presumably meant "a!safeLink()" - and the problem is that the question of Embedded interfaces 100% eclipses all normal troubleshooting of this issue, which is all that answer does.

    I'm confused why you'd reply to this one but not reply to the followup reply I left you earlier...?

Reply
  • Their response is nothing but a ChatGPT regurgitation of what's already been discussed much earlier in this thread, as Stefan pointed out, and is incorrect since the posted answer contains the nonexistent function "a!link()" where they presumably meant "a!safeLink()" - and the problem is that the question of Embedded interfaces 100% eclipses all normal troubleshooting of this issue, which is all that answer does.

    I'm confused why you'd reply to this one but not reply to the followup reply I left you earlier...?

Children