Best practices on updating shared workflows using Windows project

Help Studio
, , , , , ,
1

When updating our projects from Windows-Legacy to Windows, we face this following error, already mapped on troubleshooting guide:
Troubleshooting Guide : Conversion from Windows-Legacy project to Windows project

We are aware of this limitation:
Invoke workflow file activity in Windows project doesn’t support xaml file which doesn’t exist under the project folder.

But not satisfied with the solution:
Modify logic to use xaml file under the project folder or use Library etc.

We have over 200 processes and many of them use shared workflows, the main example is system logins.

If we follow the suggestion and create libraries for these shared workflows, once this library is updated we would have to update all these 200 processes one by one. Each process has its own repository.

Do you have any other recommendation on how to deal with this?
What is the best practice to have updated shared workflows using Windows project?

2

Hi!

Sorry to hear that, but yes, best practice is to use libraries for reuseable components.

3

This could be of help if you want to mass update the dependencies Studio - Project Dependencies Mass Update.

4

Hi @natcmll ,

I see thats the only solution u need to .
Modify logic to use xaml file under the project folder or use Library etc.

Regards
Sandy

5

Hello everyone, we decided to turn these workflows into separated processes to run with Invoke Process.

1 Like
6

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.