recordLink() - Can I link to a record type instead of a specific record?

Ok, I see that. 

But I was making the Record List a page on a site component so that it looks nicer. 

And I don't appear to have that option. 

Is that just the case, and I should keep it in Tempo?

Thanks,

Hey Robert,

Is there a way to conditionally display a different "Title" on the site based on if the user is on the record list or an individual record?

I see that you can make the title an expression, so something like this pseudo.

if(onRecordList, "Tracker", "Back")

Therefore, if they arent on the record list, then the title will change to back. I'm just not sure what conditional can check for that.

Any suggestions appreciated.

Thanks

Hi John

You can use static text or an expression for you Site Page Title.If you have deployed Appian Common Objects, I suppose you could try to use rule!APN_getSiteURL in some manner to identify when you're on a record vs the record list.
Is this really a high priority?

Yes, a back button would be nice.  But, there's a perfectly workable solution out of the box, (to click on the tab again). 
We just have to teach the users that.  They'll catch on quickly.
I'll bet there are a number of outstanding features your users would truly benefit from, and that aren't otherwise available yet. 
You might actually be doing your users a favor if you de-prioritize this altogether and shift your focus elsewhere.

I hope that helps.

Hi John

You can use static text or an expression for you Site Page Title.If you have deployed Appian Common Objects, I suppose you could try to use rule!APN_getSiteURL in some manner to identify when you're on a record vs the record list.
Is this really a high priority?

Yes, a back button would be nice.  But, there's a perfectly workable solution out of the box, (to click on the tab again). 
We just have to teach the users that.  They'll catch on quickly.
I'll bet there are a number of outstanding features your users would truly benefit from, and that aren't otherwise available yet. 
You might actually be doing your users a favor if you de-prioritize this altogether and shift your focus elsewhere.

I hope that helps.