We’ve had an issue that our redirects that work in our SF environment break when we take them to the community because we have more than one community and the community name is appended to the URL. So now we’ve added that community name to our redirects but the won’t work when previewing in straight SF. I am wondering if this could be managed by a custom setting that lets us specify what should be included in the root of the URL?
Custom setting to determine root URL""
+3This topic has been closed for replies.
+13Are you using relative links in your Redirects, e.g. “/apex/skuid__UI?page=NewApplication&id=a0600000000123”, as opposed to absolute links, e.g. “https://skuid--acme--full.na12.visual.force.com/apex/skuid__UI?page=NewApplication&id=a060000000000123”?
+3yes we are. The tricky bit is that in the Community Portal we need to subsitute the “Apex” bit with “Community Name”. I don’t think it would be a problem if we only had one community…
+9Thad, Maybe you could use a custom setting (which is a sort of global variable stored in your org). Your pages could build the url’s and append in the value of the custom setting, in one case the setting would be “apex” and in the other “community name”. You can find custom settings under “setup/develop/custom settings”. You can add a model to a SKUID page that gets the custom setting data, just like it was from a custom object, and then refer to that model to get the value you need.
+3Kevin, Good to know. We are about to start building out our second community and so should look at this approach.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.