Question

Feature Request: Ability to Remap Web Service When Importing Workflow

Workflow Forms

Updated September 28, 2024

asked on February 28, 2020

Most people name the web service in Workflow that connects to Forms 'Forms'. When importing a workflow from another system that was configured to use a web service named 'Forms' (or a different name that already exists) it gives the following error:

We need to be able to remap what web service is used just like the other options we have to remap when importing a workflow.

1 0

Replies

replied on February 28, 2020

Hi Blake and Jessica,

Turns out this error is caused by a case sensitivity mismatch between what the Workflow Import Wizard checks (case-sensitive) and what the Workflow Server stores (case-insensitive) for the web service name.

Basically, the Import Wizard looks at the process your importing, sees it has a "Forms" web service, thinks that's different than the existing "forms" web service, and then dutifully tells Workflow Server it needs to create a new web service called "forms". Workflow Server correctly reports back that a web service with that name already exists.

I strongly suspect one of your systems has the web service labeled "Forms" while the other has it as "forms". Get the capitalization matching and I bet the problem goes away.

That said, this is still a general usability bug. The Workflow team is now aware and they anticipate addressing it in a future patch or version.

Cheers,

Sam

2 0

replied on March 2, 2020

Samuel, thank you for the reply. We look forward to the fix. Until then it is still a little bit of a struggle since we cannot change the name of the web service in the Workflow Administration Console and have to delete and create a new one.

0 0

replied on January 25, 2024

Noting for the record that the import wizard case sensitivity bug described above was fixed in Workflow 11 in late 2021.

1 0

replied on February 28, 2020

I just went through this today and it was most unpleasant.

1 0

replied on January 25, 2024

Just wanted to bump this again, specifically being able to remap a web service when importing a workflow. Looks like we still can't do it in version 11.

0 0

View 2 previous replies

replied on January 25, 2024

What is the exact version of 11 that you're running?

0 0

replied on January 25, 2024

11.0.2306.898 for the Workflow Designer.

0 0

replied on January 25, 2024

This is trickier than it seems because unlike Data Sources which are effectively a black box of a connection + packaged query thrown at the connection, the Forms Web Service activities (Set / Retrieve Business Process Variables) have UIs that pull forms and fields. There's more involved than just swapping Web Service A for Web Service B.

0 0

replied on January 25, 2024

That makes sense for Forms web service activities. What about being able to do it for Custom types of web services? Those are the type that we ran into this week when transferring production workflows to our test environment. Even if we can't update the Forms web services, it would be nice if the wizard made a mention that the workflow contains Forms web service activities and they should be looked at.

0 0

replied on March 11, 2024 • Show version history

Hi Blake,

We could not reproduce the issue on Workflow 11.0.2306.898 for four types of the web service. During import, select use existing object in action works well.

Could you provide more details for us? Like which step it occurs the error, the activity used in workflow, the web service used in workflow and the web service name and type in the targeted workflow system.

0 0

You are not allowed to follow up in this post.

Question

Question

Feature Request: Ability to Remap Web Service When Importing Workflow

Replies

Sign in to reply to this post.