New SAP SuccessFactors App in the Microsoft Teams App Store and Deprecation of Legacy App Package

[VanessaLi]

What’s New

You may have seen this Roadmap Explorer item that with the release as of March 4th 2024, a new SAP SuccessFactors App will be available and published to the Microsoft Teams App Store.

As an admin, you may choose to search for this app in Manage Apps in Teams and install this app for all yourusers in the organization. Once the admin has enabled it for your organization, the end user may choose to search for this app directly from the Teams App Store and download it/install it to their Teams. Alternatively, admin may choose to install and pin the new App for all users in Manage Apps. 

This change is made to reduce your administrative chores in downloading, uploading, and upgrading app packages every time we deliver new features. It also enables users to explore the app themselves and increases exposure.

Some resources to help you with the enablement:

• Video demo of how to setup this Latest App here.
• Implementation guide of how to set up the new App here.
• Learn about what features we are delivering to the Latest App in this Help doc and this video demo. (Video TBD)

---------------------------------Read on if you are an existing customer on Legacy App---------------------------------------

Existing Customers Migration

For existing customers who have already installed the Legacy App (via zip package), there are some actions required to help you with the migration:

Step 1: search for this new app in Manage Apps from the Teams App Store and install this app.

Step 2: Disconnect from the Legacy App and connect to the new Latest App. Manually setup the connection and switch to the new experience by following onscreen instructions embedded in the ‘Learn More’ buttons on the SAP SuccessFactors App in Teams (Legacy) and SAP SuccessFactors App in Teams tabs of the Work Tech Configuration page in Admin Center. The two tabs will co-exist for a few months until the 1H 2024 release.

The previous legacy app, which is the custom SAP SuccessFactors App package (zip file) that you downloaded via the Work Tech Configuration page of the Admin Center will reach End of Maintenance and be Deleted as of the 1H 2024 release (May 2024), you will no longer be able to download that zip file or access that app after that time.

Step 3: End users may now search for the new App via Apps tab in Teams. Alternatively, admin may choose to install and pin the new App for all users in Manage Apps.

Recommended: Admins may choose to uninstall and unpin the old app on behalf of all end users so as to not confuse them with two Apps.

Migration Timeline

We encourage you to complete the transition no later than the 1H 2024 release (May 2024). As of March 2024, new features will only be available in the app downloaded from the Teams app store.

Learn More

Additional resources about how to transition into the new App, please visit the below links:

• Switching to the New Experience of SAP SuccessFactors App Installation
• Installing the SAP SuccessFactors App from Microsoft Teams App Store (New Experience) 

If you encounter a technical issue while transitioning from the Legacy App to the Latest App, submit an incident within the SAP Support Portal, using the component LOD-SF-EAS-WRK.

If you have further questions, please leave a comment in this post.

[chrisstokes4]

@VanessaLi useful post thanks. How do we get notified when new features become available in the Teams app? This week Time Off approvals seem to have started appearing but I’ve not seen any updates about this ahead of it happening unless I’m missing something? Thanks 

[VanessaLi]

@chrisstokes4 Usually new features will be listed here https://help.sap.com/docs/SAP_SUCCESSFACTORS_PLATFORM/3adee415c1eb4b918bc0172afc76948c/87e6bd834acd4... or in this chapter  https://help.sap.com/docs/SAP_SUCCESSFACTORS_PLATFORM/3adee415c1eb4b918bc0172afc76948c/8dfaafbbfb9c4... 

Our roadmap explorer will also briefly introduce the upcoming roadmap items. https://roadmaps.sap.com/board?PRODUCT=089E017A62AB1EDA94C15F5EDB3320E1&range=CURRENT-LAST&q=work%20... 

As of Time off use case, we have plans to deliver the end to end scenario of submitting a time off request, approving the time off request is 1H 2024 timeframe. This is still work in progress therefore the whole use case is not ready yet, but you may see us iteratively deliver the use case.

[mohitsomani2003]

Hi Team, 

@VanessaLi  We are trying to activate Microsoft Teams functionality in one of our SF instances.

1) in Work Tech Configuration in Admin Center, we do not see the option "SAP SuccessFactors App in Teams".  We only have the legacy option, which is currently disconnected.

Is it something which will be available in SF from 4th March 2024? Or am i missing something here?

