a!startProcessLink() open in a different/new tab?

Hello , 

Is there a way to implement this in Appian sites ? Currently new tab in the browser opens in tempo as we have configured Temp on the uri . I tried to configure in sites ,but no luck. Is there a way to configure to open in new tab when using application in Appian sites . Something like https://[Appian Site URL].appiancloud.com/suite/sites/[application-name].

Thank you.

You can use Safelink and in that you can provide the url to which you want to navigate.

I tried using safelink , but looks like we can open new tab in Tempo ,if configured in Sites ( I mean application hosted using Sites   --> suite/sites/ ) ,I am getting access denied error .

Can you use a record action instead of a start process link? The record action contains a property for "openActionsIn" that allows you to designate whether to open in a new tab, same tab, or dialog. If you do this, it will work within your site rather than opening in Tempo.

Also just a general suggestion - I'd recommend creating a new post in the future rather than adding to an existing thread. In 4 years a lot of things change so there are often new ways to achieve functionality that could be better served with a new post

Hi Peter,

Thank you for the heads up on the record action.

Peter Lewis said:

The record action contains a property for "openActionsIn"

As an aside, i think it was a bit of an oversight / feature incompleteness issue that [some of] the other link components were updated with launch target overrides (which is great) but a!startProcessLink() was passed over.  Especially considering that with enough (unreasonably work-aroundish) effort, someone could set up arbitrary links anyway using the Record Action link as you mentioned - of course this would require staging a dummy record type, a dummy action, etc - and for what gain?

Peter Lewis said:

The record action contains a property for "openActionsIn"

As an aside, i think it was a bit of an oversight / feature incompleteness issue that [some of] the other link components were updated with launch target overrides (which is great) but a!startProcessLink() was passed over.  Especially considering that with enough (unreasonably work-aroundish) effort, someone could set up arbitrary links anyway using the Record Action link as you mentioned - of course this would require staging a dummy record type, a dummy action, etc - and for what gain?

It's a fair point - how often would you say that you have an action that isn't associated with a record in some way though?

Peter Lewis said:

how often would you say that you have an action that isn't associated with a record in some way

I don't know whether that's a fair metric by which to judge whether a!startProcessLink()'s lack of a "new_tab" launch target is actually a "feature incompleteness" issue.

But I'll go ahead and say I use it fairly often and (without having an easy way to tally retrospectively of course) i'd roughly estimate that maybe 75% of my use cases are relevant to data that doesn't concern any specific entry in one of the (relatively few) DB tables we have set up as Record Types.

Hi, 

Is there a way to close the New Tab opened in web browser after the process completion ?

Thanks,

Priyanka

priyankav4295 said:

Is there a way to close the New Tab opened in web browser after the process completion

Nope, sorry.