Sladescross's Blog

Blogging about Sharepoint related stuff

PowerShell and Workflow September 30, 2013

Filed under: Channel 9,Powershell,Powershell Workflow,Workflow — sladescross @ 4:03 pm



PowerShell Workflow September 14, 2013

Filed under: Powershell,Powershell Workflow,Workflow — sladescross @ 8:41 pm


Workflow Manager Stopped Working March 12, 2013

Filed under: Bug,SharePoint 2013,Workflow,Workflow Manager — sladescross @ 8:57 am

fond out how to enable and view the workflow manager log file, please follow
the technet guide at:
From the error message it seems the problem is related to database permission
related. So connected to the database (using SQL management studio) and found
out the workflow manager windows service user’s (under whose credentila’s the
workflow service is running) security settings. The original permission I found
was “WFServiceOperators” and then I added dbo permission to the user
also.  Then I restarted the SQL service and it all started working. I know
this is not the best solution but for time being the hack solved the problem in
my Dev.




SharePoint 2013 Workflow Manager 1.0 Debugging March 8, 2013

Filed under: SharePoint 2013,Workflow — sladescross @ 8:14 am

Database Log

In the workflow Management database, there’s a table ‘DebugTraces’. I’ve noticed that sometimes Workflow Manager write down errors/debugs in this database tables. You can go and take a look if something is useful for your workflow debugging.

Locate and fix website errors and poorly performing web pages.
Analyze HTTP headers, POST data, cookies, error codes and SOAP envelopes.
Measure the size, execution and downloading time of dynamic web pages.
View the traffic from browser add-ons, ActiveX components and Java applets.
Decode HTTPS connections and gzip/chunked encodings.
See complete stats in the comprehensible form of charts and diagrams.


Workflow Manager 1.0 Setup March 6, 2013

Filed under: OAuth,SharePoint 2013,Workflow,Workflow Manager — sladescross @ 3:01 pm

Overview of Workflow architecture.

Planning and prerequisites like windows firewall and Run As account.

You can specify the SQL Server Instance and database name for each of these databases. In the SQL SERVER INSTANCE text box, the name of the SQL Server instance on the current computer appears by default. To specify a different SQL Server, type the complete name of the SQL Server instance that will host the databases for the farm. The current user needs to have SysAdmin privilege on this SQL Server instance. Refer to the SQL Server section in System Requirements (Workflow Manager 1.0) for understanding SQL Server requirements.

In the text box under Configure Admin Group enter the name of the user group. This is the user group for which you want to grant access for all databases that you are adding to the farm and service configuration.

By default, the administrative group name is used. BUILTIN\Administrators appears by default. Every user in this group has administrative access to the databases that are part of the farm. If this group is local, ensure that the group also exists on all computers in the farm and on the SQL Server that you specified earlier.

This section describes known issues in Workflow Manager 1.0.

•Configuration fails when server’s administrator group contains accounts in a different domain

•Configuration fails when server’s administrator group contains unresolvable SIDs

•Add-WFHost cmdlet does not work across domains

•If the permissions of a workflow scope are set to BUILTIN\Administrators, Client Applications must run using elevated permissions


Registering workflow service problem. Use force.

I have installed all the components for workflow. And ran the following command.

Register-SPWorkflowService -SPSite “http://homebase” -WorkflowHostUri “http://Workflow:12291″ -AllowOAuthH

However i need to change the url it points to however it wont let me i get the error Failed to register because the farm or partition
is already registered with a workflow service

Is there a way to “UNREGISTER” i have not found a way. I even deleted the web app and recreated it in hopes the config was stored at the web app level. But did not work.

An event happens in a SharePoint workflow when an item is added or an item is changed. A workflow can wait for these events to happen before proceeding with the workflow. The Eventing actions in SharePoint Designer 2013 Preview are:

Wait for Event in List Item: Used to wait for a new item to be created or an item to be changed.

Wait for Project Event: Used to wait for a project to be checked in, committed, or submitted.


Update Approval Task Programmatically February 26, 2013

Filed under: Programmatically,Task,UPDATE,Workflow — sladescross @ 2:11 am


SharePoint 2013 Workflow January 3, 2013

Filed under: 2013,SharePoint 2013,Workflow — sladescross @ 2:28 pm


Workflow Improvements in Setting August 14, 2012

List workflow events.

External system messaging improvements CallExternalMethod and HandleExternalEvent.

The assembly name and public key information can be obtained using GACUTIL.EXE /l.

Walkthrough of pluggable workflow service.

Step 2 – Update the web.config

Once the pluggable workflow service is constructed, it needs to be registered with the workflow runtime that runs in SharePoint. This is done by editing the web.config section for workflow services. The web.config editing required should be done using a feature receiver that calls SPWebApplication.WebConfigModifications.Add. The following code shows the additional configuration entry to be added:


Workflow Initiation and Association Parameters June 14, 2012

Filed under: Association,Initiation,Parameters,Workflow,Workflow Parameters — sladescross @ 9:29 am

Then another layer pops up with the workflow information that is controllable for the chosen item. When you choose a workflow to start, the form that comes up next is the initiation form. This is a list workflow or associated reusable workflow example, however the forms of site workflow or globally reusable workflows are also initiation forms.

On the contrary, association forms however, face users only when a reusable workflow is being associated.

Association and initiation forms are displayed for users to complete before any workflow actually starts. You can use these forms to enable users to set parameters and other information for the workflow in advance. Association forms address how the workflow applies to a specific list, library, or content type; initiation forms address how the workflow applies to a specific SharePoint item.

Association forms are displayed to administrators when they first decide to add—or associate—a workflow with a particular list, document library, or content type. You can use association forms to let an administrator specify parameters, default values, and other information for the workflow as it applies to items on the list, library, or content type with which the administrator is associating it.

Initiation forms are displayed to users when they start a workflow on a specific SharePoint item. You can use initiation forms to let users override or append the association parameters set by administrators, or specify additional parameters or information about the workflow as it applies to the specific SharePoint item. Not all workflows need initiation forms.

The initiation form can be the same form as the association form. For example, using the same form for each workflow form enables you to let administrators set certain default parameters during workflow association, and then let the user who actually starts the workflow instance on a particular item review and overwrite those default parameters.

You cannot use the fields you need to make the workflow logic.

· Reusable workflow with base content type

o You are an advanced user of SPD workflow so you know the concept of base content type for reusable workflow.

o First, you create a new content type and add the necessary fields to the content type. And in the ‘Create Reusable Workflow’ dialog, designate the content type you created as the base content type.

o Now you can see the fields in the workflow designer and you can achieve what you are required to do. This has no issue with reuse scenario as long as you associate this workflow with the content type and the content type is added to the list or document library.

o But what if you found out you need a new field? Every time you need a new field, you have to go to site content type or the site column UI either on the server or on SPD.

o Another weakness still exists. When you want to move your workflow using ‘Save as Template’, the unpackaged workflow will lose some information on the base content type if the base content type is a custom content type or the content type contains a custom site column.


When do we need association columns

Let’s first start off by setting a scenario. You are a workflow author who is used to using SPD and you are required to make a workflow that should be used in many lists or document libraries with some workflow-specific fields. How do you implement it? Here are some examples of choices you might try to achieve this goal.




SharePoint Workflow Resource Center June 13, 2012

Filed under: Resource,Resource Center,Workflow — sladescross @ 10:06 pm

Workflow Centre



Get every new post delivered to your Inbox.

Join 63 other followers