Workflow project installer does not properly replace the project when project is already published with different name.

book

Article ID: 171735

calendar_today

Updated On:

Products

Workflow Solution

Issue/Introduction

For open and modifiable ServiceDesk projects it is fairly common to rename a project when unpackaging to better keep track of for example version: SD.ChangeManagementSimple.Voting.8.1.RU5

A situation where this issue can occur is ServiceDesk upgrade. When some projects with changed names like example above are published project installers from ServiceDesk with newer projects will not publish properly over existing published projects. This can cause published project folder to have multiple project files and old version of the project to (partially) get used and cause hard-to-track issues.

This behaviour is specific to project installer and does not occur with normal publishing from Workflow Designer.

Cause

Workflow project installer does not properly replace the project files when project is already published with different name.

Resolution

Republish the affected problem from scratch:

  1. Remove the project's vDir in IIS Manager
  2. Stop IIS and Symantec Workfow Server Service
  3. Delete the project folder from %ProgramFiles%\Symantec\Workflow\WorkflowDeploy\Release\
  4. Republish the project. In case of ServiceDesk, the installers for current version of projects are in %ProgramFiles%\Symantec\Workflow\Installers\ServiceDesk

This issue is resolved in Workflow 8.5 and ServiceDesk 8.5.