0% found this document useful (0 votes)

4K views

Nintex Workflow 2007 SDK 1.2

Nintex Workflow 2007 Software Development Kit (SDK) includes API documentation as well as technical "how to's" and code examples. This document is intended for developers. It will be updated to include new API documentation and practical examples as they become available.

Uploaded by

wregwe

Available Formats

Download as PDF, TXT or read online on Scribd

0% found this document useful (0 votes)

4K views

Nintex Workflow 2007 SDK 1.2

Uploaded by

wregwe

Available Formats

Download as PDF, TXT or read online on Scribd

You are on page 1/ 235

Nintex Workflow 2007

Software Development Kit

Software Development Kit v1.2

OVERVIEW
Welcome to the Nintex Workflow 2007 Software Development Kit (SDK). This document is intended for developers and includes API documentation as well as technical "how to's" and code examples. This SDK will be updated to include new API documentation and practical examples as they become available. Please submit all feedback to [email protected]. To download the latest version of the Nintex Workflow 2007 software development kit and supporting resources please see http://www.nintex.com/Nproducts/Workflow2007SDK.aspx.

WHATS NEW?
Section on creating custom task forms for the Flexi Task action Updated the task form example to support Flexi Task action New web service methods: ProcessFlexiTaskResponse2 and GetOutcomesForFlexiTask Updated web service methods with a more descriptive return type: ProcessTaskResponse3, ProcessFlexiTaskResponse2 Added descriptions for web service methods AddLongTermDelegationRule, DeleteLongTermDelegationRule and the PublishFromNWF* and SaveFromNWF* methods

www.nintex.com

Page 2 of 235 [email protected]

connect.nintex.com

Software Development Kit v1.2

SUPPORT RESOURCES
This section lists a range of software required to successfully develop for and extend Nintex Workflow.

Nintex Connect The Nintex Connect site provides a forum for discussing the use and development of Nintex Workflow 2007, along with additional examples and downloads. Download: http://connect.nintex.com

Microsoft .NET Framework 3.0 Redistributable Package The Microsoft .NET Framework version 3.0 redistributable package installs the common language runtime and associated files required to run applications developed to target the .NET Framework 3.0. Download: http://www.microsoft.com/downloads/details.aspx?FamilyId=10CC340B-F857-4A14-83F525634C3BF043&displaylang=en

Visual Studio 2005 extensions for .NET Framework 3.0 (Windows Workflow Foundation) This addin provides developers with support for building workflow-enabled applications using Windows Workflow Foundation. Compatible with the released versions of the 2007 Microsoft Office system, Microsoft Windows Vista, and the .NET Framework 3.0 Runtime Components. Download: http://www.microsoft.com/downloads/details.aspx?FamilyId=5D61409E-1FA3-48CF-8023E8F38E709BA6&displaylang=en

Microsoft Visual Studio 2005 Team Suite Service Pack 1 This download installs Service Pack 1 for Microsoft Visual Studio 2005 Standard and Professional, and Team editions. Download: http://www.microsoft.com/downloads/details.aspx?FamilyId=BB4A75AB-E2D4-4C96-B39D37BAF6B5B1DC&displaylang=en

Visual Studio 2005 Service Pack 1 Update for Windows Vista The Visual Studio 2005 Service Pack 1 Update for Windows Vista addresses areas of Visual Studio impacted by Windows Vista enhancements. Download: http://www.microsoft.com/downloads/details.aspx?FamilyID=90e2942d-3ad1-4873-a2ee4acc0aace5b6&displaylang=en

www.nintex.com

Page 3 of 235 [email protected]

connect.nintex.com

Software Development Kit v1.2

HOW TO INTERACTING AND EXTENDING NINTEX WORKFLOW
This section contains a number of examples demonstrating how to extend Nintex Workflow 2007 to meet custom business requirements. This section contains the following examples 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. InfoPath Forms Integration Create a Custom Workflow Action Overview Create a Custom Workflow Action Step by Step Guide Create a Custom Task Response Form Create a Custom Flexi Task Response Form Export Workflow History BizTalk Integration Re-brand Nintex Workflow Create custom context data items Use the Error Handling Panel Deploying a Nintex Workflow as part of a SharePoint solution package (WSP). Deploying a custom workflow action as part of a SharePoint solution package (WSP). Create an Inline Function

www.nintex.com

Page 4 of 235 [email protected]

connect.nintex.com

Software Development Kit v1.2

HOW TO: INFOPATH FORM INTEGRATION SKILL LEVEL: INTERMEDIATE OVERVIEW
This example will demonstrate the integration of Nintex Workflow into an InfoPath form. For the example we will be using a basic expense form and business process; the form will collect some user details and details of an expense claim. The form will then be submitted to a workflow for routing and approval. The approval process will be integrated directly into the InfoPath form which will contain business logic to ensure the form is not updated incorrectly. Please note that this example requires Microsoft Office 2007 InfoPath as some of the functionality is not available in Microsoft Office 2003 InfoPath. When integrating InfoPath and Nintex Workflow the two technologies do not directly interact with each other, they communicate via SharePoint. This interaction is achieved via columns on the library; InfoPath writes key status information to the columns and Nintex Workflow reads and writes back to the same columns allowing data to be shared. The full example provided has hard coded data sources configured to communicate with the example SharePoint web server http://development.nintex.com. When using this example file you will be required to change the data sources to point to a valid URL in your environment. Note: The provided examples have been developed with InfoPath Form Services enabled, which would allow the forms to be used in InfoPath or a web client.

REQUIREMENTS
This example requires the following technologies and/or applications: Windows SharePoint Services 3.0 Nintex Workflow 2007 Office InfoPath 2007

You may receive warning messages about the publishing location of the provided SDK example InfoPath Form. You should ignore the messages and once the form is loaded, republish it and then open the form from its published location.

1. Bind the form sections to the appropriate data sources. a. Bind the Employee Information section to expenseReport/Employee. When the Department field has been added, change the control element from a text box to a drop-down list box and configure some sample department names. b. Bind the Approval section to expenseReport/ExpenseApproval c. Bind the Submit section (the last section on the form [the large orange section]) to expenseReport Tip: How to bind a field/control 1. An unbound field/control will have a red cross next to it ( ), when you hover over the red cross the following message will be displayed. Right click on the unbound field/control and select Change Binding ( ). Fromt the Selection Binding pop up window select the required field or group and click OK.

2. 3.

Note: When binding a field control you must always bind it to a field in the data source. However controls such as the Section control can be bound to a group in the data source. 2. Add the fields to the surface area: a. Add fields ID, Name, Email and Department to the Employee Information section. b. Add field Item as a Repeating Table to the section Expenses. Display the footer on the repeating table (Repeating table properties | Display | Options | Include Footer). Add the Total field to the repeating table footer. Set the Total fields default value to sum(Amount) (this will calculate each item in the expense from and give us a single total). c. Add field Comments to the Approval section. Tip: How add a field to the design area To add a field from the data source tool pane, you can simply drag and drop it on to the design area. Once it is there you can adjust the size and properties (including validation rules, conditional formatting, etc).

Tip: How to set a default value on a field You can set the default value for a field control from the properties window for the control. The following steps show how to set the default for a text field control. 1. Right click on the text box. 2. Click Text Box Properties. 3. In the properties window enter the default value into the Value field under the heading Default Value. Note: Default values can be calculated, which allows you to use a combination of lookups, functions and hard coded values. 4. Add buttons to control the approval process. These buttons will be used for the key actions on the form (submit, approve and reject). a. Add two buttons to the Approval section titled Approve and Reject b. Add a button to the last section of the form titled Submit.

The form UI has now been designed. Next we need to configure the form to communicate with the Nintex Workflow web service.

www.nintex.com

Page 8 of 235 [email protected]

connect.nintex.com

Software Development Kit v1.2

Figure: The completed design of the InfoPath form.

Step 3 Data Connections 1. Add a new data source to receive the current workflow tasks for the current user from a web service. a. Click the Tools menu and select Data Connections b. Click Add c. Select Create a new data connection to: and select Receive data. Click Next d. Select Web service and click Next e. Enter the URL http://development.nintex.com/_vti_bin/nintexworkflow/workflow.asmx?WSDL, remembering to replace http://development.nintex.com with a url to a teamsite in your environment. Click Next f. From the selection of operations select GetRunningWorkflowTasksForCurrentUser. Click Next g. Click Next h. When asked to store a copy of the data in the form template, ensure this is not selected as it is not required and could cause issues. Click Next i. When asked if the form must automatically retrieve data when it is opened ensure this is not selected. Click Finish. Add a new data source to process the workflow task (approve/reject) for the current user from a web service. a. From the file menu click Tools -> Data Connections b. Click Add c. Select Create a new data connection to: and select Receive data, click Next d. Select Web service and click Next e. Enter the URL http://development.nintex.com/_vti_bin/nintexworkflow/workflow.asmx?WSDL. Click Next f. From the selection of operations select ProcessTaskResponse. Click Next g. Click Next h. When asked to store a copy of the data in the form template, ensure this is not selected, as it is not required, and would cause issues. Click Next i. When asked if you want to automatically retrieve data when the form is opened ensure this is not selected, click Finish.

www.nintex.com

Page 9 of 235 [email protected]

connect.nintex.com

Software Development Kit v1.2

3. Add a new data source to submit the form to a SharePoint library. a. From the file menu click Tools -> Data Connections b. Click Add c. Select Create a new data connection to: and select Submit data, click Next d. Select To a document library on a SharePoint site, and click Next e. Enter the URL http://development.nintex.com/myformlibrary, click Next (please note that the form library myformlibrary is a standard Form Library with no extra columns). f. For the File name enter the function concat("Expenses - ", now(), " - ", userName()). click Next g. Click Finish.

Step 4 Business Logic (Rules) 1. Configure the open behavior for the form: a. From Tools | Form Options select Open and Save, the click on Rules b. Add the rules outlined below. Use the Field Name References row as a fully qualified field reference. This will allow you to find the correct field in the Main data source. Name Conditions Actions Field Fully Qualified References Load Workflow Information FileUrl != 1. Set a fileUrl = FileUrl 2. Query using a data connection: GetRunningWorkflowTasksForCurrentUser fileUrl = GetRunningWorkflowTasksForCurrentUser /dfs:myFields/dfs:queryFields/ tns:GetRunningWorkflowTasksForCurrentUser/tns:fileUrl fileUrl = /my:expenseReport/my:ExpenseForm/my:FileUrl

Figure: Screenshot from InfoPaths logic inspector

www.nintex.com

Page 10 of 235 [email protected]

connect.nintex.com

Software Development Kit v1.2

Name Conditions Setup approval control Submitted = string(true()) AND SharePointTaskId != "" AND TaskType = "Approval" 1. Set a field's value: AllowApproval = true() Submitted = /my:expenseReport/my:ExpenseForm/my:Submitted SharePointTaskId = GetRunningWorkflowTasksForCurrentUser /dfs:myFields/dfs:dataFields/ tns:GetRunningWorkflowTasksForCurrentUserResponse/ tns:GetRunningWorkflowTasksForCurrentUserResult/tns:UserTask/ tns:SharePointTaskId TaskType = GetRunningWorkflowTasksForCurrentUser /dfs:myFields/dfs:dataFields/ tns:GetRunningWorkflowTasksForCurrentUserResponse/ tns:GetRunningWorkflowTasksForCurrentUserResult/tns:UserTask/tns:TaskType

Actions Field Fully Qualified References

Figure: Screenshot from InfoPaths logic inspector Name Conditions Setup editing control Submitted = string(false()) OR Submitted = string(true()) AND SharePointTaskId != "" AND TaskType = "Approval" 2. Set a field's value: AllowEditing = true() Submitted = /my:expenseReport/my:ExpenseForm/my:Submitted SharePointTaskId = GetRunningWorkflowTasksForCurrentUser /dfs:myFields/dfs:dataFields/ tns:GetRunningWorkflowTasksForCurrentUserResponse/ tns:GetRunningWorkflowTasksForCurrentUserResult/tns:UserTask/ tns:SharePointTaskId TaskType = GetRunningWorkflowTasksForCurrentUser /dfs:myFields/dfs:dataFields/ tns:GetRunningWorkflowTasksForCurrentUserResponse/ tns:GetRunningWorkflowTasksForCurrentUserResult/tns:UserTask/tns:TaskType

Actions Field Fully Qualified References

Figure: Screenshot from InfoPaths logic inspector

www.nintex.com

Page 11 of 235 [email protected]

connect.nintex.com

Software Development Kit v1.2

2. Configure the Approve button rules a. Right click on the Approve button and click Properties b. Click on the Rules button c. Add the rules outlined below. Use the Field Name References row as a field fully qualified field reference. This will allow you to find the correct field in the Main data source. Name Conditions Actions Set Approval Settings 1. 2. 3. 4. 5. Set a field's value: spTaskId = SharePointTaskId Set a field's value: outcome = "Approved" Set a field's value: comments = Comments Query using a data connection: ProcessTaskResponse Close the form spTaskId = /dfs:myFields/dfs:queryFields/tns:ProcessTaskResponse/tns:spTaskId SharePointTaskId = GetRunningWorkflowTasksForCurrentUser /dfs:myFields/dfs:dataFields/ tns:GetRunningWorkflowTasksForCurrentUserResponse/ tns:GetRunningWorkflowTasksForCurrentUserResult/tns:UserTask/ tns:SharePointTaskId outcome = /dfs:myFields/dfs:queryFields/tns:ProcessTaskResponse/tns:outcome comments = /dfs:myFields/dfs:queryFields/tns:ProcessTaskResponse/ tns:comments Comments = /my:expenseReport/my:ExpenseForm/my:Comments

Field Fully Qualified References

Figure: Screenshot from InfoPaths logic inspector 3. Configure the Reject button rules. a. Right click on the Reject button and click Properties b. Click on the Rules button c. Add the rules outlined below. Use the Field Name References row as a fully qualified field reference. This will allow you to find the correct field in the Main data source. Name Conditions Actions Set Rejection Settings 1. 2. 3. 4. 5. Set a field's value: spTaskId = SharePointTaskId Set a field's value: outcome = "Rejected" Set a field's value: comments = Comments Query using a data connection: ProcessTaskResponse Close the form spTaskId = /dfs:myFields/dfs:queryFields/tns:ProcessTaskResponse/tns:spTaskId SharePointTaskId = GetRunningWorkflowTasksForCurrentUser /dfs:myFields/dfs:dataFields/ tns:GetRunningWorkflowTasksForCurrentUserResponse/ tns:GetRunningWorkflowTasksForCurrentUserResult/tns:UserTask/ tns:SharePointTaskId outcome = /dfs:myFields/dfs:queryFields/tns:ProcessTaskResponse/tns:outcome comments = /dfs:myFields/dfs:queryFields/tns:ProcessTaskResponse/ tns:comments Comments = /my:expenseReport/my:ExpenseForm/my:Comments

Field Fully Qualified References

www.nintex.com

Page 12 of 235 [email protected]

connect.nintex.com

Software Development Kit v1.2

Figure: Screenshot from InfoPaths logic inspector 4. Configure the Submit button rules. a. Right click on the Submit button and click Properties b. Click on the Rules button c. Add the rules outlined below. Use the Field Name References row as a fully qualified field reference. This will allow you to find the correct field in the Main data source. Name Conditions Actions Submit Expense 1. 2. 3. Set a field's value: Submitted = true() Submit using a data connection: SharePoint Library Submit Close the form Submitted = /my:expenseReport/my:ExpenseForm/my:Submitted

Field Fully Qualified References

Figure: Screenshot from InfoPaths logic inspector 5. Configure advanced form UI a. Now the business logic has been created we have a field called AllowEditing which was configured in rule Setup editing control. With this field we can configure the relevant form controls to allow editing or to display a read only view. Use this field and configure the input fields Conditional Formatting. b. Configure the Approval section to only display if the field AllowApproval is true. c. Configure the Submit section to only display if the field Submitted is false

www.nintex.com

Page 13 of 235 [email protected]

connect.nintex.com

Software Development Kit v1.2

Nintex.Workflow.Activities.Adapters.IActivityDesignTime

This interface contains members to specify how the action is displayed during workflow design.
Nintex.Workflow.Activities.Adapters.IActivityPreview

