Question

Is re-publishing same workflow to two environments a valid approach?

Workflow Version 9 Administration

Updated January 28, 2022

asked on June 15, 2015

To move workflows from Dev to Prod I have always used export and import. Recently I opened a workflow in Dev, switched the workflow designer to the Prod environment, and because I wasn't paying close enough attention I accidentally published the still-open Dev workflow to the Prod environment without realizing it, which updated the corresponding Prod workflow. (I had been about to do the export/import anyway so no harm done after I adjusted the connection profile). However, because I did this accidentally and had never even considered it before, I'm curious if there are any cons to using this approach that I'm not aware of?

0 0

Answer

SELECTED ANSWER

replied on June 15, 2015

The con would be you aren't presented with a wizard at time of import to adjust connection profiles and references to external objects.

The workflow will get published to production and require manual changing of the common changes prompted by the wizard.

Cheers,

Carl

0 0

replied on January 28, 2022

Hello Carl,

We are currently syncing our dev/qa/prod environments, and as part of that strategy, we are naming the objects the same across the 3 environments, so in the import wizard, we will choose 'Use Existing Object.' Outside the potential to choose 'replace', would the scenario presented in this question use the Prod asset (works as 'Use Existing') asset or replace it with the Dev Object? I notice you said there would need to be remapping, but that made me think you assume unique names across all 3 environments. Any insight is appreciated.

0 0

replied on January 28, 2022

Selecting "Use Existing" should use the object configuration of the destination workflow server as referenced in the Workflow Administration console and NOT replace it w/ the object from dev.

Example

A workflow activity makes use of a data source named "Business Tools" which is configured to a [devserver.business tools] sql table.

Upon promotion to your QA environment via the Export/Import process - if you have an existing data source on the QA Server's Workflow Server, named "business tools" and are presented w/ the question of "Use Existing" it will use the QA Server's data source and NOT replace it with the Dev Object.

Assuming the Workflow Server in the QA environment has a datasource "Business Tools" mapped to [qaserver.business tools] - the imported workflow will use the qaserver.business tools database and NOT the dev server sql.

Added confirmation Via - Importing Workflow Import Files (laserfiche.com)

0 0

Replies

replied on June 16, 2015

Thanks - I wasn't even sure this was a supported method, and I didn't even realize I had done it at the time. It wasn't until later when the workflow failed that I realized what must have happened. There should be some sort of way to identify open workflows as being from one server or another.

0 0

You are not allowed to follow up in this post.

Question

Question

Is re-publishing same workflow to two environments a valid approach?

Answer

Replies

Sign in to reply to this post.