• Alex Schutte
  • NEWBIE
  • -1 Points
  • Member since 2014

  • Chatter
    Feed
  • 0
    Best Answers
  • 0
    Likes Received
  • 0
    Likes Given
  • 2
    Questions
  • 2
    Replies
We have our Knowledge Base articles accessible within our Customer Community (utilizes legacy Customer Portal - Usage Login license types), exposing the Knowledge Base as a tab and giving Community members Permission to read the individual article types.

However, if you send out a link to an individual Knowledge article and you are not already logged in, it takes you to a generic force.com Page Not Found page with a clock and orange exclamation point. 

Example link: https://qvidian.force.com/community/articles/Release_Notes/Qvidian-Proposal-Automation-QPA-February-2015-Maintenance-Release

When we first launched though, clicking on an individual article link used to take them to the SFDC Customer Community login page first if they were not already logged in.

Do you know if there is a way such that if anyone attempts to access Community resources directly, such as a bookmark or perhaps a shared link, that we can direct them to a login page first and then continue to the desired page, or prompt them for the credentials, or at least have a message saying you need to log into the Community before viewing this content - rather than having this obscure message come up?
We just upgraded/migrated our Customer Portal to the new Customer Communities platform (but kept the Customer Portal licenses and did not migrate to new Communities licenses) and now when we create a new Community User the Welcome email is not sending at all - regardless of whether or not you check "Generate new password and notify user immediately" or not - have tried both ways on initial creation and either way it does not send the welcome email.

In the Manage Communities Setup option we do have "Send welcome email" checked and created a new email template to be used with it. The template is active and Available for Use. All of the Portal Profiles and permissions have been given access to the new Community. 

When I first Published the new Community I did not have the Manage Communities Setup option "Send welcome email" checked because I didn't want to blow up all the existing Users' inbox. We were already sending an email to customers announcing the upgraded Community. But then once it was Published and the new email template was created the setting was checked back to "Send welcome email".

What does work is after you create the new user and leave "Send welcome email" unchecked, Save it. Then go back and click 'Edit' and now check "Send welcome email". That will then send the email template set for the 'Forgot Password' and 'Change Password' options in the Manage Communities Setup options.

And apparently, SFDC changed how they treat these emails from Portal to Communities, but does not mention this in any documentation. In Portals an auto-generated password used to be contained directly in the email template, inserted at the bottom.

Now, in the new Communities, that auto-generated password is no longer included, but they changed how they do this for security reasons (winter 14 release update apparently) and instead of sending a username and password in the email they now send a special link that allows people to click and change their password.

The trick is that your forgot your password email template needs to include this special merge field (undocumented anywhere by SFDC from what I found):

{!Community_Url}

If you include that it will be replaced with a special url that allows the user to change their password and logs them in. Thread where I first found this out: http://salesforce.stackexchange.com/questions/17887/communities-forgot-password-emails

This is being successfully included in the 'Forgot Password' and 'Change Password' email templates that were created. So when I go back to the newly created User and click 'Edit' and now check "Send welcome email", it does send the email template set for the 'Forgot Password' and 'Change Password' options to the new user and they are able to get in after setting their password.

Any ideas or help you can provide??

Thanks,
Alex
We have our Knowledge Base articles accessible within our Customer Community (utilizes legacy Customer Portal - Usage Login license types), exposing the Knowledge Base as a tab and giving Community members Permission to read the individual article types.

However, if you send out a link to an individual Knowledge article and you are not already logged in, it takes you to a generic force.com Page Not Found page with a clock and orange exclamation point. 

Example link: https://qvidian.force.com/community/articles/Release_Notes/Qvidian-Proposal-Automation-QPA-February-2015-Maintenance-Release

When we first launched though, clicking on an individual article link used to take them to the SFDC Customer Community login page first if they were not already logged in.

Do you know if there is a way such that if anyone attempts to access Community resources directly, such as a bookmark or perhaps a shared link, that we can direct them to a login page first and then continue to the desired page, or prompt them for the credentials, or at least have a message saying you need to log into the Community before viewing this content - rather than having this obscure message come up?
We just upgraded/migrated our Customer Portal to the new Customer Communities platform (but kept the Customer Portal licenses and did not migrate to new Communities licenses) and now when we create a new Community User the Welcome email is not sending at all - regardless of whether or not you check "Generate new password and notify user immediately" or not - have tried both ways on initial creation and either way it does not send the welcome email.

In the Manage Communities Setup option we do have "Send welcome email" checked and created a new email template to be used with it. The template is active and Available for Use. All of the Portal Profiles and permissions have been given access to the new Community. 

When I first Published the new Community I did not have the Manage Communities Setup option "Send welcome email" checked because I didn't want to blow up all the existing Users' inbox. We were already sending an email to customers announcing the upgraded Community. But then once it was Published and the new email template was created the setting was checked back to "Send welcome email".

What does work is after you create the new user and leave "Send welcome email" unchecked, Save it. Then go back and click 'Edit' and now check "Send welcome email". That will then send the email template set for the 'Forgot Password' and 'Change Password' options in the Manage Communities Setup options.

And apparently, SFDC changed how they treat these emails from Portal to Communities, but does not mention this in any documentation. In Portals an auto-generated password used to be contained directly in the email template, inserted at the bottom.

Now, in the new Communities, that auto-generated password is no longer included, but they changed how they do this for security reasons (winter 14 release update apparently) and instead of sending a username and password in the email they now send a special link that allows people to click and change their password.

The trick is that your forgot your password email template needs to include this special merge field (undocumented anywhere by SFDC from what I found):

{!Community_Url}

If you include that it will be replaced with a special url that allows the user to change their password and logs them in. Thread where I first found this out: http://salesforce.stackexchange.com/questions/17887/communities-forgot-password-emails

This is being successfully included in the 'Forgot Password' and 'Change Password' email templates that were created. So when I go back to the newly created User and click 'Edit' and now check "Send welcome email", it does send the email template set for the 'Forgot Password' and 'Change Password' options to the new user and they are able to get in after setting their password.

Any ideas or help you can provide??

Thanks,
Alex