This interface contains members to specify how the action is displayed in preview views (e.g. the workflow start page, viewing from the site gallery).
Nintex.Workflow.Activities.Adapters.IActivityRunTime

This interface contains members to specify how the action is displayed when viewing the progress of a running workflow. To simplify development, the abstract base class Nintex.Workflow.Activities.Adapters.GenericRenderingAdapter is provided. This class implements all necessary interfaces and provides generic rendering logic suitable for most activities. This SDK only describes creating actions that inherit from this base class. The following methods must be overridden:
public override NWActivityConfig GetDefaultConfig(Guid listId)

This method is used to return the default configuration xml for the action
public override bool ValidateConfig(ActivityContext context)

This method returns a boolean indicating whether or not the adapter has a valid configuration xml for the WF activity.
public override NWActionConfig GetConfig(Activity a, List<Activity> supportingActivities, Hashtable ruleConfigs, Guid listId, WorkflowVariableCollection variables)

This method returns an NWActionConfig built from an existing configured WF activity. This is used when rendering from previously saved Xoml. e.g. The workflow progress page or a saved workflow.
public override CompositeActivity AddActivityToWorkflow(NWActionConfig config, RootWorkflowActivityWithData parentWorkflow, CompositeActivity parentActivity, RuleConditionReference condition, WorkflowVariableCollection variables)

This method is called when building a workfow. This creates an instance of the WF activity and inserts it into the parent workflow. It is here that the configuration is read and the values in it assigned to the WF activity.
public override ActionSummary BuildSummary(ActivityContext context)

This method specifies the contents of the summary box displayed during design and in the preview views of the workflow. The following method may be overriden:
public override ActionSummary BuildRuntimeSummary(ActivityRuntimeContext context)

This method specifies the contents of the summary box for when viewing a running workflow. By default it displays the same content as BuildSummary() with the addition of start and end timestamps.

Creating the Configuration Dialog To ensure UI consistency across all dialogs and to simplify development, a custom master page has been created (ActivityUIMasterPage.master). This master page includes necessary client scripts containing common functions used to manipulate the configuration xml. It is recommended that your custom dialog uses this master page and this document assumes this is the case. Add a reference to the master page by including the following declaration in the aspx page:

ASP.Net

www.nintex.com

Page 19 of 235 [email protected]

connect.nintex.com

Software Development Kit v1.2

ASP.Net
<%@ Page MasterPageFile="/_layouts/NintexWorkflow/ActivityUIMasterPage.master"%>

For more information on the activity UI master page see the master page section in the SDK. Two JavaScript functions are required to retrieve and write configuration xml. These functions are called from the scripts included in the master page.
function TPARetrieveConfig()

This function must read the configuration xml and populate the controls in the dialog with the correct values.
function TPAWriteConfig()

Nintex Workflow Xml Node The first few nodes hold system data and configuration dialogs can ignore the values. The <TLabel>, <BLabel>, <LLabel> and <RLabel> elements hold the text is the top, bottom, left and right labels of the action. The attributes LCustLbl, RCustLbl, TCustLbl and BCustLbl specify whether the user has customized any label with the edit label dialog. The <ExpectedDuration> holds the total minutes value if the user has specified an expected duration. The <Assembly> and <Type> elements contain the reference to the adapter class for the action. The <IsValid> value tells the designer whether the action is completely configured. It is set automatically by the system based on result of the adapters ValidateConfig() method. The <ConditionUse> element is a system node related to conditions. The remaining nodes hold the configuration data. There are two sets of nodes: parameters and field references. Parameters hold explicit values and field references can be used for a dynamic list of values. There is no hard rule regarding when and how to use each. Remember that the default configuration is defined in the GetDefaultConfig adapter method. The following code in GetDefaultConfig would produce the corresponding Xml. C# NWActionConfig c = new NWActionConfig(); c.Parameters = new ActivityParameter[1]; c.Parameters[0] = new ActivityParameter(); c.Parameters[0].Name = "x"; c.Parameters[0].PrimitiveValue = new PrimitiveValue(); c.Parameters[0].PrimitiveValue.Value = "Some Value"; c.Parameters[0].PrimitiveValue.ValueType = SPFieldType.Text.ToString();

Nintex Workflow Xml <Parameter Name="x"> <PrimitiveValue Value="Some Value" ValueType="Text"/> </Parameter>

The child node of Parameter (and FieldReference) can be a PrimitiveValue or a Variable to represent a workflow variable. Using the correct value nodes allow for the use of helper methods in building the workflow to assist in automatically interpreting the configuration xml.

www.nintex.com

Page 24 of 235 [email protected]

connect.nintex.com

Software Development Kit v1.2

HOW TO: CREATE A CUSTOM WORKFLOW ACTION STEP BY STEP GUIDE SKILL LEVEL: ADVANCED OVERVIEW
This example details the steps required to create a custom action for Nintex Workflow 2007 (NW). This example will use the example of a custom Windows Workflow Foundation (WF) activity that executes a SQL command against a database. It will detail how to write the WF activity, the NW adapter, a user interface and how to expose the action in the NW designer. The completed solution is included in this SDK. This example will make use of the Nintex Workflow Action Visual Studio project template. For more information on Visual Studio project templates see http://technet.microsoft.com/en-us/library/6db0hwky(VS.80).aspx.

REQUIREMENTS
Windows SharePoint Services 3.0 Nintex Workflow 2007 Visual Studio 2005 Extensions for the .NET Framework 3.0 Visual Studio 2005 Service Pack 1

SUMMARY
This is a quick summary of the steps and procedures required to complete this example. 1. 2. 3. 4. Building the Workflow Foundation activity Building the Nintex Workflow adapter Building the configuration dialog Importing into Nintex Workflow

