a!safeLink not working as expected

Question

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

Mike Schmitt · Answer

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.

Mike Schmitt · Answer

I just tried and confirm that the "SAME_TAB" functionality works as expected both on a site as well as in a Tempo report - using both a!linkField() as well as my preferred method, which is a Rich Text Display field with a link added. 
 If you try different browser(s) does the behavior stay the same for you?

Mike Schmitt · Answer

Sandya said: Any solution to open safelink in the same tab from embedded interface 
 can you describe your "embedded interface" in any more detail? If I had to guess, I'd think this feature might possibly be internally disabled in such a case, to prevent the parent interface from being clicked away from inadvertently.

Mike Schmitt · Answer

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

Mike Schmitt · Answer

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?

a!safeLink not working as expected

Top Replies