2) Also, can we connect multiple SF instances to same Microsoft Teams Tenant (e.g. Test & Productive SF Instance to Productive Teams Tenant) ? Will the functionalities work and send the information correctly to correct instance using ESS Quick actions from Teams?As per the documentation, it seems to be possible. But the next statement also is confusing.

Best Regards,

Mohit Somani

[VanessaLi]

@mohitsomani2003 Correct, it will be available on 4th March for you to re-connect (you have to disconnect from the Legacy one first).

[mohitsomani2003]

Thanks  @VanessaLi 

Also, if you can clarify this?

Can we connect multiple SF instances to same Microsoft Teams Tenant (e.g. Test & Productive SF Instance to Productive Teams Tenant) ? Will the functionalities work and send the information correctly to correct instance using ESS Quick actions from Teams?As per the documentation, it seems to be possible. But the next statement also is confusing.

Regards,

Mohit Somani

[VanessaLi]

@mohitsomani2003 it is not possible to connect multiple SF to the same Teams. Nor is it possible to connect one Teams to multiple SF. That is what we mean by the mapping is unique. We recommend to connect Test SF to Test Teams, then Prod SF to Prod Teams. 

To achieve multiple mapping is rather challenging for us therefore the plan is support this is unknown at this point. 

[mohitsomani2003]

Thanks @VanessaLi for the clarification. 

Also, one more follow-up (as we expect these questions from clients as well).

As we are more into exploring phase, with many stakeholders for different processes, do you see any problem,

1. if we connect SF Test with Microsoft Teams Productive Instance for exploration, and give access to Apps to controlled users.

2. Once we would like to connect SF Production, we "disconnect" the connection in Work Tech Configuration from SF Test Instance,  and create new connection from SF Production Instance.

Do you see any potential challenges here?

Regards,

Mohit Somani

[VanessaLi]

@mohitsomani2003  This is a great question. Answer is yes, that is possible and recommended. You must first disconnect from the SF Test, then go to SF Prod to re-connect.

[Ethan_Dai]

Hi @VanessaLi,

We are planning to do it like that as well (connect SF Test to Prod Teams) and test out the SF app in Teams for selected users first but I have a question / concern around the user mapping step.

If we map Test SF users with Prod Teams (AD Azure) users, would there be any unexpected issues?

The users in our Test SF won't be aligned to that of Prod Teams, will the user mapping all the sudden create our Test SF users in Prod Teams (AD Azure)?

Thanks

[VanessaLi]

@Ethan_Dai No it won't create new users in Prod Teams. The mapping is always done on existing users from both sides.

If there are no matching email addresses between Test SF and Prod Teams then the mapping will simply fail. Therefore for this testing, you need to make sure that the users in Prod Teams exists as well in SF Test.

[Ethan_Dai]

Thanks @VanessaLi,

Some Prod Teams users do exist in our Test SF but not all. And what would happen in this scenario? Would the user mapping be successful or fail?

And would the SF Teams app be working for the users that do exist in both systems?

If not, then it is almost impossible to test it out using this approach as users in Prod and Test systems won't 100% align...

Regards

[Ethan_Dai]

Hi @VanessaLi,

Just wondering if you had a chance to look into my question from 4 Mar.

Thanks

[VanessaLi]

@Ethan_Dai  In the SF Admin Centre, the user mapping for whoever is setting up the connection has to be successful (the admin user). Once successful, go to the Teams App, and the end users using the app may partially succeed or fail depending on if they have a valid user on both sides. The App will work for those who are successfully mapped.

[chrisstokes4]

Thanks @VanessaLi for the clarification. We went out and explained to our managers that time off approvals they were seeing come through were a new feature and time off requests were coming later on, but then around a week ago they disappeared again! Do you know why? It’s really confusing our comms messages. Thanks

[VanessaLi]

@chrisstokes4 

Good catch, we have released this Time Off Approval by accident and prematurely, we applied an immediate patch to remove it afterwards. Therefore it is now removed.

We will be officially releasing the whole Time Off scenario (submit Time off, approve time off) in the upcoming months. Cannot promise it will be 1H 2024, it may slip into a monthly release, for example June/July.

[GuadalupeRangel]

Hi @VanessaLi,

I have a similar question to a previous one, can we connect 2 TEST SF instances to the same Microsoft Teams Tenant? we have 2 test instances, one in Germany and one in China and only one MS Teams

Thanks

[VanessaLi]

@GuadalupeRangel unfortunately, only a 1:1 mapping is supported now.