MDS Workflow Extender and SPD Custom Action

Rating:        Based on 1 rating
Reviewed:  1 review
Downloads: 262
Change Set: 24314
Released: Jun 2, 2013
Updated: Jun 2, 2013 by hascheidl
Dev status: Stable Help Icon

Recommended Download

Application Site Workflow Activation Web Service - SP2013
application, 7K, uploaded Jun 2, 2013 - 189 downloads

Other Available Downloads

Application MDS WorkflowExtenders for SharePoint 2013
application, 7K, uploaded Jun 2, 2013 - 35 downloads
Application MDS Custom Activity for SharePoint Designer
application, 7K, uploaded Jun 2, 2013 - 38 downloads

Release Notes

Custom activity and custom action for SharePoint Designer

A SharePoint solution package. Deploy the solution by PowerShell using the Install-SPSolution with GACDeployment option.
Check SharePoint Designer Custom Workflow Action.

MDS WorkflowExtenders for SharePoint 2013

A workflow extender for Master Data Services. This is a DLL to be deployed in MDS server. Please check Master Data Services workflow extender for details.

Site Workflow Activation Web Service - SP2013

Deploy the solution by PowerShell using the Install-SPSolution with GACDeployment option.
http://technet.microsoft.com/en-us/library/ff607534.aspx

For more information on this component, check https://mdsforsharepoint.codeplex.com/wikipage?title=Web%20Service%20for%20Site%20Workflow%20activation

Reviews for this release

     
For starters the ASP.NET runtime changes the client ID of your controls in this release. This is the id attribute that is used in client script to access controls from JavaScript in the browser. With normal ASPX pages the server side ID of a control is usually inserted one on one in the final HTML. For example a Button control with a server side ID of Button1 in a normal ASPX release defined with this code: <asp:Button ID="Button1" runat="server" Text="Click Me"/> ends up with a client side ID like this in the final HTML: <input type="submit" name="Button1 value="Click Me" id="Button1"/> However the same button inside an <asp:Content> control ends up like this: <input type="submit name="ct100ScpMainContentSButton1" value="Click Me" id="cpMainContent_Button1" /> The same attribute has been prefixed with the auto generated ID of the master page(ct100) and both the name and the id attributes contain the IDof the content PlaceHolder control (cpMaincontent). This means that any client side code that refers to Button1 =cpMC_B1.
by CenecaJet82 on Dec 24, 2013 at 1:05 AM