Expand my Community achievements bar.

Join us LIVE in San Francisco on November 14th for Experience Makers The Skill Exchange. Don't miss out on this free learning event!

Communication Regarding URL Change

Avatar

Level 3
Does anyone has a sample communication that has been sent to users about Workfront URL change? I am looking for some sample communication to be sent out.
2 Replies

Avatar

Level 10
This is what I sent out…we used the changeover by WorkFront to create an alias, so that we never have to announce a change in URLs ever again. We alias crowley.my.workfront.com to workfront.crowley.com. I also sent this out before WorkFront announced an extension to the cut-over / cut-off date. Hope this helps… Hi: You are receiving this email because you are listed as an active user in WorkFront, the project management software used by IT and other groups at Crowley. Two years ago, WorkFront changed the name of their software from “AtTask” to “WorkFront”. At the end of March of this year, WorkFront is going to change the URL/Address used to get to their software - they are removing the name AtTask from that URL. Before the end of March, please start using : http://workfront.crowley.com/ to get to WorkFront. Other URLs will stop working at the end of March, so please delete them. We’ve activated auto-authenticate in Chrome, so that it shouldn’t give you an Azure login screen anymore - it will automatically log you in. If you have any questions or concerns, please do let me know straight away. Thanks very much! Eric

Avatar

Level 10
Hi, There was Announcements sent out few times already about it in Workfront. ------ 7/2/17 For your information, Workfront is updating the URL used in all email notifications beginning March 29, 2017, moving all customers to .my.workfront.com domain. If you are an SSO customer, you will be receiving an additional message with instructions to ensure your metadata is updated correctly . New and and existing links will continue to function. However, we encourage you to update any existing bookmarked or saved links to the new URL to prevent confusion or future issues, and remind your users to do the same. Thank you for being a customer 8/7/17 We will be updating the Workfront email links and URLs to phase out any legacy AtTask domains. Two required actions on your end will need to be completed before March 29, 2017. 1. Update any existing bookmarks or saved URLs to your new url: .my.workfront.com 2. Update the metadata file from Workfront in your IdP For many configurations, the update to your metadata file occurs automatically and might already be complete. To verify whether your metadata file needs to be updated: 1. Launch a private browsing window (“inPrivate” in IE, or “incognito” in Chrome). 2. Ensure that you can successfully log in using SSO. If you cannot successfully log in, you must update the metadata in your IdP, as described in “"https://support.workfront.com/hc/en-us/articles/216651258" Updating SAML 2.0 Metadata in Your Identity Provider ” on the Workfront Help site. If you have additional questions or need assistance, please contact Workfront Technical Support. While existing links will continue to work, it’s important to update your Workfront metadata before March 29, 2017 to ensure a smooth transition. We also recommend that you update any existing bookmarked or saved links to point to the updated URL. Thank you in advance for your cooperation! 7/3/17 This is a reminder that Workfront is updating the URL used in all email notifications on March 29, 2017. All email links will use .my.workfront.com. If you are an SSO customer, you will need to take the following actions before March 29, 2017: • Update any existing bookmarks or saved URLs to your new url: .my.workfront.com New and and existing links will continue to function throughout 2017. However, we encourage you and your users to update any existing bookmarked or saved links to the new URL to prevent confusion or future issues. • Update the metadata file from Workfront in your IdP For many configurations, the update to your metadata file occurs automatically and might already be complete. To verify whether your metadata file needs to be updated: 1. Launch a private browsing window (“inPrivate” in IE, or “incognito” in Chrome). 2. Ensure that you can successfully log in using SSO. If you cannot successfully log in, you must update the metadata in your IdP, as described in “"https://support.workfront.com/hc/en-us/articles/216651258" Updating SAML 2.0 Metadata in Your Identity Provider ” in the Workfront Help center. If you have additional questions or need assistance, please contact Workfront Technical Support. 14/3/17 Recently, we sent notifications that we will be updating the Workfront email links. However, based on feedback from our customers, we have decided to extend the previously communicated deadline of March 29, to May 15, 2017 . If you are using SSO to access Workfront , we request that you complete the following two actions before May 15, 2017 . After that date, all email links will be updated to .my.workfront.com. 1. Update existing or saved bookmarks to your new url: .my.workfront.com (Although links will be functional for the duration of 2017, we encourage you to update any existing bookmarks to the new URL to prevent confusion or future issues.) 2. Update the metadata file from Workfront in your IdP For many configurations, the update to your metadata file occurs automatically and might already be complete. However, to verify if your metadata file needs to be updated, please follow the instructions below: 1. Launch a private browsing window (“inPrivate” in IE, or “incognito” in Chrome). 2. Ensure that you can successfully login using SSO. If you cannot successfully log in, you must update the metadata in your IdP, as described in “"https://support.workfront.com/hc/en-us/articles/216651258" Updating SAML 2.0 Metadata in Your Identity Provider ”, available in the Workfront Help center. If you have additional questions or need assistance, please contact Workfront Technical Support. That's what we've received so far. And to add to this - we've made the change already.