Skip to main content

Posts

Showing posts from April, 2015

Nintex Workflow Namespace

<%@ Register TagPrefix="Nintex" Namespace="Nintex.Workflow.ServerControls" Assembly="Nintex.Workflow.ServerControls, Version=1.0.0.0, Culture=neutral, PublicKeyToken=913f6bae0ca5ae12" %> <%@ Register TagPrefix="Nintex" TagName="ConfigurationPropertySection" src="_layouts/NintexWorkflow/ConfigurationPropertySection.ascx" %> <%@ Register TagPrefix="Nintex" TagName="ConfigurationProperty" src="_layouts/NintexWorkflow/ConfigurationProperty.ascx" %> <%@ Register TagPrefix="Nintex" TagName="DialogLoad" Src="_layouts/NintexWorkflow/DialogLoad.ascx" %> <%@ Register TagPrefix="Nintex" TagName="DialogBody" Src="_layouts/NintexWorkflow/DialogBody.ascx" %> <%@ Register TagPrefix="Nintex" TagName="SingleLineInput" Src="_layouts/NintexWorkflow/SingleLineInput.ascx" %> <%@ Regis

Java Screept Code for Custom Nintex Dialog on SharePoint

 <Nintex:DialogLoad runat="server" />     <script type="text/javascript" language="javascript">         function TPARetrieveConfig() {             setRTEValue('<%=propertyProperty.ClientID%>', configXml.selectSingleNode("/NWActionConfig/Parameters/Parameter[@Name='Property']/PrimitiveValue/@Value").text);             document.getElementById('<%=resultOutput.ClientID%>').value = configXml.selectSingleNode("/NWActionConfig/Parameters/Parameter[@Name='ResultOutput']/Variable/@Name").text;         }         function TPAWriteConfig() {             configXml.selectSingleNode("/NWActionConfig/Parameters/Parameter[@Name='Property']/PrimitiveValue/@Value").text = getRTEValue('<%=propertyProperty.ClientID%>');             var resultOuputCtrl = document.getElementById('<%=resultOutput.ClientID%>');             if (resultOuputCtrl.val

Custom Actions Event Receiver

using System; using System.Collections.ObjectModel; using System.IO; using System.Runtime.InteropServices; using System.Xml; using Microsoft.SharePoint; using Microsoft.SharePoint.Administration; using Nintex.Workflow; using Nintex.Workflow.Administration; using Nintex.Workflow.Common; using System.Reflection; namespace CFSP.CustomActions.Features.WebApplication___Custom_Actions {     [Guid("07607091-449b-422b-94e4-84e6d863eb9e")]     public class WebApplication___Custom_ActionsEventReceiver : SPFeatureReceiver     {         #region Events         public override void FeatureActivated(SPFeatureReceiverProperties properties)         {             SPWebApplication parent = (SPWebApplication) properties.Feature.Parent;             AddCustomAction(parent, properties, "ReadFromPropertyBagAction.nwa");         }         public override void FeatureDeactivating(SPFeatureReceiverProperties properties)         {             SPWebApplication paren

SharePoint Capacity Management and Sizing Overview

Capacity management   is an ongoing process, because no implementation remains static with regard to content and usage. You need to plan for growth and change, so that your SharePoint Server 2013–based environment can continue to deliver an effective business solution. Capacity Planning  is only one part of the capacity management cycle. It is the initial set of activities that brings the design architect to the point where there is an initial architecture that the architect believes will best serve the SharePoint Server 2013 deployment. The capacity management model includes additional steps to help you validate and tune the initial architecture, and provides a feedback loop for re-planning and optimizing the production environment until it can support design goals with optimal choices of hardware, topology, and configuration. Capacity management versus capacity planning Capacity management extends the concept of capacity planning to express a cyclical approach in w