Migration of Workflow Management Packages to SAP Build PA

[tnt_phan]

Hello community,

I'm new to SAP Build and Workflow Management and stand before a little headscratcher. We use Workflow Management deploayd in Cloed Foundry and want to migrate to SAP Build Process Automation. I've followed the steps of this help page: Migrate to SAP Build Process Automation | SAP Help Portal. The workflows were successfully deployed to a PA instance, but we'd like to have capability to configure them in Process Automation also. Is it possible to migrate fully and import the project?

Best Regards,

Tony

[zeal_it_christopher_linke]

Hey there,

yeah, I think many of us have similar problems now. We don't want to start new Workflows with the "old" WF Management, but SAP Build is just not ready for new developments. There are many parts missing right now, so for me there are two options:

- Build with the old WF, than you have to manually re-develop it in SAP Build at some point

- Build with SAP Build, find workarounds for missing functionalities (CAP services, etc.) and then clear up the workarounds once SAP Build delivers the functionality

Does anyone see other options? Both aren't really good, but the second one is the way to go for me. At least for the user the UI etc. won't change, if you switch from old WF to the SAP Build there might be bigger consequences for the user, which should always be avoided.

If you want to get in contact to help each other, feel free to contact me.

[Jana_dK]

"The old way" of developing workflows and deploying them, will still be possible. Since it's developing your workflow in SBAS and deploying it to workflow management. But you can do the same with SBPA .. develop your workflow in SBAS (because of the extended functionality) and deploy them to SBPA instead of WF.

In my opinion, complex workflows can still better be developed in SBAS instead of switching to a process in SBPA.

[vbalko-claimate]

Hey zeal_it_christopher_linke,

good to hear, that somebody else is in the same problems and is looking for way how to solve it.

We have just (before christmas) delivered project to customer, which is implemented as a live package in Workflow management. It is really pain in the a** to distribute the changes among landscape (dev, test, prod), because there isn`t any way how to transport the package - except manual export and import as a file. But the cockpit for managing variants, decision tables etc. in one place for one project is really convenient and key users on customer side are happy with it.

But sunset of WFM - with Manage Package Application with it puts us into very inconvenient situation, because BUILD lobby dont have replacement/successor functionality for that (manage packages) and therefore any change request will get us into situation, when we wouldnt be able to deliver change, because we wont have application to modify/update that custom live package.

I would really like to hear if anybody found out how to solve that not pleasant situation - sunset of WFM and introduction of BUILD with incomplete feature set.

Recently, SAP announced in Whats New for BUILD, that they delivered support for Cloud Transport Service, but today I found, that that message disappeared and help page from that message is out - https://help.sap.com/docs/PROCESS_AUTOMATION/a331c4ef0a9d48a89c779fd449c022e7/f778a164c9ab4723a2b7e1...

archana.shukla dont you know anything about that support of transport service for BUILD Process Automation artifacts? Or at least what is best practice for that?

[Archana]

Hello Tony,

We need to look into your process and different capabilities that you are using to advice you better. Please raise a ticket on LOD-BPM-BPC component for workflow management content migration and we will support you accorindgly.

[tnt_phan]

Helllo Archana,

thanks for your answer. Our application is still in development and uses SAP workflow managment with custom user, script and service tasks in its workflows. Since Workflow Management is sunset and supposedly integrated with Process Automation I was tasked with finding ways of migration. Goal is to have the project in Process Automation to continue development, especially the tasks. So far I found the possibility to export the WM package into the PA lobby as a live process, but it can't be configured there (only the visibility scenario that was used). If I understand correctly, the workflows have to be edited in BAS? Or is there a way to import/rebuild them in Build PA?

Regards,

Tony

[Archana]

Hello Tony,

To update the workflows deployed from SBAS, can only be configured from SBAS. If you can be specific what exactly you wish to configure, I can help you better.

Regards,
Archana