SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

my workflow is deployed through the following script in SharePoint 2010:

# Set CurrentDirectory
$callingDir = Split-Path -Parent $MyInvocation.MyCommand.Path
[Environment]::CurrentDirectory = $callingDir

# Includes
$MainScriptName = "XXX.SharePoint.Powershell.YYY.ps1"
$MainScriptPath = Join-Path -Path $callingDir -ChildPath $MainScriptName

if (Test-Path $MainScriptPath)
{
    # use file from local folder
    . $MainScriptPath
}
else
{
    # use central file (via PATH-Variable)
    . $MainScriptName
}

Setup

$WebAppUrl = "NONE"

$SolutionPackageName = "Dataport.Survey.Webpart.wsp"
InstallSolution $SolutionPackageName $WebAppUrl

TearDown

After that the workflow is shown as "deployed" (solution is provided). If I want to use the workflow (for example on a list) I can´t do this. In the Websitesettings (under "Workflows") the workflow is shown as inactive. But why? What can I do to use the workflow?

Thank you in advance!

share|improve this question
up vote 0 down vote accepted

Ok - the problem is fixed now. I had accidentally set "hidden=true" on the feature. If I set "hidden = false" on the feature the workflow is useable.

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.