Migration from schedulesource.net/Enterprise

Modified on Tue, Jan 7 at 4:07 PM

Updated:  January 7th, 2025


Background

The TeamWork application was originally hosted under the schedulesource.net domain, at the full URL of https://www.schedulesource.net/Enterprise/TeamWork5/.  For several years, we have also hosted the app on the domain tmwork.net.  This new domain provides a much shorter  URL for typing and remembering.  


After maintaining both sites for several years, it's time to retire the site at the old URL and have everyone using the tmwork.net domain.  


Impact / Changes

For most users, the impact is minimal as they can simply begin logging on with the new URL.  The one action that a user may need to take is to update any calendars that use the iCAL / Public Page URL for synchronizing schedules.  


For organizations, there are two additional changes to complete:  1) Single Sign-On integration, and 2) API integrations. We have provided some details below in the migration steps about these changes. Please contact support or the HelpDesk with questions or help with this change.


Timeline

The target completion date for this change is April 2nd, 2025.  We have some flexibility with the API migration (if needed) but ideally all customers will be connecting to the new URL by April 2nd.



Migration Steps


Step 1:  Start using the new site

    The URL is https://tmwork.net/signin.  This is the production site going forward. 

 

Step 2:  Update references to public pages 
 

The base URL’s for public pages are: 

Employee:     https://tmwork.net/public/empsch 

Location:    https://tmwork.net/public/locsch 

 

These links, with the unique codes for each employee or location, are available within the application. 

 

Step 3: Migrate Single-Sign-On (SSO) calls to the new URL

Old URL’s for SSO can include: 

https://www.schedulesource.net/Enterprise/xhandlers/<SomePageName>.aspx 

https://www.schedulesource.net/Enterprise/teamwork/sso/ 

https://www.schedulesource.net/Enterprise/teamwork/saml/sso/<ID>/<Type> 

https://www.schedulesource.net/Enterprise/teamwork5/saml/sso/<ID>/<Type> 

The new URL for SSO is: 

https://tmwork.net/api/ops/saml/<ID>/<Type> 

            

                Where <ID> is your organization id and <Type> designates the portal or portals to check.  

                Valid values for <Type> are emp, mgr, and emp-mgr

                ***** Note:  We are ready to help implement new SSO metadata as necessary. *****


Step 4: Update Kiosk Browsers with new URL

If the organization is using the browser based Kiosk, the base URL needs to be changed, without changing the remaining query values in the URL.  For example, these:

        https://www.schedulesource.net/Enterprise/Kiosk/?<additionalvalues>

        https://www.schedulesource.net/Enterprise/TeamWork5/Kiosk/?<additionalvalues>

become:    

        https://tmwork.net/Kiosk/?<additionalvalues>


Step 5: Migrate API calls to the new URL

ScheduleSource has implemented a variety of API endpoints over the years.  From the original SOAP/Xml endpoints to the read-only genericio.aspx page, to the newer Data I/O endpoints (/api/io/<EntityType>).   All of these variations are still supported under tmwork.net, except the paths have moved.  We are utilizing URL rewrite tools to support the old paths, but it would be best to use the new paths when migrating to the new site. 

The table below lists common endpoints from V3 and their new paths on tmwork.net (TW5).    

V3 (https://www.schedulesource.net/Enterprise)  

TW5 (https://tmwork.net) 

/TeamWork/Services/genericio.aspx 

/services/genericio 

/TeamWork/Services/genericio.asmx 

/services/genericio.asmx 

/TeamWork/Services/v200/Service.asmx 

/services/service.asmx 

/TeamWork/Services/v200/External2.asmx 

/services/External2.asmx 

Or, for TW5 on the old site: 

https://www.schedulesource.net/Enterprise/TeamWork5/ 

Becomes: 

https://tmwork.net/ 






Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article