Andrew Connell Updates for Share.Point 2.Workflow.Over the last two months weve seen a LOT of updates and improvements to workflow development for Share.Point 2.Recently Grace Kochavi from the Share.Point workflow team published a post on the Apps for Office Share.Point Blog that talks about a bunch of the updates and then walks you through creating a workflow Share.PowerShellGetHelpInstallSolution_300AFF91.png' alt='How To Install A Wsp In Sharepoint Foundation 2010' title='How To Install A Wsp In Sharepoint Foundation 2010' />Point Workflow Development with Office Developer Tools for Visual Studio 2.I dont want to rehash what Grace said, but I do want to add a few things I ran into including one big show stopper that isnt in the current documentation that you MUST do in order to publish workflows within apps.There are two things you need to do.You first need to update your platform which includes Service Bus, Workflow Manager and Share.Point 2.Power.Shell statement script and finally you need to update your developer tools.Delivering a high performance application in SharePoint is quite challenging and most of the times you end up using many tools to figure out the reason behind the.In SharePoint 2013 we have a new site template called Developer Site Template.I was pretty excited to know more about this template but was not able to get much info.Sapplique SharePoint Foundation 2013, SharePoint Server 2013 Enterprise.Dernire rubrique modifie 20161216.Dploie une solution SharePoint installe.Over the last two months weve seen a LOT of updates and improvements to workflow development for SharePoint 2013.Recently Grace Kochavi from the SharePoint workflow.How To Install A Wsp In Sharepoint Foundation 2010' title='How To Install A Wsp In Sharepoint Foundation 2010' />Update Your Platform.There are quite a few things you need to do here.Youre ultimately trying to update workflow within Share.Point 2.Workflow Manager 1.Update the Share.Point Dependencies.Because workflow is handled by Workflow Manager 1.Service Bus 1.February CUs for both Service Bus 1.Workflow Manager 1.February 2.Cumulative Update for Service Bus 1.KB2.February 2.Cumulative Update for Workflow Manager 1.KB2.Two words of warning when you install Workflow Manager 1.Ensure you are logged in as the same admin account you used to install Workflow Manager 1.I set the service account for WM as a local admin on the box so I was logged in as that.When you run the CU installer, for me and many others, youll see the installer seem to go away and appear complete.This isnt the case.Be patient and wait.To verify the installs completed correctly, you can check the file versions for both products.For Service Bus, look in C Program FilesService Bus1.Microsoft.Cloud.Service. Bus.This should be version 2.For Workflow Manager, look in C Program FilesWorkflow Manager1.WorkflowArtifacts for the Microsoft.Workflow.Service.EXE. This is the DLL that runs the workflow backend service.It should be version 1.Or you can look in the Add Remove Programs app, select View Installed Updates and find both Service Bus 1.Workflow Manager 1.Update Share.Point 2.March 2. 01.Public Update.With the dependencies updated, the next thing you need to do is update Share.Point 2.The update you need is the Share.Point 2.March 2.PU PU vs.CU. Both Todd Klindt and Wictor Wilen do a good job with guidance here take note of the search and WAC stuff they talk about.March 2.Public Update for Share.Point 2.Note you only need the server PU if you have server.SPF one has.After applying the updates, you should rerun the workflow pairing Power.Shell cmdlet Register SPWorkflow.Service with the Force flag set.This will do two things it will add a new deployment group and also republish the updated Share.Point activities updated in the March 2.Public Update to the Workflow Manager farm.Special Note about Workflow Changes in the Share.Point 2.March 2.Public Update. How To Activate Adobe Photoshop Cs 3 here. The way workflows are deployed within apps has changed from Share.Point 2.RTM to how they are deployed after this Public Update.In Share.Point 2.RTM When a workflow was deployed in a Share.Point app, they were deployed using WSPs.In the Share.Point 2.March 2. 01.Public pdate they are now deployed using this thing called a deployment group Im sparing you the details, but its an internal thing to the app deployment thats new in Share.Point 2.The challenge is that this deployment group doesnt exist after installing all the PU.The omission of this step is likely an oversight on the Share.Point 2.March PU installation script or instructions.Ive spoken to the product team who confirmed this needs to be done and will update the instructions accordingly.If you dont have this deployment group, you will get an error when you try to deploy an app that includes a workflow.There is no Workflow App Part registered.This happens both in production as well as in development.You dont get this error if you include the workflow in a farm or sandbox solution.In order to create the deployment group you need to call Register.Workflow.Lifecycle.Management.Environment on the Workflow Manager Service service app proxy in order to register a new Workflow Deployment Group provider that knows how to unpack deploy workflows included in an app.So from a Share.Point Management Shell, run this script Wms.Sap Get SPWorkflow.Service.Application.Proxy.Wms. Sap. Register.Workflow.Lifecycle.Management.EnvironmentNote this is not necessary if you rerun the pairing Power.Shell cmdlet like I state above as this is one of the things the pairing command does for you.Update Your Developer Tools.Last but not least, make sure you update your Share.Point 2.RTM toolsThere are a ton of changes in the workflow development pieces in these tools, something I discuss more in this post.You can install these RTM tools directly over the Preview 2 from the Web Platform Installer, or using this shortcut link http aka.Office.Dev. Tools.For. VS2.Note that any workflows you created using the Preview 2 tools will need to be updated as there were quite a few changes improvements to activities as well as the deployment and packaging process within apps.I discuss some of those things in this post.To make things easier, the workflow team provides a tool available through Code.Plex that will help in updating your projects.April 4, 2.AM. Fixed two typos from the original post 1 Power.Shell script referred to Get SPWorkflow.Application.Proxy when it should be Get SPWOrkflow.Service.Application.Proxy and 2 changed Product Update to Public Update.June 1.PMI added some extra notes about running the pairing Power.Shell cmdlet after installing all the updates.Previously the post only mentioned the Power.Shell cmdlet to add the new workflow deployment group.However you should run the pairing command instead.The reason for this is so the activities updated in the March 2.Appdata Roaming Microsoft Credentials Access Denied there.Public Update are republished to the Workflow Manager farm.Managing Apps and Solutions Using Power.Shell.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |