Appian Community
Site
Search
Sign In/Register
Site
Search
User
DISCUSS
LEARN
SUCCESS
SUPPORT
Documentation
AppMarket
More
Cancel
I'm looking for ...
State
Not Answered
Replies
6 replies
Subscribers
8 subscribers
Views
2392 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
User Interface
a!pickerFieldRecords: opening the record on a NEW tab?
erickp
over 7 years ago
The component a!pickerFieldRecords gives you the option to click on the selected item taking you to the record. Is there any way to open the Summary dashboard on a NEW tab? I don't want the system to take the user away from where they were before.
OriginalPostID-268879
Discussion posts and replies are publicly visible
0
Mike Schmitt
Certified Lead Developer
over 7 years ago
The link functionality appears to be automatic and unconfigurable. The only alternative idea I can think of off the top of my head would be to do a custom picker where you declare the item links yourself and wrap them in a!safeLink. AFAIK this would work, though it would take a lot more effort.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Jacob Cohen - Project Leader - Macedon Technologies
over 7 years ago
This is standard browser functionality. The user has the option to open the record in a new tab with CTRL + Click (or right click, open in new tab), but you are not forcing them to open a new tab.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
erickp
over 7 years ago
Is there any way to make it not clickable?
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Jacob Cohen - Project Leader - Macedon Technologies
over 7 years ago
What do you mean by not clickable?
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
erickp
over 7 years ago
I don't want the user clicking the link and leaving the task they were on. So I want to make the selectable item on the picker non-clickable.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Mike Schmitt
Certified Lead Developer
over 7 years ago
again my best guess would be to use a custom picker field. it seems to me like some of these things should be controllable within parameters of a!pickerFieldRecords, but it looks like that's not the case.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel