Hi,
Did you mean how to open skelta controls using web application ? . There are two ways to get started in executing & designing workflows.
1) Use Skelta Enterprise Console to create workflows and execute
2) Skelta web server controls can be embedded to ASPX pages using drag & drop functionality. See below steps required [Taken from help files] 1) Create a new ASP.NET Web Site, the location for web site can be file system or Http (VS2005 -> File -> New -> Website) e.g: Create a file system ASP.NET Website under C:\Demo\SkeltaWebSite 2) Create a copy of BPMUITemplates from [SkeltaInstalledFolder]\BPM.Net 2007\Web\ BPMUITemplates to the RootFolder of Created web site e:g : Copy BPMUITemplates folder to C:\Demo\SkeltaWebSite 3) Create five aspx pages for embedding Skelta web server controls a. Designer.aspx b. WorkItemList.aspx c. Calendar.aspx d. BAM.aspx e. Queue.aspx 4) Remove the below tag from all aspx pages <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> 5) Add the below tag in web.config <pages validateRequest="false"></pages> 6) Add the Skelta Server Controls to the Visual Studio .NET 2005 Toolbox, a. Select View->Toolbox. b. Right click on the blank area in the Toolbox and select the Add Tab option. c. Type “Skelta Server Controls” and press Enter. d. Now select the Skelta Server Controls tab. e. Right click on the blank area under the Skelta Server Controls tab, and select Add/Remove Items. f. This opens the Customize Toolbox window. g. Select the .NET Framework Components tab from this window. h. Click on the Browse button. i. In the Open dialog, navigate to the [SkeltaInstalledFolder]\BPM.NET 2007\Bin directory. j. Select Workflow.NET.Web.Designer.NET2.dll – this is for the Process Designer Control. k. Select Skelta.HWS.WorkListChannel.Web.WorkItemListControl.dll – this is for the WorkItem List Control l. Select Skelta.BAM.dll – this is for the BAM Control. m. Select Skelta.HWS.Web.CalendarControl.dll – this is for the Calendar Control. n. Select Skelta.HWS.Web.QueueControl.dll – this is for the Queue Control. o. Click on the OK button of the Customize Toolbox. Now all the specified controls get added to the Visual Studio.NET toolbox. 7) Make sure the Workflow.NET.CodeBehind.dll is referenced in the web application from Bin 8) Drag and Drop each of the controls to the respective aspx pages. 9) The Mandatory properties for each of the controls are a. Process Designer Control: Application Name/Repository name b. WorkItem Control : Application Name & UserIdString. The UserIdString value varies based on the authentication provider configured. This value should have the Entity instance mapped for the respository to be prefixed along with real id of the user e.g: If repository is mapped to Skelta list user provider the UserIdString will be skeltalist::C99B4110-C8CC-410B-BF70-93F3A7E34EDF, here the GUID is taken from SKEUsers table present in the Repository DB If repository is mapped to active directory user provider the UserIdString will be activedirectory::[samAccountName], here samAccountName is an active directory property value If repository is mapped to forms user provider the UserIdString will be sqlprovider::[UniqueIdentifier], here UniqueIdentifier is the unique identifier id for resource If repository is mapped to ASP.NET user provider the UserIdString will be membershipprovider::[UniqueIdentifier], here UniqueIdentifier is the unique identifier id for resource. c. Queue Control : Application Name & UserIdString (Same as above) d. Calendar Control : Application Name 10) Design the workflow using designer control and publish the workflow 11) Execute the workflow using the Workflow.NET.Engine.Client class E.g., string xmlcontent = <Expense><Amount>2000</Amount></Expense>"; Workflow.NET.Engine.Client objClient = new Workflow.NET.Engine.Client ("ApplicationName","WorkflowName"); Int ExecutionID = objClient.Execute([UserIdString],xmlcontent);// UserIdString is used to populate the workflow initiator. objClient.Close();
Moderator |