Deprecation of the Windows-Legacy Compatibility and Orchestrator Package validation/code review

Feedback Orchestrator
,
1

Hi!

The problem that I have with new Windows project version:

  • after compiling package and publishing it to Orchestrator it is not possible to use package explorer to check differences => no quick code review then

  • published package can not be downloaded and check => no possibility to make code review on package published to Orchestrator or do it post factum

What is your suggestion for code review actions?
Our way of working is that dev is publishing package to Prod Orchestrator and send request to check package. Dev doesnt have Orchestrator to edit or create process in Prod.
If changes are small and its is update (not new project) I can do code review on explorer in Orchestrator.
If changes are bigger I can check overall changes in explorer, then download the project from Orchestrator and see what is inside it.
If it is a new project I download package and check it all.

With this approach package is deployed by one person (but it can not be used) and second person is approving.

With new Windows version I can’t do it. What is the best approach with Windows projects that is both efficient and in accordance with the four eyes principle?

@loginerror @marian.platonov

3

Any thoughts on that? Maybe @Pablito ?

4

When publishing there is an option you can select to include the XAML files in the package.

5

This not the solution. Still there will be not available explore option in Orchestrator. So how to do a code review without external software?

7

Hi, I’m happy to confirm that we have a fix underway for this, it should land in cloud sometimes in the next few sprints. You will be able to view only workflows that have the source code included in the package, of course.

9

Hi!

Thats great news! Would it be also implemented to Orchestrator on-premise?