a!safeLink not working as expected

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"
)

VAS 

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...?

I was in a rush to try solution. Sorry for that. We are embedding appian site into web page (developed using angular).

Using a!safelink to download document. We are getting authorization failed after clicking download link as it is opening in new tab. This is working as expected from long time. Only thing I see there is a version upgrade[23.4] during last weekend.  Hope I gave enough context around the problem we are facing.

Sandya said:

Using a!safelink to download document

Are you talking about an externally-hosted document?

yes

For that I don't see why a safeLink would fail (regardless of the target location) unless actively prevented by the file's source host.  Have you tried it with other externally-hosted files, with different methods of authentication (or no authentication), etc?

Hi ,

Understood, I'll strive for clarity in the responses.

the suggestions provided were based on generic troubleshooting steps applicable in many software contexts, including Appian. However, if there’s a specific Appian functionality mentioned incorrectly, such as a!link which doesn't exist in Appian's function library, the correct reference should indeed be a!safeLink. The aim was to assist with the issue pragmatically, but it's crucial to adapt the recommendations specifically to Appian’s capabilities and syntax.

Hi ,

Understood, I'll strive for clarity in the responses.

the suggestions provided were based on generic troubleshooting steps applicable in many software contexts, including Appian. However, if there’s a specific Appian functionality mentioned incorrectly, such as a!link which doesn't exist in Appian's function library, the correct reference should indeed be a!safeLink. The aim was to assist with the issue pragmatically, but it's crucial to adapt the recommendations specifically to Appian’s capabilities and syntax.

As many of the posters here are novice-level who will not know themselves how to filter "generic" answers through an Appian-specific filter, and may be badly misled in the meantime by inaccurate or downright-false answers, I would beg you to please refine such answers ahead of time both for accuracy to Appian-specific functionality, and also pertinence to the actual question being asked.  Many of the answers I see you posting have much work to do in both of these departments.

I'm not the "community police" by any means (i'd leave that to Stefan Helzle lol) but having misinfo being posted with confidence as answers to questions is only making the job harder for those of us trying to help users reach accurate and appian-appropriate solutions to their questions.