SUPPLIED SAMPLES
This example contains the completed Visual Studio solution for the Nintex Workflow SQL action. Also as a part of this example Nintex Workflow has developed a custom Visual Studio 2005 project template to aid in the development process of actions for Nintex Workflow. To deploy the Nintex Workflow Action Visual Studio project template copy the supplied zip file to you Visual Studio Project Templates (Visual C#) folder. This location of this folder can be found in your Visual Studio preferences (Tools -> Options -> Project and Solutions -> Visual Studio user project template location). Solutions 1. 2. {SDK Location}\Examples\ExecuteSqlAction {SDK Location}\support\NW2007ActionProjectTemplate

www.nintex.com

Page 25 of 235 [email protected]

connect.nintex.com

Software Development Kit v1.2

STEPS AND PROCEDURES
Step 1 - Building the Workflow Foundation activity Every Nintex Workflow action is a WF Activity. In this example, the activity will accept a connection string, a SQL statement to run against a database, and a reference to a workflow variable to return a result. For more information about developing custom WF Activities, visit http://wf.netfx3.com/. 1. Create a new Visual Studio solution

Add a Workflow Activity Library to the solution, and rename the default Activity1.cs to ExecuteSqlActivity.cs

Prepare project: Enter the code view by pressing F7 on ExecuteSqlActivity.cs. Change the class to inherit from Activity instead of SequenceActivity because we will be writing code directly into the Execute method. Change the namespace to MyCompany.WorkflowActions. Tip when changing the namespace make sure you update the *.Designer.cs file also (this is a partial class).

www.nintex.com

Page 26 of 235 [email protected]

connect.nintex.com

Software Development Kit v1.2

The Execute method of this activity implements simple data access code: C# using(SqlConnection conn = new SqlConnection(ConnectionString)) using(SqlCommand command = new SqlCommand()) { command.Connection = conn; command.CommandType = CommandType.Text; command.CommandText = SqlQuery; conn.Open(); object result = command.ExecuteScalar(); if(result != null) this.ResultOutput = result.ToString(); } return ActivityExecutionStatus.Closed;

Note: The values are retrieved from the Dependency Properties by calling the implemented property. Also note the ResultOutput is being assigned to. Any workflow variable that is bound to ResultOutput will now contain the value of result. 6. Add a check that the action is allowed to run in workflows. This is a security measure that will cause the workflow to fail if the action is not allowed on the site the workflow is running on. C# ActivityActivationReference.IsAllowed(this.GetType(), __Context.Web);

Add runtime context data: To provide more flexibility when configuring the SQL query, we want to enable lookups to context data. Context data consists of workflow variables, list item properties and other common data such as the user that initiated the workflow. In NW, lookups are done by using tags in a string. For example, {ItemProperty:Title} in a string is replaced at runtime with the title of the item that the workflow is running on. Formats for these references are: {ItemProperty:internalFieldName} properties of the item the workflow is acting on. {WorkflowVariable:variableName} workflow variables.

www.nintex.com

Page 30 of 235 [email protected]

connect.nintex.com

Software Development Kit v1.2

{Common:xxxx} predefined references. There is a list of common references is in the overview document. {WorkflowConstant:constantName} A workflow constant configured for the enviroment.

The activity is responsible for replacing the reference tags with actual values. Reference replacement is done by constructing an NWContext object and calling the AddContextDataToString method as shown here.

C# NWContext ctx = new NWContext(this.__Context, new Guid(this.__ListId), this.__ListItem, this.WorkflowInstanceId, CurrentWorkflowVariableValues, this); // Replace any inserted property references // (Common, ItemProperties and WorkflowVariables) with the current value. string sqlQuery = ctx.AddContextDataToString(SqlQuery, true);

connect.nintex.com

Software Development Kit v1.2

5. Override ValidateConfig C# public override bool ValidateConfig(ActivityContext context){}

This method defines when the configuration is in a state that the action can be published. The custom logic can check for anything; however there are some inbuilt methods for making sure the value entered is of the correct type. 6. Add a dictionary of ActivityParameterHelpers to assist validation C# Dictionary<string, ActivityParameterHelper> parameters = context.Configuration.GetParameterHelpers();

connect.nintex.com

Software Development Kit v1.2

15. Construct a new instance of NWActionConfig. C# NWActionConfig c = this.GetDefaultConfig(listId);

16. Retrieve the values from the activity. A dictionary of ActivityParameterHelpers assists when working with Dependency Properties: C# Dictionary<string, ActivityParameterHelper> parameters = c.GetParameterHelpers(); parameters[ConnectionStringProperty].RetrieveValue(a, ExecuteSqlActivity.ConnectionStringProperty, listId, variables); parameters[SqlQueryProperty].RetrieveValue(a, ExecuteSqlActivity.SqlQueryProperty, listId, variables); parameters[OutputProperty].RetrieveValue(a, ExecuteSqlActivity.ResultOutputProperty, listId, variables);

17. Retrieve the labels for the UI. C# ActivityFlags f = ActivityFlags.GetFlags(a); c.SetLabels(f);

18. Update the IsValid flag to reflect the retrieved configuration. C# c.IsValid = ValidateConfig(new ActivityContext(listId, ActivityReferenceCollection.FindByAdapter(this), c));

19. Override BuildSummary C# public override ActionSummary BuildSummary(ActivityContext context)

This method defines what is visible in the mouse over popup summary of the action. It should provide a brief summary of what the action will do. The ActionSummary takes a string that will be rendered. This example includes the connection string value to provide some contextual information.

www.nintex.com

Page 38 of 235 [email protected]

connect.nintex.com

Software Development Kit v1.2

C# Dictionary<string, ActivityParameterHelper> parameters = context.Configuration.GetParameterHelpers(); return new ActionSummary(string.Format("Run an SQL command on database {0}.", parameters[ConnectionStringProperty].Value)); Step 3- Building the configuration dialog The configuration dialog contains JavaScript to manipulate the configuration xml, which is an xml serialized form of the NWActionConfig object generated in the adapter. The template aspx form in the project already includes references to the Nintex Workflow dialog master page which references required script files. 1. Set the inherits property of the web form. As this assembly will be deployed to the GAC, the pages assembly reference must reference the strong name of the assembly. In the markup view, add the full assembly reference to the Inherits declaration.

Design the web form. Add html controls that will allow users to enter values for each parameter. You can ensure consistent styling by using the styles included in the master page. The following html provides a text control for the sql connection string, a textarea for the sql query and a select list to choose a variable to store the activity output in. ASP.Net <div class="RowBlue"> <span class="Label req">Connection String</span> <input type="text" class="InputWidth" id="connectionString" /> </div> <div class="RowBlue"> <span class="Label req">SQL Query</span> <textarea type="text" class="InputWidth" rows="30" id="sqlQuery"></textarea> </div> <div class="RowBlue"> <span class="Label">SQL Query</span> <select id="resultOutput" class="InputWidth"></select> </div>

Add script to populate the dialog. JavaScript is used to read and write to and from the configuration xml to the input controls. The xml is stored in a global object call configXml. TPARetrieveConfig reads values from configXml into the input controls. TPAWriteConfig takes values from the input controls and stores them in configXml. External script that is included in the master page initially populates configXml and persists it when the dialog is saved. Declare global variables for the objects:

www.nintex.com

Page 39 of 235 [email protected]

connect.nintex.com

Software Development Kit v1.2

JavaScript var connectionStringCtrl; var sqlQueryCtrl; var resultOuputCtrl;

TPARetrieveConfig runs when the dialog opens, so add code to first set the control variables: JavaScript connectionStringCtrl = document.getElementById("connectionString"); sqlQueryCtrl = document.getElementById("sqlQuery"); resultOuputCtrl = document.getElementById("resultOutput");

To allow the user to select from the list of variables that are defined, the resultOutputCtrl selection box must be populated with available choices. The JavaScript function ListWorkflowVariables will retrieve an xml node list of the variables that have been defined. In this case, we will filter the list to only show text variables. JavaScript var workflowVariables = ListWorkflowVariables(); for(var i=0; i<workflowVariables.length; i++) { if(workflowVariables[i].getAttribute("Type") == "Text"){ resultOuputCtrl.options[resultOuputCtrl.options.length] = new Option(workflowVariables[i].getAttribute("Name"), workflowVariables[i].getAttribute("Name"));} }

Now the controls are ready, the existing configuration values can be read from configXml. JavaScript connectionStringCtrl.value = configXml.selectSingleNode("/NWActionConfig/Parameters/Parameter[@Name ='ConnectionString']/PrimitiveValue/@Value").text; sqlQueryCtrl.value = configXml.selectSingleNode("/NWActionConfig/Parameters/Parameter[@Name ='SqlQuery']/PrimitiveValue/@Value").text; resultOuputCtrl.value = configXml.selectSingleNode("/NWActionConfig/Parameters/Parameter[@Name ='Output']/Variable/@Name").text;

Add script to save the configuration. TPAWriteConfig is called when the save button for the dialog is pressed. This function is responsible for modifying configXml with the values entered by the user. If custom validation is required, returning false will prevent the dialog from closing.

HOW TO: CREATE A CUSTOM TASK RESPONSE FORM SKILL LEVEL: ADVANCED OVERVIEW
This section describes how to create a custom task response form for the Request Approval or Request Review actions. Tasks assigned via these workflow actions are created with a specific content type that is installed when Nintex Workflow is activated. This content type has a custom edit form that is displayed when a user responds to a task. For more information about content types, see MSDN article Introduction to Content Types (http://msdn2.microsoft.com/enus/library/ms472236.aspx). The approval and review actions can be configured to use a different content type. A custom approval form can be assigned to this content type.

REQUIREMENTS
This example requires the following technologies and/or applications: Windows SharePoint Services 3.0 Nintex Workflow 2007

SUMMARY
This is a quick summary of the steps and procedures required to complete this example. 1. 2. 3. 4. 5. Create a custom Content Type Create a custom form Deploy the custom form Update content type to use the custom form Configure the workflow

RESOURCES
There is an example Visual Studio project in the Examples\CustomTaskForm folder. This contains a completed task form with the same look and feel as the out of the box task response form. It can be used as a base for modifications.

www.nintex.com

Page 44 of 235 [email protected]

connect.nintex.com

Software Development Kit v1.2

STEPS AND PROCEDURES
Procedure 1 Create a custom Content Type Content types can be created through the SharePoint user interface. When creating a custom content type, an existing content type can be chosen as a base. In this case, the Nintex Workflow Task content type must be used. To create a content type, follow these steps: 1. 2. Open the Site Settings page of the team site that will contain the workflow. Open the Site content types page under the Galleries section.

3. 4. 5. 6.

Select the "Create button at the top of the existing content types list. Enter a name and description of the content type. Under Parent Content Type, select Nintex Workflow for the group and Nintex Workflow Task for the parent content type. Press Ok to complete creating the content type.

www.nintex.com

Page 45 of 235 [email protected]

connect.nintex.com

Software Development Kit v1.2

Procedure 2 Create a custom form 1. Basic task approval To respond to a task and continue the workflow, the page code must open the task item and set certain values to signify that the task has been completed. The edit form for a task is provided with the following query string information: Query string parameter List ID Source Description The GUID of the task list. The integer item ID of the task. The URL that the user has come from. May not exist.

This information is used to open the task item, as shown in the following code: C# int spTaskItemID = int.Parse(Page.Request.QueryString["ID"]); Guid taskListId = new Guid(Page.Request.QueryString["List"]); SPListCollection lists = SPContext.Current.Web.Lists; lists.ListsForCurrentUser = true; SPList taskList = lists.GetList(taskListId, false); SPListItem spTask = taskList.GetItemById(spTaskItemID);

To respond to a task, set the decision and comments fields. These fields are a part of the base Nintex workflow task content type: C# int decision = 0; string comments = ""; Guid commentsFieldId = new Guid("{819E6CF2-36C3-4013-8AEF-C99712C26036}"); Guid decisionFieldId = new Guid("{A7AE99D0-E5DF-47f4-9D75-560E3F608006}"); spTask[decisionFieldId] = decision; spTask[commentsFieldId] = comments; spTask.Update();

If you have a reference to Nintex.Workflow.dll, the field id GUIDs are defined in constants found at:

www.nintex.com

Page 46 of 235 [email protected]

connect.nintex.com

Software Development Kit v1.2

C# Nintex.Workflow.Common.NWSharePointObjects.FieldComments Nintex.Workflow.Common.NWSharePointObjects.FieldDecision

The valid values for the decision are: Outcome Approved Rejected Continue (for review tasks) Value 0 1 5

These are defined in the enumeration Nintex.Workflow.HumanApproval.Outcome 2. The NintexTask class Further functionality can be gained by adding reference to the assembly Nintex.Workflow.dll. The class Nintex.Workflow.HumanApproval.NintexTask stores information about the approval or review task of which the actual SharePoint task item is a part. The following code retrieves the NintexTask object that corresponds to the SharePoint task item. C# NintexTask task = NintexTask.RetrieveTask(spTaskItemID, SPContext.Current.Web, taskList);

The task can either be an ApprovalTask or a ReviewTask object which both inherit from NintexTask. These objects contain information about the workflow, the item that the workflow is running on and all the users that have been designated as approvers/reviewers.

The ItemProperties server control The Nintex.Workflow.ServerControls.dll contains an ItemProperties server control. This server control renders all the properties of the workflow item, respecting the View specified in Central Administration. With an ItemProperties control on the aspx page, it can be set up with the following code: C# SPList list = lists.GetList(task.WFContext.ListID); SPListItem item = list.GetItemById(task.WFContext.ItemID) itemProperties.Item = item; itemProperties.InstanceID = task.WFContext.InstanceID;

www.nintex.com

Page 47 of 235 [email protected]

connect.nintex.com

Software Development Kit v1.2

Procedure 3 Deploy the custom form Custom aspx web forms are deployed to C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\TEMPLATE\LAYOUTS. A subfolder should be created in the layouts directory for any custom web forms. The compiled assembly should be deployed into the Global Assembly Cache. Repeat this on every front end server. Alternatively, create a SharePoint solution to manage the deployment and retraction of the custom development. See Solution Overview at MSDN for more information http://msdn2.microsoft.com/en-us/library/aa543214.aspx.

Page 53 of 235 [email protected]

connect.nintex.com

Software Development Kit v1.2

HOW TO: EXPORT WORKFLOW HISTORY SKILL LEVEL: INTERMEDIATE OVERVIEW
This example demonstrates the process of calling the Nintex Workflow web service to retrieve the workflow history for the current item in the workflow and saves the output to a field on the current list item. Although this example has been built using Nintex Workflow actions, the underlining principles can be applied to a custom developed solution.

REQUIREMENTS
This example requires the following technologies and/or applications: Windows SharePoint Services 3.0 Nintex Workflow 2007 Compatible XSLT editor

SUMMARY
This is a quick summary of the steps and procedures required to complete this example. 1. 2. Preparation Build Workflow

SUPPLIED EXAMPLES
This example contains two Xslt files. Each transforms the Xml returned from the Nintex Workflow web service and formats it into user friendly text. The first file outputs plain text to be used when writing to a plain text column in SharePoint, the second file outputs to a rich text Html column. Files 1. 2. {SDK Location}\Examples\ExportWorkflowHistory\HistoryExportPlain.xsl {SDK Location}\Examples\ExportWorkflowHistory\HistoryExportRich.xsl

STEPS AND PROCEDURES

Procedure 1 Preparation This example will collect the current workflows history and store the output in a column for the current item. You will need to create a column of type text (either plain or rich text) in your sample list/library. The following steps adds a History column to Shared Documents.

www.nintex.com

Page 54 of 235 [email protected]

connect.nintex.com

Software Development Kit v1.2

Procedure 2 Build Workflow 1. 2. 3. 4. 5. 6. 7. Create a new team site and enable Nintex Workflow. Navigate to the Shared Documents library. From the Settings link on the toobal click Create a Column. Type History in the Column name field. Select Multiple lines of text as the type of column. Select Allow unlimited length in document libraries. Click OK.

8. From the Settings link on the toolbar click Create Workflow. 9. In the workflow designer add a Log in the history list action to the blank workflow. 10. Configure the action and enter This is a Nintex Workflow SDK example, then click Save. 11. Next add a Delay for action under. 12. Configure the action and enter 1 into the minute field, then click OK. 13. From the toolbar click Settings -> Workflow Variables. 14. Type workflowHistory in the Name field. 15. Select Text as the variable type, and click Create and then Save.

Figure: Workflow varibable workflowHistory. 16. Add a Call web service action (in the integration category). 17. Configure the call web service action: a. Set the URL to {Common:WebUrl}/_vti_bin/nintexworkflow/workflow.asmx, b. Set the credentials. c. Click the refresh button next to the web method and you will be prompted to confirm the url. Once confirmed, this will contact the web service and retrieve all the available methods. d. Select GetWorkflowHistory as the web method.

www.nintex.com

Page 55 of 235 [email protected]

connect.nintex.com

Software Development Kit v1.2

e. Click Edit SOAP and populate the parameters, for an easy example you can use the following values to collect the current workflow history i. fileUrl = {Common:ItemUrl} ii. stateFilter = Running iii. workflowNameFilter = {Common:WorkflowTitle} Nintex Workflow Web Service SOAP <?xml version="1.0" encoding="utf-8"?> <soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Body> <GetWorkflowHistory xmlns="http://nintex.com"> <fileUrl>{Common:ItemUrl}</fileUrl> <stateFilter>Running</stateFilter> <workflowNameFilter>{Common:WorkflowTitle}</workflow NameFilter> </GetWorkflowHistory> </soap:Body> </soap:Envelope>

www.nintex.com

Page 64 of 235 [email protected]

connect.nintex.com

Software Development Kit v1.2

7. Define Orchestration. Define the elements that make up the flow of your orchestration. Refer to the BizTalk Server 2006 documentation for more information on designing orchestrations. The requirement for Nintex Workflow is that the 'LocationId' andMessageId elements in the header of both the send and receive message are bound to each other. Nintex Workflow uses these identifiers to determine which workflow a message is intended for.

You will also need an active receive message action and a send message action to be hooked up to the ports. The message content data that is required in your orchestration must be promoted.

www.nintex.com

Page 65 of 235 [email protected]

connect.nintex.com

Software Development Kit v1.2

Deploy the application. Sign the application assembly, define a name for the application and deploy it to your BizTalk server.

Procedure 3 Publish the Orchestration web service 1. Star the BizTalk Web Services Publishing Wizard.

Note: the web services publishing wizard is only available on machines that have Visual Studio installed.

www.nintex.com

Procedure 4 Configure the application in BizTalk Server Administration 1. Finish configuring the web service receive location. In the Receive Locations view, the generate location will be listed. If you already had the application open, you may need to refresh it.

Configure the properties of the location and change the Receive Pipeline drop down to XMLReceive. This is required for the BizTalk engine to be able to read the xml to determine what time of message it has received.

Enable the port. 2. Configure a send port. Nintex Workflow exposes a http handler to receive messages from BizTalk as post data. Create a new send port and specify HTTP as its type.

www.nintex.com

Page 69 of 235 [email protected]

connect.nintex.com

Software Development Kit v1.2

Choose the Configure button to set the properties of the port. The url should be http://<SharePoint server>/_layouts/nintexworkflow/BiztalkHandler.ashx. Note that this url will handle workflows across the entire farm. Site context in the url is not required. Enter proxy and authentication as required for your environment.

Enable the send port. 3. Bind ports to the orchestration. Select the orchestration from the orchestrations section

Set the correct host and the physical ports that have been defined in this section for the orchestrations logical ports.

Start the Orchestration.

www.nintex.com

Page 70 of 235 [email protected]

connect.nintex.com

Software Development Kit v1.2

Procedure 5 Complete the workflow configuration 1. Configure the Send / Receive BizTalk action Open the saved workflow in Nintex Workflow 2007 and open the configuration screen for the Send/Receive BizTalk action. In the BizTalk Web Service Endpoint Settings panel enter the details of the web service that was published in step 3.

Save the action. 2. Use the data. The variable created to hold the data will be populated after the BizTalk action has been completed and can be used in the same way as any other piece of workflow data. For example, if can be used in the body of an email.

www.nintex.com

Page 71 of 235 [email protected]

connect.nintex.com

Software Development Kit v1.2

HOW TO: RE-BRAND NINTEX WORKFLOW SKILL LEVEL: BEGINNER/ADVANCED OVERVIEW
This guide will explain the different areas of Nintex Workflow where re-banding can be considered to integrate into a custom design solution. This example is supplied with a sample solution to demonstrate the coding section referenced Procedure 2. To run the sample application load the solution and build the project, documentation is provided as inline XML comments.

REQUIREMENTS
This example requires the following technologies and/or applications: Windows SharePoint Services 3.0 Nintex Workflow 2007 Compatible CSS editor Visual Studio 2003/2005/2008 (optional) Microsoft Internet Explorer Developer Toolbar (option)

SUMMARY
This is a quick summary of the steps and procedures required to complete this example. 1. 2. 3. Creation of CSS Message template branding Configure SharePoint to use new styling.

SUPPLIED EXAMPLES
This example contains a Visual Studio 2005 solution for a sample console application which set a webs alternate CSS URL. Solutions 1. {SDK Location}\Examples\AltCssApp

STEPS AND PROCEDURES

Procedure 1 Creation of CSS The first step in re-branding Nintex Workflow is to re-brand SharePoint. Nintex Workflow has been design to inherit most of its style classes directly from SharePoint meaning that when a site is branded the Nintex Workflow designer should automatically inherit the new branding. Note that the configuration dialogs are using separate styles and will not inherit branding automatically. There may be instances where a new style sheet does not blend completely with Nintex Workflow, to help identify what CSS classes require changing you can use the Microsoft IE developer toolbar (http://www.microsoft.com/downloads/details.aspx?familyid=e59c3964-672d-4511-bb3e-2d5e1db91038) to analyze the applied styles to any element on a web page.

www.nintex.com

Page 72 of 235 [email protected]

connect.nintex.com

Software Development Kit v1.2

Once you have branded your SharePoint site you may find it necessary to override some of the custom Nintex Workflow CSS classes. Overriding our classes is performed in the same as with SharePoint. For more information on SharePoint branding see Cascading Style Sheets Class Definitions for Microsoft Windows SharePoint Services in the SharePoint SDK For more information on the features of the Microsoft IE developer toolbar and usage guides please see http://www.microsoft.com/ie. For more information on Cascading Style Sheets (CSS) please see http://www.w3.org/Style/CSS/.

Procedure 2 Message template branding Nintex Workflow uses a configurable messages template (a header and a footer) for all email notifications. There are different levels in which these templates can be controlled and customized: Farm level Site collection level Web level

Note: When an email message is sent by Nintex Workflow it will first check for a template at the teamsite level, if none is defined it will check the site collection level and if none is defined there, the farm template will be used. This give you a wide range of branding options for email messages. Messages templates for a teamsite and site collection are edited from the Site Settings panel on a teamsite. Farm level templates are defined in SharePoint Central Administration. Procedure 3 Configure SharePoint to use new styling There are two methods of branding SharePoint. The first is with a theme which can be very restricted in terms of management on a wide scale. We will be talking about the second option which uses the alternative CSS feature. This feature allows you to specify a single CSS file which will be included in all web pages in a team site (via the master page). The alternate CSS for a team site can be controlled by two methods. The first is only valid if you have Microsoft Office SharePoint Server 2007 (MOSS), and the second is via code which is required for Windows SharePoint Services 3.0 (WSS). Please see the below detailed steps for your environment. Please note that the WSS 3.0 method will work in a MOSS 2007 environment as well. Microsoft Office SharePoint Server 2007 Alternate CSS 1. 2. 3. 4. 5. 6. 7. 8. 9. Open your browser to your site collection root (top level site). Create a new library called Styles Upload you CSS file to this library. Browse to the team site requiring branding Browse to the site settings page. Under the heading Look and Feel click Master Page In the section Alternate CSS URL select Specify a CSS file to be used by this publishing site and all sites that inherit from it. Click the Browse button and browse to the location where you uploading your CSS file in step 3. Click OK to select the CSS file, and then click OK to save the changes.

Windows SharePoint Services - Alternate CSS

www.nintex.com

Page 73 of 235 [email protected]

connect.nintex.com

Software Development Kit v1.2

This method requires coding to the SharePoint object model to set the alterative CSS, as WSS 3.0 does not expose the setting via the UI. 1. 2. 3. 4. 5. 6. 7. Open your browser to your site collection root (top level site). Create a new library called Styles Upload you CSS file to this library. Load Visual Studio, and create a new C# Console Application. Add a reference to the Microsoft.SharePoint.dll Add a reference to the namespace Microsoft.SharePoint In the Program.cs class file enter the following code in the body of the main static method C# SPSite site = new SPSite(http://development.nintex.com); SPWeb web = site.OpenWeb(); web.AlternateCssUrl = http://development.nintex.com/Styles/custom.css; web.Update(); web.Close(); site.Close();

Compile and run the console application, your team site alternative CSS will be updated.

www.nintex.com

Page 74 of 235 [email protected]

connect.nintex.com

Software Development Kit v1.2

HOW TO: CREATE CUSTOM CONTEXT DATA ITEMS OVERVIEW
This section describes how to add additional items to the list of Common data items that can be inserted into the text used in various workflow actions.

Note: to add a static value that does not need code to generate, consider using a workflow constant.

REQUIREMENTS
Nintex Workflow build 10828 or greater allows the addition of custom data items.

STEP 1: CREATE A CUSTOM DATA ITEM CLASS

Custom data items are created by inheriting from a Nintex Workflow defined interface. 1. 2. Create a new Visual Studio project, and add references to Nintex.Workflow.dll and Microsoft.SharePoint.dll. Inherit a class from Nintex.Workflow.ICommonDataItem

Inherit from ICommonDataItem public class InitiatorEmailAddressDataItem : Nintex.Workflow.ICommonDataItem 3. Implement the DisplayName and InternalName properties. DisplayName is the value shown in the reference inserter dialog, while InternalName is the value stored when the value is inserted.

Implement Properties public string DisplayName { get { return "Initiator's Email Address"; } } public string InternalName { get { return "InitatorEmailAddress"; } }

Implement the GetValue method. This method is called at runtime to replace the token with an actual value. The method is passed a context object containing information about the workflow that is running. This example returns the email address of the user that initated the workflow

www.nintex.com

Page 75 of 235 [email protected]

connect.nintex.com

Software Development Kit v1.2

Implement Method public string GetValue(Nintex.Workflow.INWContext ctx) { return ctx.WorkflowInitiator.Email; } 5. Sign and compile the assembly and then install it into the GAC.

STEP 2: REGISTER THE DATA ITEM

Once the assembly is created, it needs to be registed in Nintex Workflow. This is done with the NWAdmin tool. nwadmin.exe is located in the Nintex Workflow installation directory, by default this is [ProgramFiles]\Nintex\Nintex Workflow 2007. The command arguments: nwadmin.exe -o AddCustomDataItem -Type <namespace.typename of data item class> -Assembly <fully qualified assembly name> For the supplied example, the command might be: nwadmin.exe -o AddCustomDataItem -Type Nintex.Workflow.Addins.InitiatorEmailAddressDataItem -Assembly Nintex.Workflow.Addins.CustomDataItems, Version=1.0.0.0, Culture=neutral, PublicKeyToken=xxxxxxxxxxxxxxxx Preform an IISRESET to refresh the cached of installed data items. You can now use your data item in a workflow.

www.nintex.com

Page 76 of 235 [email protected]

connect.nintex.com

Software Development Kit v1.2

HOW TO: USE THE ERROR HANDLING PANEL OVERVIEW
This section describes how to use the error handling panel in a custom action. Code must be added to the activity, adapter and configuration dialog.

REQUIREMENTS
Nintex Workflow build 10828 or greater. Knowledge of creating a custom action for Nintex Workflow is assumed.

STEP 1: ADD CODE TO THE ACTIVITY CLASS

The following dependency properties are used on the activity to use the error handling settings. In this example, the activity class is called MyActivity. Register Dependency Properties public static DependencyProperty CaptureErrorsProperty = DependencyProperty.Register("CaptureErrors", typeof(bool), typeof(MyActivity)); public static DependencyProperty ErrorOccurredOutputProperty = DependencyProperty.Register("ErrorOccurredOutput", typeof(bool), typeof(MyActivity)); public static DependencyProperty ErrorMessageOutputProperty = DependencyProperty.Register("ErrorMessageOutput", typeof(string), typeof(MyActivity));

Implement Dependency Properties [ValidationOption(ValidationOption.Optional), Browsable(true), DesignerSerializationVisibility(DesignerSerializationVisibility.Visible)] public bool CaptureErrors { set { base.SetValue(CaptureErrorsProperty, value); }

www.nintex.com

Page 77 of 235 [email protected]

connect.nintex.com

Software Development Kit v1.2

Implement Dependency Properties get { return (bool)base.GetValue(CaptureErrorsProperty); } } [ValidationOption(ValidationOption.Optional), Browsable(true), DesignerSerializationVisibility(DesignerSerializationVisibility.Visible)] public bool ErrorOccurredOutput { set { base.SetValue(ErrorOccurredOutputProperty, value); } get { return (bool)base.GetValue(ErrorOccurredOutputProperty); } } [ValidationOption(ValidationOption.Optional), Browsable(true), DesignerSerializationVisibility(DesignerSerializationVisibility.Visible)] public string ErrorMessageOutput { set { base.SetValue(ErrorMessageOutputProperty, value); } get { return (string)base.GetValue(ErrorMessageOutputProperty); }

The following code demonstrates how to structure error handling within the activity execution to use the error handling options. Handle error in execution try { // do activity execution code if (CaptureErrors) ErrorOccurredOutput= false; return ActivityExecutionStatus.Closed; } catch (Exception ex) { if (CaptureErrors) { ErrorOccurredOutput = true; ErrorMessageOutput = ex.Message; return ActivityExecutionStatus.Closed; }

www.nintex.com

Page 78 of 235 [email protected]

Software Development Kit v1.2

Since we are calling a web service, we need to create network credentials to authenticate. The example code demonstrates 3 ways of doing this. One way is to setup a Nintex Workflow constant in central administration. You could also hard code a username and password but this is not recommended for obvious reasons. If neither of these methods are available, the code will fall back to using the System.Net.CredentialCache.DefaultNetworkCredentials. If you are using a Nintex credential constant for retrieving the username and password, update the class constant with constant name used in your environment. MakeCab.ddf This is the definition file for MakeCab.exe. There is a post build event on the project to call MakeCab.exe to produce the packaged WSP solution file. Manifest.xml This is the manifest file used in the SharePoint solution package. It refers to the feature and the assembly containing the SPFeatureReceiver class. This assembly must be strong named and installed to the GAC. myKen.snk Strong name key file. MyWorkflowFeature.wsp This file is created automatically by a post build event. This is the output WSP solution package.

DEPLOYMENT
To deploy this solution, copy the output WSP file to your SharePoint server. Using stsadm.exe you can install and deploy the solution package. Stsadm.exe -o addsolution -filename myworkflowfeature.wsp stsadm.exe -o deploysolution -name myworkflowfeature.wsp -immediate -allowgacdeployment

www.nintex.com

Page 83 of 235 [email protected]

connect.nintex.com

Software Development Kit v1.2

HOW TO: DEPLOY A CUSTOM WORKFLOW ACTION AS PART OF A SHAREPOINT SOLUTION PACKAGE (WSP) SKILL LEVEL: ADVANCED OVERVIEW
This section demonstrates how a custom workflow action could be deployed as a part of a SharePoint solution package.

REQUIREMENTS
This example requires the following technologies and/or applications: Windows SharePoint Services 3.0 Visual Studio 2008

SUMMARY
A SharePoint solution package is used to deploy the required files for the workflow action and a web application scoped feature is used to register the custom action with Nintex Workflow. An event receiver attached to the feature performs the steps required to add and activate the action with Nintex Workflow: 1. 2. 3. Register the action with Nintex Workflow Enable the action to be used in the workflow designer for the farm Add entries to the web.config file for the web application to authorize the activity class with SharePoint

A simple custom action that writes entries to the server application event log is used for this demonstration.

SUPPLIED EXAMPLES
This example contains a Visual Studio 2008 solution demonstrating using a SharePoint feature and solution package to deploy a custom workflow action. Solutions 2. {SDK Location}\Examples\DeployWorkflowAction

COMPONENTS
The following components make up the supplied example.

www.nintex.com

Page 84 of 235 [email protected]

connect.nintex.com

Software Development Kit v1.2

Custom Workflow Action To demonstrate installing a custom action, the project includes a very simple workflow action that writes to the SharePoint server event log. The following files are part of the action: Images\EventLogActionIcon.gif Images\EventLogActionIconSmall.gif Images\EventLogActionIconWarning.gif EventLogActionDialog.aspx EventLogActivity.cs EventLogAdapter.cs

For more information on creating a custom action see the chapters How To: Create a Custom Workflow Action Overview and How To: Create a Custom Workflow Action Step by Step Guide. Feature.xml This is a standard SharePoint feature definition. It is scoped to be activated on a web application. A SPFeatureReceiver class contains the code to install the action. The code is the equivalent of manually importing the nwa file and then activating the action for the entire farm. The feature also deploys an NWA file that contains the information about the action that Nintex Workflow requires. The unique identifiers highlighted in green should be regenerated for your feature and the sections highlighted in yellow should be updated to match your receiver assembly.
<Feature Id="{0A1558DE-676C-4615-9CC9-0F9E7D3BB799}" Title="Deploy Action Example" Description="An example feature used to deploy a custom workflow action" ReceiverAssembly = "CustomActions.EventLogAction, Version=1.0.0.0, Culture=neutral, PublicKeyToken=7fc72706a49c89a6" ReceiverClass = "CustomActions.DeployActionExample.ActionInstaller" Version="12.0.0.0" Scope="WebApplication" xmlns="http://schemas.microsoft.com/sharepoint/"

www.nintex.com

Page 85 of 235 [email protected]

connect.nintex.com

Software Development Kit v1.2

ImageUrl="$Resources:NWResource,SiteCollectionFeature_ImageUrl;" Hidden="FALSE" AlwaysForceInstall="TRUE" SolutionId="{125e9779-c7be-4b9e-901e-7e9b447a93ca}"> <ElementManifests> <ElementFile Location="EventLogAction.nwa" /> </ElementManifests> </Feature>

EventLogAction.nwa This is an xml file describing the components of the action. This file is read by the feature event receiver. ActionInstaller.cs This class file contains the SPFeatureReciever class used to register the custom action with Nintex Workflow. The feature activated and feature deactivated events are implemented. When the feature is activated for a web application, the workflow action will be visible in other web applications where the core Nintex Workflow feature has been activated. This is because registering a custom action in the Nintex Workflow database is a global operation. However, workflows using the custom action will not publish or run unless the feature is activated for the parent web application due to the dependency on an entry in the web.config file. When the feature is deactivated, it will remove the web.config entries for the web application. It will only remove the action from the workflow database if the feature is not activated on any other web application. DeployActionExample.wsp This file is created automatically by a post build event. This is the output WSP solution package. MakeCab.ddf This is the definition file for MakeCab.exe. There is a post build event on the project to call MakeCab.exe to produce the packaged WSP solution file. Manifest.xml This is the manifest file used in the SharePoint solution package. It refers to the feature and the assembly containing the SPFeatureReceiver class, as well as the individual content files that make up the custom action (images and aspx page). myKen.snk Strong name key file.

DEPLOYMENT
To deploy this solution, copy the output WSP file to your SharePoint server. Using stsadm.exe you can install and deploy the solution package. stsadm.exe -o addsolution -filename deployactionexample.wsp stsadm.exe -o deploysolution -name deployactionexample.wsp -immediate -allowgacdeployment

www.nintex.com

Page 86 of 235 [email protected]

connect.nintex.com

Software Development Kit v1.2

One the solution is deployed, there will be a new feature listed in the Manage Web Application Features page.

Once the feature is activated you will be able to use the action in the workflow designer.

www.nintex.com

Page 87 of 235 [email protected]

connect.nintex.com

Software Development Kit v1.2

HOW TO: CREATE AN INLINE FUNCTION OVERVIEW
This section describes how to add additional inline functions for workflow designers to use to manipulate workflow data.

REQUIREMENTS
Nintex Workflow build 10903 or greater.

CREATE AN INLINE FUNCTION

The requirements for a function to be used by Nintex Workflow are: It is a static method It accepts parameters that can be parsed from text It is contained in a type installed into the GAC on each web server

When the function is invoked, the workflow will dynamically determine the required parameters, and attempt to parse what was provided in the workflow in to the correct data type. Overloads can also be used, as the workflow will match the number of parameters provided to the appropriate overload definition.

ALIASES
A function is referred to by its alias. A function can have multiple aliases. Localization of function names is done by adding a new alias for each language.

REGISTER THE FUNCTION

The NWAdmin.exe tool is used to register the function with Nintex Workflow. See the NWAdmin.exe documentation for command details. The following commands relate to inline functions: AddInlineFunction registers an inline function with Nintex Workflow. EnumInlineFunctions displays all the functions registered in Nintex Workflow, including the out of the box functions. RemoveInlineFunction unregisters a function from Nintex Workflow.

www.nintex.com

Page 88 of 235 [email protected]

connect.nintex.com

Software Development Kit v1.2

STYLE GUIDE
Nintex workflow has been developed to integrate with the look and feel of your existing SharePoint team site, using the out of the box SharePoint styling classes. This has the advantage when branding a team site you are not required to develop custom styles class for Nintex Workflow. There is however a couple of places where Nintex Workflow has created its own styles to implement the required UI. The defined classes table below details the key classes used by Nintex Workflow. To override Nintex Workflow out of the box classes use the AlternateUrl property of the SPWeb object from within the SharePoint APIs, or from the team site setting page (under look and feel).

DEFINED CLASSES
Selector ms-menutoolbar Description Preview

ActivityLabel DropZone ActivityIcon

SmallActivityIcon

ms-quickLaunch

expanded

Defines the look of a workflow actions toolbar category in the expanded state. Defines the look of a workflow actions toolbar category in the collapsed state.

collapsed

ms-navheader divToolBoxActivity

www.nintex.com

Page 89 of 235 [email protected]

connect.nintex.com

Software Development Kit v1.2

Selector ToolboxItem Description Preview

ActionDetailsPane

Defines the overall UI to the both the actions details information and warning panes.

ActionDetailsInfoHeader

ActionDetailsWarningHeader

ActionDetailsBody

RowBlue

Defines an alternating row colour on the action configuration interface. Defines an alternating row colour on the action configuration interface. Defines a label used in the action configuration screen.

RowWhite

Label

expandme

closeme NWDesignTimeCanvas Applied to the area in which a workflow is designed. Applied to the area in which a workflow is displayed on the start workflow page and when viewing a workflow from the workflow gallery. Applied to the area in which a workflow instance (e.g. a workflow in progress) is displayed.

NWPreviewCanvas

NWRuntimeCanvas

www.nintex.com

Page 90 of 235 [email protected]

connect.nintex.com

Software Development Kit v1.2

Selector NWStatisticsCanvas Description Applied to the area in which a workflow is displayed in statistics view (Enterprise edition only). Applied to an action on the workflow designer. The style is applied to the table containing the whole action, the td containing the top label, and the tbody containing the icon. Applied to an action rendered in a workflow in the preview view. Applied to an action rendered in a workflow in the statistics view. Applied to an action rendered in a workflow instance view. This action has not yet run (colored grey). Applied to an action rendered in a workflow instance view. This action has completed (colored green). Applied to an action rendered in a workflow instance view. The workflow is currently waiting on this action (colored yellow). Applied to a request approval action that has been declined (colored red). Preview

NWDesignTimeAction

NWPreviewAction

NWStatisticsAction

NWRuntimeFutureAction

NWRuntimePastAction

NWRuntimePresentAction

NWRuntimeActionOverrideRed

NINTEX WORKFLOW CASCADING STYLE SHEETS ON THE FILE SYSTEM

Name Dialogue Location C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\LAYOUTS\NINTEXWORKFLOW\dialogue.css C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\LAYOUTS\NINTEXWORKFLOW\SLStyles.css

SLStyles

These stylesheets can be added using the Nintex.Workflow.ServerControls.CssLink control.

www.nintex.com

Page 91 of 235 [email protected]

connect.nintex.com

Software Development Kit v1.2

MASTER PAGES
Nintex Workflow contains a single custom master page, used in the actions configuration dialog. All other pages in Nintex Workflow use the default master page associated with the site. The master page associated with the actions dialog window is located at C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\LAYOUTS\NINTEXWORKFLOW\ActivityUIMasterPage.master.

The following table describes the content placeholders contained in the ActivityUIMasterPage.

CONTENT PLACEHOLDERS DEFINED IN ACTIVITYUIMASTERPAGE.MASTER

Name of Content Placeholder AdditionalPageHeader Description Additional content that needs to be within the <head> tag of the page, for example, references to script in style sheets The location for the icon of the action The title of the action The main body of the dialog Save button Cancel button

IconPlaceHolder TitlePlaceHolder NintexPropertyPlaceHolder SaveButtonPlaceHolder CancelButtonPlaceHolder

Tip: The ActivityUIMasterPage contains the required logic to integrate with the SharePoint help system. To override the default help page insert the following JavaScript, and replace helpItem with your own help index key. JavaScript var navBarHelpOverrideKey = 'helpItem';

For more information on developing and integrating into the SharePoint help system see http://www.codeproject.com/KB/sharepoint/CustomHelpPages_SP2007.aspx

www.nintex.com

Page 92 of 235 [email protected]

connect.nintex.com

Software Development Kit v1.2

WEB CONTROLS REFERENCE
This section of the Nintex Workflow Software Development Kit (SDK) includes information about the controls available for use in custom action dialogs and other custom pages that can interact with Nintex Workflow. Please note that most server controls assume they are running in a SharePoint context, and expect SPContext.Current to be populated.

CREDENTIALS CONTROL
This control is used on action configuration dialogs to allow users to specify credentials. Users can either directly enter credentials, or select from credentials that have been defined in site settings. Nintex.Workflow.ApplicationPages.CredentialControl

PROPERTIES
Name CssClass Description Gets or sets the style sheet for the control text controls embedded in the control. Gets or sets the style sheet for the div element that the text controls are embedded in. Gets or sets display value for the control, possible values are normal or dialog. Use dialog when the control is being used on a action configuration dialog. Gets a Boolean value that specifies if control is using predefined credentials. Gets a string containing the password. Gets a integer that identifies the predefined credentials. Gets or sets whether to display a red asterisks to indicate the control is a required field. Gets a string containing the username. Get or set the width of the rendered field controls.

DialogContainerClass

DisplayMode

IsUsingPredefinedCredential

Password PredefinedCredentialID RequiredField

Username Width

METHODS
Name IsEmpty Description

SYNTAX
ASP.Net (Usage)

www.nintex.com

Page 93 of 235 [email protected]

connect.nintex.com

Software Development Kit v1.2

ASP.Net (Usage) <%@ Register TagPrefix="NWC" TagName="CredentialControl" Src="~/_layouts/NintexWorkflow/CredentialControl.ascx" %> <NWC:CredentialControl DisplayMode="dialog" CssClass="ms-input" Width="170px" runat="server" id="credentialPicker"></NWC:CredentialControl>

JavaScript (Usage) // Set username value cc_setUsername(credentialPickerClientId, username); // Set password value cc_setPassword(credentialPickerClientId, password); // Retrieve username value var username = cc_getUsername(credentialPickerClientId); // Retrieve password value var password = cc_getPassword(credentialPickerClientId);

PREVIEW

REMARKS
For the correct styles to be applied to the rendered control, use a Nintex.Workflow.ServerControls.CssLink control and the Microsoft.SharePoint.WebControls.CssLink control on the page. When a predefined credential has been selected, the cc_getPassword will return an empty string and cc_getUsername will return a string representing the credential in the format {WorkflowConstants:credentialName}. This token is recognized when resolving the credentials at runtime with Nintex.Workflow.CredentialValue.DetermineRuntimeCredentials(). The following example demonstrates resolving credentials from within a workflow activity. The activity class has a string property for Username and a string property for Password. If the Username property contains a predefined credential token, the matching username and password will be returned. If Username does not contain a token, runtimeUsername and runtimePassword will contain the same values as entered by the user. C# (Determining runtime credentials) string runtimeUsername = string.Empty; string runtimePassword = string.Empty; Nintex.Workflow.CredentialValue.DetermineRuntimeCredentials(this.Username,

www.nintex.com

Page 94 of 235 [email protected]

connect.nintex.com

Software Development Kit v1.2

C# (Determining runtime credentials) this.Password, out runtimeUsername, out runtimePassword, webId, siteId);

CSS LINK
This control is used to add the style sheets associated with Nintex Workflow to a page. Add it to the <head> element of a web page. Nintex.Workflow.ServerControls.CssLink

SYNTAX
ASP.Net (Usage) <%@ Register Assembly="Nintex.Workflow.ServerControls, Version=1.0.0.0, Culture=neutral, PublicKeyToken=913f6bae0ca5ae12" Namespace="Nintex.Workflow.ServerControls" TagPrefix="NWC" %> <NWC:CssLink id="cssLink1" runat="server"></NWC:CssLink>

DURATION SELECTOR
This control is used on action configuration dialogs to allow a duration value to be selected. The value is represented as the total minutes. Nintex.Workflow.ServerControls.DurationSelector

SYNTAX
ASP.Net (Usage) <%@ Register Assembly="Nintex.Workflow.ServerControls, Version=1.0.0.0, Culture=neutral, PublicKeyToken=913f6bae0ca5ae12" Namespace="Nintex.Workflow.ServerControls" TagPrefix="NWC" %> <NWC:DurationSelector ID="DurationSelector1" runat="server" />

JavaScript (Usage) // Get value

var value = GetDurationValue();

// Set value InitDurationSelector(parameters[5].childNodes[0].getAttribute(iTotalMinutes));

www.nintex.com

Page 95 of 235 [email protected]

connect.nintex.com

Software Development Kit v1.2

PREVIEW

REMARKS
Only one instance of this control can be included on a page. The position of the selector div can be overridden by including a JavaScript function called SetDurationPickerPosition that has one parameter representing the div object. The following example demonstrates how the default position is set: JavaScript (Setting the selector position) function SetDurationPickerPosition(oDiv){ var windowWidth = document.body.offsetWidth; var windowHeight = document.body.offsetHeight; var widthOfDiv = parseInt(oDiv.style.width); var heightOfDiv = parseInt(oDiv.style.height); var leftPos = (windowWidth - widthOfDiv) / 2; var topPos = (windowHeight - heightOfDiv) / 2; oDiv.style.left = leftPos + "px"; oDiv.style.top = topPos + "px"; }

ITEMPROPERTIES
This control displays properties for an item. Nintex.Workflow.ServerControls.ItemProperties

PROPERTIES
Name InstanceID Description Gets or sets the instance ID of the workflow that the item properties are being displayed for. If the InstanceID is not set, the workflow preview link will not display. Gets or sets the list item to display properties for. Gets or sets the source parameter to add to the url for the item the workflow is running on. Only applies for a list item, not a library item. Default is blank. Gets or sets the target attribute to add to the hyperlink that opens the item the workflow is running on. Default is _blank.

Item ItemLinkSource

ItemLinkTarget

www.nintex.com

Page 96 of 235 [email protected]

connect.nintex.com

Software Development Kit v1.2

Name HideEmptyFields Description Gets or sets whether to display fields that are empty or skip them. Default is false. Gets or sets the value to separate values in a multiple lookup field. Default is <br />. Gets or sets whether or not to list attachments from the item the workflow is running on. Gets or sets whether or not to display a link to the item the workflow is running on. Gets or sets whether or not to display a link to the workflow status page.

MultipleLookupsSeparator

ShowAttachments

ShowWorkflowItemLink

ShowWorkflowStatusLink

SYNTAX
ASP.Net (Usage) <%@ Register Assembly="Nintex.Workflow.ServerControls, Version=1.0.0.0, Culture=neutral, PublicKeyToken=913f6bae0ca5ae12" Namespace="Nintex.Workflow.ServerControls" TagPrefix="NWC" %> <NWC:ItemProperties ID="itemProperties" runat="server"></NWC:ItemProperties>

REMARKS
If the list has a view that has the same name as Task form properties view option in the Nintex Workflow Global Settings then only properties included in that view will be displayed.

PLAIN TEXT WEB CONTROL

This control is used on action configuration dialogs to capture text from the client in plain text format. It allows use of reference lookups which are replaced at runtime by the Nintex Workflow engine. Lookup categories include common, item properties, workflow variables and workflow constants. Nintex.Workflow.ApplicationPages.PlainTextWebControl

PROPERTIES
Name ApproverContext Description Gets or sets whether to include approver specific context items. This member is reserved for internal use; This value should be left as False. Gets or sets whether to list workflow constants that have been marked as sensitive to be listed in the possible references. The workflow action must also allow the user of sensitive constants for them to be successfully resolved. Gets or sets the style sheet for the control.

IncludeSensitiveWFConstants

CssClass1

www.nintex.com

Page 97 of 235 [email protected]

connect.nintex.com

Software Development Kit v1.2

Name TextAreaCols TextAreaRows Width Description Gets of sets the columns for the control. Gets of sets the rows for the control. Get or set the width of the rendered field controls.

SYNTAX
ASP.Net (Usage) <%@ Register TagPrefix="NWC" TagName="PlainText" Src="~/_layouts/NintexWorkflow/PlainTextWebControl.ascx" %> <NWC:PlainText cssClass1="ms-input" runat="server" id="plainText1" width="100%" ></NWC:PlainText>

JavaScript (Usage) // Set value setPlainTextEditorText(textInserterClientId, value); // Retrieve value var value = getStringFromPlainTextEditor(textInserterClientId);

PREVIEW

REMARKS
Workflow variables will only be listed in a workflow configuration dialog. They are obtained from the dialogArgs object that is passed into the configuration dialog by the workflow designer. Item properties will only be displayed if a QueryString value called ListId is present. ListId must contain the ID of the list to display properties from.

REFERENCE TEXT FIELD WEB CONTROL

This control provides a single line text input that includes a button to insert workflow context references. It is intended for use on action configuration dialogs.

www.nintex.com

Page 98 of 235 [email protected]

connect.nintex.com

Software Development Kit v1.2

Nintex.Workflow.ApplicationPages.ReferenceTextFieldWebControl

PROPERTIES
Name ApproverContext Description Gets or sets whether to include approver specific context items. This member is reserved for internal use; This value should be left as False. Gets or sets a value to specify if the reference selecting dialog will clear any existing values in the text box when a value is inserted. Gets or sets the type of LDAP browsing window to display open, possible values are HomeServer, LDAP or MailStore. The ShowLdapPickerButton property must be set to true for the LDAP browse button to display. Gets or sets a value to filter the values displayed in the reference selector dialog by SharePoint type. Leave blank to display all items.

ClearFieldOnInsert

DialogToOpen

Filter

Height IncludeSensitiveWFConstants Gets or sets whether to list workflow constants that have been marked as sensitive to be listed in the possible references. The workflow action must also allow the user of sensitive constants for them to be successfully resolved. Gets the value of the control. Gets or sets the display status of the LDAP picker button, defaults to False. Get or set the width of the rendered field controls.

PlainText ShowLdapPickerButton

Width

SYNTAX
ASP.Net (Usage) <%@ Register TagPrefix="NWC" TagName="ReferenceTextField" Src="~/_layouts/NintexWorkflow/ReferenceTextFieldWebControl.ascx" %> <NWC:ReferenceTextField runat="server" id="referenceTextField1"></ NWC:ReferenceTextField>

JavaScript (Usage) // Set value translateTextAndInsertIntoRefTextField(referenceTextFieldClientId, value); // Retrieve value var value = getStringFromRefTextField(referenceTextFieldClientId);

www.nintex.com

Page 99 of 235 [email protected]

connect.nintex.com

Software Development Kit v1.2

PREVIEW
With ShowLdapPickerButton set to False:

With ShowLdapPickerButton set to True:

RICH TEXT WEB CONTROL

This control is used on action configuration dialogs to capture text from the client in plain text or rich HTML format. It allows use of reference lookups which are replaced at runtime by the Nintex Workflow engine. The control can be configured to allow the client to select the text format or be forced to use a predefined format. Nintex.Workflow.ApplicationPages.RichTextWebControl

PROPERTIES
Name ApproverContext Description Gets or sets whether to include approver specific context items. This member is reserved for internal use; This value should be left as False.

HideInsertReferenceButtonInPlainTextMode HideModeChooser Gets or sets a Boolean that specifies whether to hide or show the mode selector. Default is False.

Height IncludeSensitiveWFConstants Gets or sets whether to list workflow constants that have been marked as sensitive to be listed in the possible references. The workflow action must also allow the user of sensitive constants for them to be successfully resolved. Gets or sets the text display before the mode selector Gets of sets a boolean value whether the control loads up in plain text mode. Default is False.

ModeSelectorText StartInPlainText

www.nintex.com

Page 100 of 235 [email protected]

connect.nintex.com

Software Development Kit v1.2

Name TextAreaCols TextAreaRows Width Description Gets of sets the columns for the control. Gets of sets the rows for the control. Get or set the width of the rendered field controls.

SYNTAX
ASP.Net (Usage) <%@ Register TagPrefix="NWC" TagName="RichText" Src="~/_layouts/NintexWorkflow/RichTextWebControl.ascx" %> <NWC:RichText runat="server" id="richTexWeb" ApproverContext="true" ModeSelectorText="Format"></NWC:RichText>

JavaScript (Usage) // Get value var value = rte_getText(richTextEditorClientId); // Set value rte_SetText(richTextEditorClientId, Value); // Set the size rte_setSize(richTextEditorClientId, width, height); // Toggle between plain text MODE_PLAINTEXT and rich text rte_setTextEditorMode(richTextEditorClientId, mode); // Get the mode var value = rte_getTextEditorMode(richTextEditorClientId);

MODE_RTE

PREVIEW

REMARKS
A script on the page must be set to run after all other processing to apply a size to the rich text editor.

www.nintex.com

Page 101 of 235 [email protected]

connect.nintex.com

Software Development Kit v1.2

JavaScript (Setting the size) <script language="javascript" event="onload" for="window"> rte_setSize("<%= richText1.ClientID %>", 500, 100); </script>

SCRIPT LINK
This control is used to add the JavaScript files associated with Nintex Workflow to a page. Add it to the <head> element of a web page. Nintex.Workflow.ServerControls.ScriptLink

SYNTAX
ASP.Net (Usage) <%@ Register Assembly="Nintex.Workflow.ServerControls, Version=1.0.0.0, Culture=neutral, PublicKeyToken=913f6bae0ca5ae12" Namespace="Nintex.Workflow.ServerControls" TagPrefix="NWC" %> <NWC:ScriptLink id="scriptLink1" runat="server"></NWC:ScriptLink>

USER CHOOSER WEB CONTROL

This control allows the selection of people and groups, as well as workflow context lookups. The UserChooserWebControl replaces the popup dialog for searching names, adding the ability to enter an external email address or workflow context reference. Nintex.Workflow.ApplicationPages.UserChooserWebControl

PROPERTIES
Name AllowEmpty Description (Inherited from Microsoft.SharePoint.WebControls.PeopleEditor) Gets or sets a Boolean that specifies if the panel for external email addresses is displayed. (Inherited from Microsoft.SharePoint.WebControls.PeopleEditor)

AllowExternalEmailAddresses

AllowTypeIn

www.nintex.com

Page 102 of 235 [email protected]

connect.nintex.com

Software Development Kit v1.2

Name IncludeSensitiveWFConstants Description Gets or sets whether to list workflow constants that have been marked as sensitive to be listed in the possible references. The workflow action must also allow the user of sensitive constants for them to be successfully resolved. (Inherited from Microsoft.SharePoint.WebControls.PeopleEditor) (Inherited from Microsoft.SharePoint.WebControls.PeopleEditor) (Inherited from Microsoft.SharePoint.WebControls.PeopleEditor) (Inherited from Microsoft.SharePoint.WebControls.PeopleEditor) (Inherited from Microsoft.SharePoint.WebControls.PeopleEditor) (Inherited from Microsoft.SharePoint.WebControls.PeopleEditor) (Inherited from Microsoft.SharePoint.WebControls.PeopleEditor) (Inherited from Microsoft.SharePoint.WebControls.PeopleEditor)

MultiSelect

PlaceButtonsUnderEntityEditor

Rows

SelectionSet

ShowCreateButtonInActiveDirectory AccountCreationMode ValidateResolvedEntity

ValidatorEnabled

Width

SYNTAX
ASP.Net (Usage) <%@ Register TagPrefix="NWC" TagName="UserChooser" Src="~/_layouts/NintexWorkflow/UserChooserWebControl.ascx" %> <NWC:UserChooser id="userChooser" ShowCreateButtonInActiveDirectoryAccountCreationMode="false" runat="server"></NWC:UserChooser>

JavaScript (Usage) // Set the value. The value can be a semi colon delimitated string setPeopleEditorDisplayText(peopleEditorClientID, value); // returns a semi colon delimitated string of users var value = getUsersFromPeopleEditor(peopleEditorClientID); // Get the a reference to the people editor control getPeopleEditor(peopleEditorClientID); // Returns a collection of data for every entry in the box

www.nintex.com

Page 103 of 235 [email protected]

connect.nintex.com

Software Development Kit v1.2

JavaScript (Usage) var oValue = GetPeopleDataCollection(peopleEditorObject); // Returns data of a specific login name that is selected in the people editor var oValue = GetPersonDataCollection(peopleEditorObject, loginName); // Attempt to resolve the values entered in the input box peopleEditorCheckNames(peopleEditorClientID);

PREVIEW

REMARKS
Workflow variables will only be listed in a workflow configuration dialog. They are obtained from the dialogArgs object that is passed into the configuration dialog by the workflow designer.

www.nintex.com

Page 104 of 235 [email protected]

connect.nintex.com

Software Development Kit v1.2

Item properties will only be displayed if a QueryString value called ListId is present. ListId must contain the ID of the list to display properties from. The JavaScript function GetPersonDataCollection returns an associative array of user details. GetPeopleDataCollection returns an array of associative arrays of user details. Valid keys in the associative array are SPUserID Email DisplayName Department SIPAddress Title PrincipalType Username

When using this control on a configuration dialog, setting the value must be done in an event attached to page load. JavaScript (Setting the value in a dialog) var setValue = function() { setPeopleEditorDisplayText("<%= userChooser.ClientID %>", value); } window.attachEvent("onload", setValue);

WORKFLOW VISUALISER
This control renders a workflow. Nintex.Workflow.ServerControls.WorkflowVisualiser

PROPERTIES
Name ButtonToDisable Description Gets or sets the client id of a button to disable if there are warnings regarding starting the workflow. ShowWarnings must be set to True. Gets or sets the instance id of a workflow instance to render. Required when RenderStyle is Runtime. Gets or sets the ID of the list that the workflow to display is associated with. Required when RenderStyle is Statistics or Preview.

InstanceId

ListId

www.nintex.com

Page 105 of 235 [email protected]

connect.nintex.com

Software Development Kit v1.2

Name RenderStyle Description Gets or sets a value determining the mode to display the workflow in. Options are Preview, Runtime or Statistics. The default is Preview. Statistics can be used in enterprise licenses only. DesignTime is treated as Preview. Gets or sets a value determining whether to display mouse-over popups displaying summary information. Use in conjunction with CssLink and ScriptLink. Gets or sets a Boolean value that specifies whether the published version of the workflow is displayed, or the latest saved version. Gets or sets a Boolean value that specifies whether to display any warnings detected in the workflow. Gets or sets a WorkflowStatistics object to render. Required when RenderStyle is Statistics. Gets or sets the base association ID of the workflow to render. Gets or sets the name of the workflow to render.

ShowMouseOverPopups

ShowPublishedVersion

ShowWarnings

Statistics

WorkflowId

WorkflowName

SYNTAX
ASP.Net (Usage) <%@ Register Assembly="Nintex.Workflow.ServerControls, Version=1.0.0.0, Culture=neutral, PublicKeyToken=913f6bae0ca5ae12" Namespace="Nintex.Workflow.ServerControls" TagPrefix="NWC" %> <NWC:WorkflowVisualiser ID="WorkflowView" runat="server" Height="100%" Width="100%" />

APPROVALTASK
Represents an assigned workflow task that requests approval. Inheritance Hierarchy: Nintex.Workflow.HumanApproval.NintexTask

PROPERTIES
Name ApprovalBehaviour Description Gets or sets the Nintex.Workflow.HumanApproval.ApprovalType for this task. Gets or sets a string supporting the ApprovalBehaviour. Will contain a number representing the required approval responses for a Vote ApprovalBehaviour.

ApprovalBehaviourData

METHODS
Name ApprovalTask Description Constructor. Use NintexTask.RetrieveTask to obtain an instance of ApprovalTask. Cancels a task that is currently running. Registers a response to the task.

CancelApprovalTask ProcessResponse

REMARKS
An instance of an approval task can be retrieved us

www.nintex.com

Page 113 of 235 [email protected]

connect.nintex.com

Software Development Kit v1.2

APPROVALTYPE ENUMERATION
Represents the behavior of a task regarding the number of users that must respond.

MEMBERS
Member name AllMustApprove FirstToRespond AnyApprove Vote Description Every response must approve. The first responder determines the outcome. If any approve is registered, the task is approved. A specified number of positive responses are required. ApprovalTask.ApprovalBehaviourData contains the required number.

www.nintex.com

Page 114 of 235 [email protected]

connect.nintex.com

Software Development Kit v1.2

APPROVER
Represents a task assignee. Inheritance Hierarchy: Nintex.Workflow.HumanApproval.User

PROPERTIES
Name AllowDelegation Description Gets or sets a value that determines if this approver is allowed to delegate the task. Gets or sets the Message that will be sent if the approver no longer needs to respond to a task. Gets or sets the Nintex.Workflow.HumanApproval.Outcome that has been registered by the user. If no response has been registered, the value will be Pending. The ID of this approver. Corresponds to an ID stored in the database. Gets or sets the comments the approver registered with this task. Gets the time that the task was assigned to the approver. Gets the time that the approver completed the task. The Nintex.Workflow.HumanApproval.NintexTask that this approver has been assigned to. Gets or sets the Message that will be sent if to the approver when the task is assigned. Gets the ID of the SPListItem task that this approver must complete.

ApprovalNoLongerRquiredMessage

ApprovalOutcome

ApproverID

Comments EntryTime ExitTime ParentTask

RequestApprovalMessage

SPTaskId

METHODS
Name Approver FlagTaskAsHidden Description Creates an Approver and assigns them to the parentTask. Hides the specified task for the user from the My Workflow Tasks webpart. Commits property changes to the database. Optionally updates the SPListItem task with the Comments and ApprovalOutcome.

Update

REMARKS
The term Approver also refers to users assigned to Review tasks.

www.nintex.com

Page 115 of 235 [email protected]

connect.nintex.com

Software Development Kit v1.2

USERCONFIG
An object for storing limited details about a user. Used for assigning data to an Activity object. Inheritance Hierarchy: System.Object

PROPERTIES
Name DisplayName OtherEmailAddress PrincipalType User Description

www.nintex.com

Page 116 of 235 [email protected]

connect.nintex.com

Software Development Kit v1.2

APPROVERCONFIG
An object for storing limited details about an approved. Used for assigning data to an Activity object. Inheritance Hierarchy: Nintex.Workflow.HumanApproval.UserConfig

PROPERTIES
Name AllowDelegation AllowLazyApprove ApprovalNotRequiredMessage ApprovalRequiredMessage IsCustom Description

METHODS
Name Copy ToNWApprover Description

www.nintex.com

Page 117 of 235 [email protected]

connect.nintex.com

Software Development Kit v1.2

DELEGATION
Represents a delegation rule detailing a period where tasks assigned to a user are automatically delegated to another. Also handles delegating tasks to other users. Inheritance Hierarchy: System.Object

PROPERTIES
Name DelegateUsername Description Gets or sets the login name of the user who will have tasks delegated to them. Gets the ID of the delegation record. Corresponds to an ID stored in the database. Gets or sets the date and time when the delegation rule will no longer apply. Gets or sets a formatted string representation of EndDate. Gets a string representing the scope of the delegation rule. Gets or sets the ID of the site collection containing the teamsite that the delegation rule applies to. Set to Guid.Empty for a global rule. Gets or sets the date and time from which the delegation rule will apply. Gets a formatted string representation of StartDate. Gets or sets the login name of the user who set up the delegation rule. Gets or sets the ID of the teamsite this delegation rule applies to. Set to Guid.Empty for a global rule.

DelegationID

EndDate

EndDateDisplay Scope SiteID

StartDate

StartDateDisplay Username

WebID

METHODS
Name DelegateApprovalTask Delegation Description Delegates an Approver to another user. Constructor. Creates a new delegation rule. Update must be called to persist the new rule. Deletes the delegation rule. Searches delegation rules for a login name and returns a delegate login name if a rule has been set up for the current time. Returns null if no delegate is found. Persists the property values to the database.

Delete FindDelegate

Update

www.nintex.com

Page 118 of 235 [email protected]

connect.nintex.com

Software Development Kit v1.2

www.nintex.com

Page 119 of 235 [email protected]

connect.nintex.com

Software Development Kit v1.2

DELEGATIONHISTORY
Represents a record of a delegation of a task from one user to another. Inheritance Hierarchy: System.Object

PROPERTIES
Name ApproverID Comment Description Gets the ApproverID that the delegation applied to. Gets a string of comments that were entered to explain the delegation. Gets the login name of the user whom the task was delegated to. Gets the login name of the user who delegated the task.

DelegateUsername Username

www.nintex.com

Page 120 of 235 [email protected]

connect.nintex.com

Software Development Kit v1.2

DELIVERYMECHANISM ENUMERATION
Represents the preferred format of message delivery.

MEMBERS
Member name None Email SMS IM UserPreference Description

www.nintex.com

Page 121 of 235 [email protected]

connect.nintex.com

Software Development Kit v1.2

MESSAGE
Represents a notification that is sent to a user. Inheritance Hierarchy: System.Object

PROPERTIES
Name AllowLazyApprove Description Gets or sets a value indicating whether the message is LazyApproval enabled. Gets or sets a value indicating if the workflow item should be attached to the message. Gets or sets the text of the notification body. Gets or sets a collection of users to include as CC recipients. Gets or sets a value indicating the mode of delivery. Gets or sets the user from whom the message should be sent from. Gets or sets a value indicating if the message is in HTML format. Gets or sets the subject of the notification.

AttachFile

Body CcList DeliveryType From

IsHtmlMessage Subject

METHODS
Name Copy DecodeForLazyApproval DeSerialize Send Serialize Sends a message. Interprets a subject for a LazyApproval token. Description

www.nintex.com

Page 122 of 235 [email protected]

connect.nintex.com

Software Development Kit v1.2

NINTEXTASK
Represents a workflow task that a user or group of users must respond to. Inheritance Hierarchy: System.Object

PROPERTIES
Name ApprovalStatus Approvers EntryTime ExitTime SequenceId Description Gets the Nintex.Workflow.HumanApproval.Outcome of the task. Gets the collection of users for the task. Gets the time and date that the task was created. Gets the time and date that the task was completed. Get a value that correlates the task to its position in the workflow. Gets the context of the workflow and task.

WFContext

METHODS
Name GetPendingApprover Description Returns an Approver object from a User and a SharePoint task item ID. Retrieves an SPListItem from a task list. Returns the NintexTask that is associated with a SPListItem task.

RetrieveSPListItem RetrieveTask

www.nintex.com

Page 123 of 235 [email protected]

connect.nintex.com

PROPERTIES
Name AfterHours Description Gets or sets a value indicating a users preference for notifications out of business hours notifications. Gets or sets a value indicating a users preference for notifications during business hours notifications. Gets or sets the value to send SMS messages to.

BusinessHours

SMSAddress

METHODS
Name UserPreference Description Constructor. Creates an instance of UserPreference for a given login name. Persists the property values to the database.

Update

www.nintex.com

Page 130 of 235 [email protected]

connect.nintex.com

Software Development Kit v1.2

WEB SERVICES
Nintex Workflow functionality can be accessed via web services. This is the preferred method of integration by third party applications.

OVERVIEW
Nintex Workflow web services have been developed to behave similar to SharePoint web services. To call the Nintex Workflow web service http://MyServer/[sites/][MySite/][MySubsite/]_vti_bin/NintexWorkflow/Workflow.a smx

To access the Nintex Workflow web services WSDL http://MyServer/[sites/][MySite/][MySubsite/]_vti_bin/NintexWorkflow/Workflow.a smx?WSDL

For more information on SharePoint web service usage and coding see the Web Service Guidelines in the SharePoint SDK.

WEB SERVICE: WORKFLOW

Service AddLongTermDelegationRule AddWorkflowSchedule Description Adds a delegation rule for a user. Adds or updates a workflow schedule on a file in a document library. Adds or updates a workflow schedules on a list item. Delegate all tasks assigned to a user to another. Deletes a delegation rule for a user. [System] Delete a snippet. [System] Delete a workflow. Generates a workflow export file. Run the fix for workflows in site templates. [System] Used by the Windows Vista Gadget for displaying a user's tasks. Retrieves the available outcomes for a Flexi task action.

AddWorkflowScheduleOnListItem DelegateAllTasks DeleteLongTermDelegationRule DeleteSnippet DeleteWorkflow ExportWorkflow FixWorkflowsInSiteFromTemplate GetItemsPendingMyApproval

GetOutcomesForFlexiTask

www.nintex.com

Page 131 of 235 [email protected]

connect.nintex.com

Software Development Kit v1.2

Service GetRunningWorkflowTasks Description Retrieves all workflow tasks associated with a file in a document library. Retrieves all running workflow tasks. Retrieves tasks assigned to the calling user that are associated with a document in a document library. Retrieves tasks assigned to the calling user that are associated with a particular list item. Retrieves all workflow tasks associated with a list item. Retrieves workflow history. Retrieves workflow history. [System] Flags a task to not be displayed on the 'My Workflow Tasks' web part. Registers a response to a Flexi task action. Obsolete. Registers a response to a workflow Approval or Review task in the default Nintex Workflow task list. Registers a response to a workflow Approval or Review task in a custom Nintex Workflow task list. Will publish a workflow from the contents of an exported workflow file. Will publish a workflow from the contents of an exported workflow file, and fail if a workflow with the same name already exists. Will publish a workflow from the contents of an exported workflow file, skipping the SharePoint validation step. Will publish a workflow from the contents of an exported workflow file, skipping the SharePoint validation step, and fail if a workflow with the same name already exists. Will publish a workflow from the XML contents of an exported workflow file. Will publish a workflow from the XML contents of an exported workflow file, and fail if a workflow with the same name already exists. Will publish a workflow from the XML contents of an exported workflow file, skipping the SharePoint validation step.

GetRunningWorkflowTasksCollection GetRunningWorkflowTasksForCurrentUser

GetRunningWorkflowTasksForCurrentUserForListItem

GetRunningWorkflowTasksForListItem GetWorkflowHistory GetWorkflowHistoryForListItem HideTaskForApprover

ProcessFlexiTaskResponse ProcessTaskResponse

ProcessTaskResponse2

PublishFromNWF

PublishFromNWFNoOverwrite

PublishFromNWFSkipValidation

PublishFromNWFSkipValidationNoOverwrite

PublishFromNWFXml

PublishFromNWFXmlNoOverwrite

PublishFromNWFSkipValidation

www.nintex.com

Page 132 of 235 [email protected]

connect.nintex.com

Software Development Kit v1.2

Service PublishFromNWFSkipValidationNoOverwrite Description Will publish a workflow from the XML contents of an exported workflow file, skipping the SharePoint validation step, and fail if a workflow with the same name already exists. [System] Used by the workflow designer to publish a workflow. [System] Deletes a configured workflow schedule. Deletes a configured workflow schedule. [System] Returns the html required to render a workflow. Will save a workflow from the contents of an exported workflow. Will save a workflow from the contents of an exported workflow, and fail if a workflow with the same name already exists. Will save a workflow from the XML contents of an exported workflow. Will save a workflow from the XML contents of an exported workflow, and fail if a workflow with the same name already exists. [System] Save a snippet. [System] Save a template. [System] Used to save a workflow in the designer. [System] Checks if the snippet exists. Starts a workflow on a file in a document library. Starts a workflow on a list item. [System] Checks if the template exists. [System]Terminates a running or errored workflow. Terminates a running or errored workflow that is on a file in a document library. Terminates a running or errored workflow that is on a list item. *System+ Checks the workflows in use value against the list.

PublishWorkflow

QueryForMessages RemoveWorkflowSchedule RemoveWorkflowScheduleOnListItem RetrieveWorkflow

SaveFromNWF

SaveFromNWFNoOverwrite

SaveFromNWFXml

SaveFromNWFXmlNoOverwrite

SaveSnippet SaveTemplate SaveWorkflow SnippetExists StartWorkflow StartWorkflowOnListItem TemplateExists TerminateWorkflow TerminateWorkflowByName

TerminateWorkflowByNameForListItem

WorkflowExists

www.nintex.com

Page 133 of 235 [email protected]

connect.nintex.com

Software Development Kit v1.2

ADDLONGTERMDELEGATIONRULE
Adds a delegation rule for a user. If the Allow site administrators to set long term delegation for other users option is switched off in Global Settings, the callee of the web service must be the user the delegation rule is being created for. Web Reference: http://<Site>/_vti_bin/NintexWorkflow/workflow.asmx

SYNTAX
C# public int AddLongTermDelegationRule( DateTime fromTheBeginningOf, DateTime untilTheEndOf, string delegateFrom, string delegateTo, bool currentSiteOnly )

PARAMETERS
fromTheBeginningOf The date from when the delegation rule will take effect (from 12:01 in the morning). untilTheEndOf The date when the delegation rule will finish at the end of the day (midnight). delegateFrom The user whose tasks will be delegated. delegateTo The user to whom the tasks will be delegated to. currentSiteOnly True to restrict this rule to the context team site, false to make this rule global.

RETURN VALUE
The ID of the rule.

ADDWORKFLOWSCHEDULE
Adds or updates a workflow schedule on a file in a document library. Web Reference: http://<Site>/_vti_bin/NintexWorkflow/workflow.asmx

SYNTAX

www.nintex.com

Page 134 of 235 [email protected]

connect.nintex.com

Software Development Kit v1.2

C# public int AddWorkflowSchedule( string fileUrl, string workflowName, string startDataXml, Nintex.Workflow.Scheduling.Schedule schedule, bool updateIfExists )

PARAMETERS
fileUrl Url to the file with workflows containing running tasks. Can be absolute or server relative. workflowName The name of the workflow to schedule. startDataXml The xml representing the start data for a workflow. Can be an empty string. See Appendix B: Workflow Start Data Format for more information. schedule The details of when and until the schedule should run. All dates are in local time. updateIfExists If a schedule for the nominated workflow already exists on the nominated item, its details will be updated if this parameter is true.

connect.nintex.com

Software Development Kit v1.2

SYNTAX
C# Public void DeleteLongTermDelegationRule ( int id )

PARAMETERS
id The domain\login name of the user to whom tasks are currently assigned to.

DELEGATETASK
Delegates a workflow task from one user to another. Web Reference: http://<Site>/_vti_bin/NintexWorkflow/workflow.asmx Delegating a task with the web service follows the same rules as the UI. An error will be thrown if delegation is not enabled for the task unless the identity calling the web service is a site administrator.

SYNTAX
C# public bool DelegateTask( int spTaskId, string taskListName, string targetUsername, string comments, bool sendNotification )

PARAMETERS
spTaskId The SharePoint ID of the task to be reassigned. taskListName The name or GUID of the task list containing the task. targetUsername The domain\login name of the user to reassign the task to. comments Any notes about why the task was delegated for the workflow history sendNotification True to send a notification message to the new assignee informing them that the task has been assigned to them.

RETURN VALUE
False if the task is not pending, otherwise True.

www.nintex.com

Page 139 of 235 [email protected]

connect.nintex.com

Software Development Kit v1.2

www.nintex.com

Page 140 of 235 [email protected]

connect.nintex.com

Software Development Kit v1.2

DELETEWORKFLOW
[System] Delete a workflow. Web Reference: http://<Site>/_vti_bin/NintexWorkflow/workflow.asmx

SYNTAX
C# public void DeleteWorkflow( Guid listId, Guid workflowId )

PARAMETERS
listId A Guid that specifies the ID of the list the workflow is associated with. workflowId A Guid that specifies the ID of the workflow

www.nintex.com

Page 141 of 235 [email protected]

connect.nintex.com

Software Development Kit v1.2

EXPORTWORKFLOW
Generates a workflow export file for the specified workflow. This is the equivliant of exporting a workflow from the workflow designer. Web Reference: http://<Site>/_vti_bin/NintexWorkflow/workflow.asmx

SYNTAX
C# public string ExportWorkflow( string workflowName, string listName )

PARAMETERS
workflowName The name of the workflow to export. listName The name or ID of the list that contains the workflow.

RETURN VALUE
A string representing the contents of an Export file.

www.nintex.com

Page 142 of 235 [email protected]

connect.nintex.com

HIDETASKFORAPPROVER
[System] Flags a task to not be displayed on the 'My Workflow Tasks' web part. Web Reference: http://<Site>/_vti_bin/NintexWorkflow/workflow.asmx

SYNTAX
C# public void HideTaskForApprover( long approverId, int contentDbId )

PARAMETERS
approverId The Nintex internal ID of the approver. contentDbId The Nintex internal ID of the content database containing the task data.

www.nintex.com

Page 153 of 235 [email protected]

connect.nintex.com

Software Development Kit v1.2

PROCESSFLEXITASKRESPONSE
Registers a response to a workflow Flexi task. Web Reference: http://<Site>/_vti_bin/NintexWorkflow/workflow.asmx

SYNTAX
C# public bool ProcessFlexiTaskResponse( string comments, string outcome, int spTaskId, string taskListName )

PARAMETERS
comments Any comments to record against the task response. outcome The response for the task. Use GetOutcomesForFlexiTask to discover the allowed responses. spTaskId The list item id of the task. taskListName The name of the task list that contains the task.

RETURN VALUE
True if task was processed successfully. False is the user context of the web service call is not a valid approver for the task. Other errors will manifest as an exception.

www.nintex.com

Page 154 of 235 [email protected]

connect.nintex.com

Software Development Kit v1.2

PROCESSFLEXITASKRESPONSE2
Registers a response to a workflow Flexi task. Web Reference: http://<Site>/_vti_bin/NintexWorkflow/workflow.asmx

SYNTAX
C# public ProcessTaskResponseResult ProcessFlexiTaskResponse( string comments, string outcome, int spTaskId, string taskListName )

RETURN VALUE
One of the following values: Success: The response was submitted correctly. CannotObtainLock: The task is locked by another operation so the response could not be submitted. For this result, it is good to inform the user to retry in a moment. InvalidUser: The user responding to the task is invalid.

www.nintex.com

Page 155 of 235 [email protected]

connect.nintex.com

Software Development Kit v1.2

PROCESSTASKRESPONSE
Obsolete. Registers a response to a workflow Approval or Review task in the default Nintex Workflow task list Web Reference: http://<Site>/_vti_bin/NintexWorkflow/workflow.asmx

SYNTAX
C# public bool ProcessTaskResponse( string comments, Outcome outcome, int spTaskId )

PARAMETERS
comments Any comments to record against the task response. outcome The response for the task. Use 'Continue' for review tasks, 'Approved' or 'Rejected' for approval tasks. spTaskId The list item ID of the task.

RETURN VALUE
True if task was processed successfully. False is the user context of the web service call is not a valid approver for the task. Other errors will manifest as an exception.

www.nintex.com

Page 156 of 235 [email protected]

connect.nintex.com

Software Development Kit v1.2

PROCESSTASKRESPONSE2
Registers a response to a workflow Approval or Review task in a custom Nintex Workflow task list. Web Reference: http://<Site>/_vti_bin/NintexWorkflow/workflow.asmx

www.nintex.com

Page 167 of 235 [email protected]

connect.nintex.com

Software Development Kit v1.2

QUERYFORMESSAGES
[System] Web Reference: http://<Site>/_vti_bin/NintexWorkflow/workflow.asmx

connect.nintex.com

Software Development Kit v1.2

SAVETEMPLATE
[System] Save the template. Web Reference: http://<Site>/_vti_bin/NintexWorkflow/workflow.asmx

SYNTAX
C# public void string string string string ) SaveTemplate( templateName, templateDescription, category, activityConfigs

PARAMETERS
templateName A string specifying the template name. templateDescription A string specifying the template name. category A string specifying the category the template belongs to. activityConfigs A XML Representation of the configurations for the actions contained in the object.

www.nintex.com

Page 177 of 235 [email protected]

connect.nintex.com

Software Development Kit v1.2

SAVEWORKFLOW
[System] Used to save a workflow in the designer. Web Reference: http://<Site>/_vti_bin/NintexWorkflow/workflow.asmx

REPORTDEFINITION
Top-level element that contains the definition of a report definition.

Page 196 of 235 [email protected]

connect.nintex.com

Software Development Kit v1.2

PAGINGMODE
Specifies the mode which should be used for paging.

CHILD ELEMENTS
None

Page 202 of 235 [email protected]

connect.nintex.com

Software Development Kit v1.2

URLFORMATSTRING
The template of the Url with format items which are replaced with values specified in UrlColumnNames.

connect.nintex.com

Software Development Kit v1.2

ISTEXTCOLUMN
Identifies this column as a key text field used when generating charts.

CHILD ELEMENTS
None

PARENT ELEMENTS
ReportColumn

OCCURRENCES
Minimum: 1 Maximum: 1

www.nintex.com

Page 211 of 235 [email protected]

connect.nintex.com

PARAMETERTYPE
Specifies the value type of the parameter.

ApprovalAI This table holds the recognized responses for the LazyApproval system. Column ApprovalAIRuleID SiteID Type int - Identity uniqueidentifier Identifier of the site collection that the term is valid for. Identifier of the teamsite that the term is valid for. The term that is recognized. 1 if the term is recognized as an approve, 0 if the term is recognized as a reject. Description

WebID

uniqueidentifier

Phrase Outcome

nvarchar (255) bit

CustomContextData This table stores custom context data items that have been registered with Nintex Workflow. Column ID TypeName AssemblyName Type int - Identity nvarchar (255) nvarchar (255) Description

Databases This table stores the connection details for each content database. Column DatabaseID DatabaseName ServerName Username Password UseIntegrated Type int - Identity nvarchar (255) nvarchar (255) nvarchar (255) nvarchar (255) bit The username to use if UseIntegrated is false. The password to use if UseIntegrated is false. Description

www.nintex.com

Page 222 of 235 [email protected]

connect.nintex.com

Software Development Kit v1.2

Delegation This table stores the list of static delegations that been set up by users. Column DelegationID Username Type int - Identity nvarchar (255) The login name of the user whose tasks will be delegated. The date and time from which the delegation is valid for. The date and time until which the delegation is valid for. Identifier of the site collection where the delegation will be applied to the task. Identifier of the teamsite where the delegation will be applied to tasks. The login name of the user whom tasks will be assigned to in the specified timeframe. Description

StartDate

datetime

EndDate

datetime

SiteID

uniqueidentifier

WebID

uniqueidentifier

Delegate

nvarchar (255)

GlobalSettings This table stores configuration settings. Column SMTPServer Type nvarchar (255) Description The address of the smtp server used to send emails. The address from which notifications are sent. The reply to address for notifications.

FromAddress ReplyAddress RTCSourceMailAddress RTCSourceDomainUser RTCSourceDomainUserPassword RTCSourceIMServer RTCSourceIMTransport EnforceSafeLoop

nvarchar (255) nvarchar (255) nvarchar (255) nvarchar (255) nvarchar (255) nvarchar (255) nvarchar (255) bit

1 to specify that a delay action must be inserted at the bottom of loops and state machines.

www.nintex.com

Page 223 of 235 [email protected]

connect.nintex.com

Software Development Kit v1.2

GlobalSettings DefaultTaskListName nvarchar (255) The default task list that Nintex Workflow uses when a workflow is created. A task list with this name will be created when Nintex Workflow is activated on a teamsite if it does not exist. 1 to allow users to set up delegations over a period of time. 1 to allow users to define their notification preferences. 1 to specify that web designer rights are required to create schedules. The view name that the Item Properties control on the default approver / reject page will look for when determining which properties to display. The text appended to a notification that is LazyApproval enabled.

AllowStaticDelegation

bit

AllowNotificationPreferences

bit

NeedDesignerRightsForSchedules

bit

TaskViewName

nvarchar (255)

LazyApprovalFooter

nvarchar (255)

Holidays This table stores the holidays that have been defined. Holidays are used when determining business hours. Column HolidayID HolidayName HolidayDate RepeatYearly WebId SiteId Type int - Identity nvarchar (255) datetime bit uniqueidentifier uniqueidentifier Description

LazyApprovalIgnoreTerms This table stores the terms that LazyApproval checks an incoming message subject for to determine if it should discard the message. Column Id Term Type int - Identity nvarchar (255) The text to search a subject for. Description

www.nintex.com

Page 224 of 235 [email protected]

connect.nintex.com

Software Development Kit v1.2

www.nintex.com

Page 225 of 235 [email protected]

connect.nintex.com

Software Development Kit v1.2

MessageTemplates This table stores the message templates used in all notifications. Column TemplateID MessageRequireApproval Type int - Identity text The default message for an approval email notification. Header text pre pended to all email notifications. Footer text appended to all email notifications. The default message for an approval no longer required email notification. Identifier of the site collection where the message settings will be used. Identifier of the teamsite where the message settings will be used. Description

Header

nvarchar (1500)

Footer MessageNoLongerRequired

nvarchar (1500) text

SiteID

uniqueidentifier

WebID

uniqueidentifier

Reports Lists the reports available to the reporting webparts. Reporting functionality is available for Enterprise licenses only. Column ID Title Description Role Type int - Identity nvarchar (256) nvarchar (256) nvarchar (256) The domain group that users must be a member of to view the report. The definition of the report. 1 to allow users to select the report in the report webparts. } The display name of the report. Description

DefinitionXML Enabled

text bit

ReportType

nvarchar (256)

www.nintex.com

Page 226 of 235 [email protected]

connect.nintex.com

Software Development Kit v1.2

RTCMessageQueue This table stores the message in queue for Real Time Communication clients (Microsoft Office Communication Server [OCS] and Microsoft Live Communication Sever [LCS]). Column MessageID Message SIPAddress EmailAddress Created Type int - Identity text nvarchar (255) nvarchar (255) datetime Description

Storage This table maps site collections to Nintex Workflow content databases. All workflow instance data on the site collection will be stored in the content database listed here. Column DatabaseID SiteID Type int uniqueidentifier Description

UserPreference Stores preferences set by a user. Column Username Type nvarchar (255) Description The login name of the user that the settings apply to. The notification preference for messages that are sent out of business hours. The notification preference for messages that are sent during business hours. The address to send sms messages to for the user.

Afterhours

tinyint

Businesshours

tinyint

SMSAddress

nvarchar (255)

www.nintex.com

Page 227 of 235 [email protected]

connect.nintex.com

Software Development Kit v1.2

Version Internal user only. This table stores the database version. Column Version Type nvarchar (50) Description

WorkflowConstants This table stores the workflow constants that have been defined. Column ID Title Description Value Type int - Identity nvarchar (255) nvarchar (4000) nvarchar (4000) The value that is used to replace the constant at runtime. 1 if the value is encrypted. The name of the workflow constant. Description

Sensitive SiteId WebId Type

bit uniqueidentifier uniqueidentifier nvarchar (255)

The data type of the constant.

WorkflowSchedule This table stores the workflow schedules. Column ScheduleId ItemId ListId Type int - Identity int uniqueidentifier The item ID that the schedule is defined on. The list ID of the list containing the item that the schedule is defined on. The ID of the teamsite that contains the item that the schedule is defined on. The ID of the sitecollection that contains the item that the schedule is defined on. The ID of the workflow that the schedule executes. Description

WebId

uniqueidentifier

SiteId

uniqueidentifier

WorkflowId

uniqueidentifier

www.nintex.com

Page 228 of 235 [email protected]

connect.nintex.com

Software Development Kit v1.2

WorkflowSchedule NextRunTime Schedule StartData datetime ntext ntext When the schedule will next execute. XML representing the details of the schedule. XML representing data that will be passed to the workflow when the schedule runs. The login name of the user who last modified the schedule.

ModifiedBy

nvarchar (255)

www.nintex.com

Page 229 of 235 [email protected]

connect.nintex.com

Software Development Kit v1.2

CONTENT DATABASE
This section describes the database tables used to store workflow progress and task information.

TABLES
This table stores information related to delegation history. DelegationHistory This table stores a record of task delegations. Column DelegationHistoryID Username Type int - Identity nvarchar (255) The login name of the user who delegated the task. The login name of the user who had the task delegated to them. The comments entered by the user to explain the delegation. The identifier of the task approver that the delegation applies to. Description

Delegate

nvarchar (255)

Comment

varchar (1024)

ApproverID

bigint

DatabaseID DelegationDate

int datetime A timestamp of when the delegation occurred.

HumanWorkflow This table stores information about tasks that have been assigned. Column HumanWorkflowID ApprovalType Type bigint - Identity tinyint The rules for task completion. Value corresponds to a member of Nintex.Workflow.HumanApproval.ApprovalType. The time and date that the task was assigned. The time and date that the task was completed. The outcome of the task. Value corresponds to a member of Nintex.Workflow.HumanApproval.Outcome Description

EntryTime ExitTime Outcome

datetime datetime tinyint

WorkflowTaskID

int

www.nintex.com

Page 230 of 235 [email protected]

connect.nintex.com

Software Development Kit v1.2

HumanWorkflow WorkflowProgressID bigint The workflow action that the task is associated with. If ApprovalType is Vote, the number of required approvals are stored here. The type of task. Values corresponds to a member of Nintex.Workflow.HumanApproval.TaskType.

ApprovalData

nvarchar (255)

TaskType

tinyint

HumanWorkflowApprovers This table stores information about each user that is assigned to a task. Column ApproverID HumanWorkflowID Username EmailAddress EntryTime ExitTime Type bigint - Identity bigint nvarchar (255) nvarchar (1024) datetime datetime The workflow task that the user is associated to. The login name or group name of the approver. The email address of the approver. The date and time when the task was assigned. The data and time when the approver responded. The comments entered by the user when registering their response. The response the user entered. Value corresponds to a member of Nintex.Workflow.HumanApproval.Outcome. The approval required message that was sent to this user. The approval not required message that was sent to this user. 1 if this approver is allowed to delegate the task. 1 if this approver is a domain group. 1 if this user is a SharePoint group. The ID of the SharePoint task item that represents the task. Description

Comments

nvarchar (1024)

Outcome

tinyint

ApprovalRequiredMessageTemplate

text

NoLongerRequiredMessageTemplate

text

AllowDelegation

bit

IsDomainGroup IsSPGroup SPTaskID

bit bit int

www.nintex.com

Page 231 of 235 [email protected]

connect.nintex.com

Software Development Kit v1.2

HumanWorkflowApprovers TaskDeleted bit 1 if this task should not be displayed on the My Workflow Tasks webpart.

Version Internal user only. This table stores the database version. Column Version Type nvarchar (50) Description

WorkflowInstance This table stores information about every workflow that is run. Column InstanceID XOML SiteID Type bigint - Identity text uniqueidentifier The version of the Xoml file this workflow uses. The ID of the site collection that the workflow was run on. The ID of the list containing the item that the workflow was run on. The ID of the list item that the workflow was run on. The ID of the teamsite that the workflow was run on. A timestamp of when the workflow was started. The ID used to identify the workflow instance in SharePoint. Obsolete. The login name of the user who started the workfklow. The display name of the workflow that was started. The ID of the workflow that was started. The current state of the workflow. Value corresponds to a member of Microsoft.SharePoint.Workflow.SPWorkflowState. Description

ListID

uniqueidentifier

ItemID

int

WebID

uniqueidentifier

StartTime WorkflowInstanceID

datetime uniqueidentifier

WorkflowData WorkflowInitiator

image nvarchar (50)

WorkflowName

nvarchar (255)

WorkflowID State

Uniqueidentifier int

www.nintex.com

Page 232 of 235 [email protected]

connect.nintex.com

Software Development Kit v1.2

WorkflowInstance Rules ConfigXml text text The version of the Rules file this workflow uses. The configuration xml that was used when publishing the workflow into SharePoint. The number of minutes that the workflow is expected to take.

ExpectedDuration

int

WorkflowProgress This table stores a log of every action that is run in a workflow. Column WorkflowProgressID InstanceID Type bigint Identity bigint The ID of the workflow instance the action is associated with. The ID of the action type that this action is. See Activities table in the configuration database. Obsolete. 1 if the action has finished executing. The time the action was run. An identifier that associates an action with its position in the workflow. The name assigned to the action in the workflow designer. The number of minutes that the action is expected to take. Description

ActivityID

int

WorkflowData ActivityComplete TimeStamp SequenceID

image bit datetime int

CurrentActivityTitle

nvarchar (255)

ExpectedDuration

int

www.nintex.com

Page 233 of 235 [email protected]

connect.nintex.com

Software Development Kit v1.2

APPENDICES APPENDIX A: START A WORKFLOW FROM THE SHAREPOINT OBJECT MODEL
Starting workflows is done from the SharePoint object model without any need to reference the Nintex Workflow code base. There is a StartWorkflow method of the SPWorkflowManager class. The msdn link is http://msdn.microsoft.com/enus/library/ms435535.aspx. Starting a workflow SPSite site = ; SPWorkflowManager workflowManager = site.WorkflowManager; workflowManager.StartWorkflow(SPListItem, SPWorkflowAssociation, associationData)

The SPListItem parameter is the SharePoint item that the workflow will run on. The SPWorkflowAssociation parameter represents the workflow to start. The SPList that contains the list item has a WorkflowAssociations collection property containing all the available SPWorkflowAssociation objects. The associationData parameter is a string of xml representing the workflow initiation data (referred to as Start Data in Nintex Workflow). To use the default initiation data, or if the workflow has no start data, pass in the AssociationData property of the SPWorkflowAssociation object. For more information on providing specific values for the associationData, see Appendix B.

www.nintex.com

Page 234 of 235 [email protected]

connect.nintex.com

Software Development Kit v1.2

APPENDIX B: WORKFLOW START DATA FORMAT
When starting a workflow with start data through the API, the values for each start data item can be specified in an XML format. The same format is used in a number of Nintex Workflow web service methods that are related to starting workflows. The following is an example of the workflow start data format: Start Data xml example <Data> <StartDataItem1>value1</StartDataItem1> <StartDataItem2>value2</StartDataItem2> <StartDataItem3>value3</StartDataItem3> </Data>

Each child element represents one start data item. The name of the element is the internal name of the start data item. To determine the internal name of the start data item: 1. 2. 3. 4. 5. Open SharePoint Designer to the site that holds the workflow Expand Workflows\NintexWorkflow\ Open the folder with the same name as your workflow Open the file with the same name as your workflow and an extension of .xoml.wfconfig.xml Find your start data item in the list of Parameter elements. The Name attribute is the internal name of the start data item.

This xml format is used both in workflows created with Nintex Workflow 2007 and SharePoint Designer. Note that date values must be in UTC, represented in the ISO8601 format. Note that in the Microsoft SharePoint Workflow API Start Data is referred to as Association Data. The default association data for a workflow can be queried via the AssociationData property of the SPWorkflowAssociation object representing the workflow.

www.nintex.com

Page 235 of 235 [email protected]

connect.nintex.com

Cis4100 - Project 1 Introduction: Murach'S PHP and Mysql by Developing An Application Called Sportspro Technical
0% (1)
Cis4100 - Project 1 Introduction: Murach'S PHP and Mysql by Developing An Application Called Sportspro Technical
16 pages
Export Data From Excel To Table Using Custom Web ADI Integrator
No ratings yet
Export Data From Excel To Table Using Custom Web ADI Integrator
17 pages
Manageengine Servicedesk Plus: Technical Proposal
No ratings yet
Manageengine Servicedesk Plus: Technical Proposal
10 pages
SRS - How to build a Pen Test and Hacking Platform
From Everand
SRS - How to build a Pen Test and Hacking Platform
alasdair gilchrist
2/5 (1)
Nintex Workflow 2007 SDK 1.1
No ratings yet
Nintex Workflow 2007 SDK 1.1
214 pages
70-488 Exam Dumps With PDF and VCE Download (61-80)
No ratings yet
70-488 Exam Dumps With PDF and VCE Download (61-80)
36 pages
PeopleTools 8.48 Documentation Issues and Corrections
No ratings yet
PeopleTools 8.48 Documentation Issues and Corrections
24 pages
pl-400_7
No ratings yet
pl-400_7
23 pages
Websphere Dashboard Framework - Standard Demo Lab Exercise: Compensation Budget Summary and Drilldown
No ratings yet
Websphere Dashboard Framework - Standard Demo Lab Exercise: Compensation Budget Summary and Drilldown
25 pages
Microsoft PL 400 Exam Updated Material PDF
100% (1)
Microsoft PL 400 Exam Updated Material PDF
33 pages
AX2012R2-DevIII-FinalAppendix
No ratings yet
AX2012R2-DevIII-FinalAppendix
20 pages
How To Configure SAP XI PI
No ratings yet
How To Configure SAP XI PI
59 pages
Export Data From Excel To Table Using Custom Web ADI Integrator
No ratings yet
Export Data From Excel To Table Using Custom Web ADI Integrator
18 pages
MB-820-demo
No ratings yet
MB-820-demo
9 pages
[Nov-2021] New PassLeader PL-400 Exam Dumps
No ratings yet
[Nov-2021] New PassLeader PL-400 Exam Dumps
8 pages
PL 400 December 11, 2024
No ratings yet
PL 400 December 11, 2024
27 pages
Job Portal
No ratings yet
Job Portal
138 pages
Manual Steps
No ratings yet
Manual Steps
6 pages
What'S New in Businessobjects 6.5 Service Pack 2
No ratings yet
What'S New in Businessobjects 6.5 Service Pack 2
24 pages
2007 Office Service Pack 2 Changes
No ratings yet
2007 Office Service Pack 2 Changes
45 pages
Name of Solution:: Please Rate This Solution and Share Your Feedback On Website
No ratings yet
Name of Solution:: Please Rate This Solution and Share Your Feedback On Website
3 pages
Tech Note 923 - Resolving Excel Reporting Missing
No ratings yet
Tech Note 923 - Resolving Excel Reporting Missing
8 pages
Microsoft Dynamics AX 2009 Upgrade Process
No ratings yet
Microsoft Dynamics AX 2009 Upgrade Process
7 pages
Question No: 1
No ratings yet
Question No: 1
49 pages
Artículo Arquitectura PHP
No ratings yet
Artículo Arquitectura PHP
4 pages
France
No ratings yet
France
17 pages
PRPC Build Your First Application
No ratings yet
PRPC Build Your First Application
134 pages
JDE 1
No ratings yet
JDE 1
12 pages
Platform: CRM System, WPF/Silverlight, Azure
No ratings yet
Platform: CRM System, WPF/Silverlight, Azure
11 pages
LAB 05 Forms Experience Builder Portal Integration
No ratings yet
LAB 05 Forms Experience Builder Portal Integration
35 pages
Msus 02 How To Migrate Access Forms To Dot Net Whitepaper Ver15
No ratings yet
Msus 02 How To Migrate Access Forms To Dot Net Whitepaper Ver15
71 pages
Aif Ax
No ratings yet
Aif Ax
13 pages
80312A-ENUS Error Log
No ratings yet
80312A-ENUS Error Log
10 pages
Account Generator
No ratings yet
Account Generator
6 pages
Project Report of Online Job Portal
No ratings yet
Project Report of Online Job Portal
141 pages
Skip Navigation
No ratings yet
Skip Navigation
10 pages
Change Document3a Step by Step
No ratings yet
Change Document3a Step by Step
15 pages
Microsoft - Certleader.pl 400.rapidshare.2023 Jun 27.by - Brian.176q.vce
No ratings yet
Microsoft - Certleader.pl 400.rapidshare.2023 Jun 27.by - Brian.176q.vce
25 pages
Web Reports Sample ReadMe
No ratings yet
Web Reports Sample ReadMe
5 pages
BI Publisher Report With Apex
No ratings yet
BI Publisher Report With Apex
8 pages
279026Employee Central Advanced Reporting Implementation Tips
No ratings yet
279026Employee Central Advanced Reporting Implementation Tips
4 pages
Proyecto 13-17
No ratings yet
Proyecto 13-17
19 pages
Convincing Reasons To Move To Web Intelligence
No ratings yet
Convincing Reasons To Move To Web Intelligence
6 pages
Microsoft - PL 300.VJan 2024.by .HuynDair.127q
100% (1)
Microsoft - PL 300.VJan 2024.by .HuynDair.127q
101 pages
Name of Solution:: Please Rate This Solution and Share Your Feedback On Website
No ratings yet
Name of Solution:: Please Rate This Solution and Share Your Feedback On Website
3 pages
PCFControl Guide
No ratings yet
PCFControl Guide
37 pages
AET Cookbook v1 3
No ratings yet
AET Cookbook v1 3
14 pages
[June-2021] New PassLeader PL-400 Exam Dumps
No ratings yet
[June-2021] New PassLeader PL-400 Exam Dumps
14 pages
Studio Lab Manual - Vendor Invoice Entry - WinGUI
No ratings yet
Studio Lab Manual - Vendor Invoice Entry - WinGUI
19 pages
0404
No ratings yet
0404
36 pages
Article_ Technical Documentation Agent - Boomi Community
No ratings yet
Article_ Technical Documentation Agent - Boomi Community
4 pages
4.multi Tier Architecture
No ratings yet
4.multi Tier Architecture
6 pages
IM Appendix J Web DB Dev With ColdFusion Ed12
No ratings yet
IM Appendix J Web DB Dev With ColdFusion Ed12
15 pages
IPPM4.2c Release Notes
No ratings yet
IPPM4.2c Release Notes
20 pages
Practice Questions for UiPath Certified RPA Associate Case Based
From Everand
Practice Questions for UiPath Certified RPA Associate Case Based
Exam OG
No ratings yet
Visual Basic 2010 Coding Briefs Data Access
From Everand
Visual Basic 2010 Coding Briefs Data Access
Kevin Hough
5/5 (1)
Learning Dynamics NAV Patterns: Create solutions that are easy to maintain, are quick to upgrade, and follow proven concepts and design
From Everand
Learning Dynamics NAV Patterns: Create solutions that are easy to maintain, are quick to upgrade, and follow proven concepts and design
Marije Brummel
No ratings yet
SharePoint 2010 Issue Tracking System Design, Create, and Manage
From Everand
SharePoint 2010 Issue Tracking System Design, Create, and Manage
Sarath Thirumoorthi
3/5 (1)
C# 2010 Coding Briefs Data Access
From Everand
C# 2010 Coding Briefs Data Access
Kevin Hough
No ratings yet
Intermediate Load Runner With Oracle/Apex Concepts.
From Everand
Intermediate Load Runner With Oracle/Apex Concepts.
Rohan Gordon
No ratings yet
Ricoh SmartDeviceMonitor Quick Reference Document 2009724184734
No ratings yet
Ricoh SmartDeviceMonitor Quick Reference Document 2009724184734
2 pages
PDF Alfa
No ratings yet
PDF Alfa
34 pages
Installation Guide
No ratings yet
Installation Guide
9 pages
S01C5021 PDF
No ratings yet
S01C5021 PDF
243 pages
Syncmaster 245B / 245Bw: Install Driver Install Programs
No ratings yet
Syncmaster 245B / 245Bw: Install Driver Install Programs
54 pages
ReadmeV8 0 en
No ratings yet
ReadmeV8 0 en
7 pages
EchoLink USB To Serial Adapter Instructions PDF
No ratings yet
EchoLink USB To Serial Adapter Instructions PDF
4 pages
Microsoft Application Compatibility Toolkit (ACT) Version 5.0 - Frequently Asked Questions (FAQ)
No ratings yet
Microsoft Application Compatibility Toolkit (ACT) Version 5.0 - Frequently Asked Questions (FAQ)
8 pages
BU303-353 Win UsersGuide-V2.2
No ratings yet
BU303-353 Win UsersGuide-V2.2
14 pages
Leica Install Guide
No ratings yet
Leica Install Guide
24 pages
System Requirements Guidelines NX 8 5
No ratings yet
System Requirements Guidelines NX 8 5
3 pages
C25 Service Manual PDF
No ratings yet
C25 Service Manual PDF
454 pages
How To: Install Windows 7 From A USB Key!
No ratings yet
How To: Install Windows 7 From A USB Key!
6 pages
Bizhub C360 C280 C220 Spec and Install Guide
No ratings yet
Bizhub C360 C280 C220 Spec and Install Guide
23 pages
TAC Vista 4.5 and 5.0 New Features Overview Presentation
No ratings yet
TAC Vista 4.5 and 5.0 New Features Overview Presentation
57 pages
NFS HS Sp-Ep
No ratings yet
NFS HS Sp-Ep
5 pages
Comms Tool User Guide
No ratings yet
Comms Tool User Guide
44 pages
Ims200 Surveillance System User Manual
No ratings yet
Ims200 Surveillance System User Manual
93 pages
How To Install The P6 Standalone
No ratings yet
How To Install The P6 Standalone
11 pages
IO Libraries Suite - Why Can't I Talk To My Keysight USB Instrument When NI-VISA Is Also Installed On Windows Vista - Keysight (Formerly Agilent's Electronic Measurement)
No ratings yet
IO Libraries Suite - Why Can't I Talk To My Keysight USB Instrument When NI-VISA Is Also Installed On Windows Vista - Keysight (Formerly Agilent's Electronic Measurement)
1 page
DDT Users Manual
No ratings yet
DDT Users Manual
73 pages
Code Composer Studio v4.1
No ratings yet
Code Composer Studio v4.1
5 pages
Full Guide-Hotel Lock System
No ratings yet
Full Guide-Hotel Lock System
48 pages
Remote Administrator 5: Installation Manual and User Guide
No ratings yet
Remote Administrator 5: Installation Manual and User Guide
122 pages
License Wizard: Installation Notes For Version 3.1
No ratings yet
License Wizard: Installation Notes For Version 3.1
26 pages
Spss Install Instructions
No ratings yet
Spss Install Instructions
5 pages
IndigoSCADA User Manual
No ratings yet
IndigoSCADA User Manual
69 pages
RSLinx Classic - 2.59.02
50% (2)
RSLinx Classic - 2.59.02
14 pages
License Server Status - NOT RUNNING For ArcGIS License Manager 10
No ratings yet
License Server Status - NOT RUNNING For ArcGIS License Manager 10
4 pages
Binyamin Karam Ali Khan: Article I. Personal Information
No ratings yet
Binyamin Karam Ali Khan: Article I. Personal Information
2 pages