Jingmei Li's MSDN Blog : SharePoint Development

How to hide Send To Records Center menu option in MOSS?

jingmeili — Fri, 14 Mar 2008 19:35:00 GMT

MOSS delivers a Records Center site template which can be used for records managment, but once this is configured every user in the farm will be able to send documents to Records Center by using the context menu Send To -> Records Center. This is usually not desired since enterprise would normall develop a systematic way of submitting records through workflows, event handlers, etc.

To hide Send to Records Center menu option, I've listed out 2 options.

Option #1: quick but need to watch out for SP install to avoid changes being overidden.

1. Go to c:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\LAYOUTS\1033, locate CORE.js, make a copy of the file and save it in another place for backup purpose.

2. Open core.js in Notepad, search for "officialfilename" and comment out the line that says "CAMOpt" in the "if block" by inserting "//" in front of the line. Save the file. The code should look like the following after the change:

if (ctx.OfficialFileName !=null && ctx.OfficialFileName !="")

{

strDisplayText=ctx.OfficialFileName;

strAction="STSNavigate('"+ ctx.HttpRoot+ "/_layouts/SendToOfficialFile.aspx?"+ "SourceUrl="+ currentItemEscapedFileUrl+ "&Source="+ GetSource()+"')";

strImagePath="";

//CAMOpt(sm, strDisplayText, strAction, strImagePath);

}

3. IISReset to force client cache refresh.

Option #2: more deployable and can control which sites the change is applied to.

1. Go to c:P\rogram Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\LAYOUTS\1033, locate CORE.js, open core.js in Notepad, search for "officialfilename". Copy the entire javascript function and paste it to a new file called something like CORE_custom.js and make the same changes as in option #1.

2. In SharePoint Designer, open the site where you want the change to be applied. Create a custom master page with the following change:

<SharePoint:ScriptLink language="javascript" name="core.js" Defer="true" runat="server"/>

<SharePoint:ScriptLink language="javascript" name="core_CUSTOM.js" Defer="true" runat="server"/>

3. In your site, go to site settings and Master Page, then apply the custom master page.

How to start a workflow programmatically in the InfoPath code using Workflow web service

jingmeili — Thu, 17 Jan 2008 21:20:00 GMT

How to start an Approval workflow programmatically in the InfoPath form code?

Create a web reference that points to http://yourSiteUrl/_vti_bin/workflow.asmx .
Configure an Approval workflow in your form library and capture the template id.

From form library settings->workflow settings, click the workflow name, right click in the page to View Source. Search for “templateid”. The TemplateID looks like the following:

TemplateID=%7b5C65AB69-11BC-430D-B730-71050250F576%7d

(“%7b” is encoded for “{“ and “%7d” is encoded for “}”)

GUID for the template id is : 5C65AB69-11BC-430D-B730-71050250F576

Write the InfoPath code. The highlighted parts in the sample code below needs to be replaced.

**TIP: If you can't get the workflowParamers XML string right, you can write a simple console app in server using OM. SPWorkflowAssociation.AssociationData will return the init form data that you already configured in the list/library workflow settings.

public void submit_OnClick(DocActionEvent e)

{

// Write your code here.

WorkflowService.Workflow workflowService = new WorkflowService.Workflow();

workflowService.Url = "http://siteURL/_vti_bin/workflow.asmx";

workflowService.Credentials = System.Net.CredentialCache.DefaultCredentials;

workflowService.PreAuthenticate = true;

try

{

XmlDocument workflowParameters = new XmlDocument();

string strXml = "<my:myFields xml:lang='en-us' xmlns:xsi='http://www.w3.org/2001/XMLSchema-instance' xmlns:my='http://schemas.microsoft.com/office/infopath/2003/myXSD'><my:Reviewers><my:Person><my:DisplayName>Approver’s display name</my:DisplayName><my:AccountId>domain\\account</my:AccountId><my:AccountType>User</my:AccountType></my:Person></my:Reviewers><my:CC></my:CC><my:DueDate xsi:nil='true'></my:DueDate><my:Description></my:Description><my:Title></my:Title><my:DefaultTaskType>1</my:DefaultTaskType><my:CreateTasksInSerial xsi:nil='true'></my:CreateTasksInSerial><my:AllowDelegation>true</my:AllowDelegation><my:AllowChangeRequests>true</my:AllowChangeRequests><my:StopOnAnyReject xsi:nil='true'></my:StopOnAnyReject><my:WantedTasks xsi:nil='true'></my:WantedTasks><my:SetMetadataOnSuccess xsi:nil='true'></my:SetMetadataOnSuccess><my:MetadataSuccessField></my:MetadataSuccessField><my:MetadataSuccessValue></my:MetadataSuccessValue><my:ApproveWhenComplete xsi:nil='false'></my:ApproveWhenComplete><my:TimePerTaskVal xsi:nil='true'></my:TimePerTaskVal><my:TimePerTaskType xsi:nil='true'></my:TimePerTaskType><my:Voting>false</my:Voting><my:MetadataTriggerField></my:MetadataTriggerField><my:MetadataTriggerValue></my:MetadataTriggerValue><my:InitLock xsi:nil='false'></my:InitLock><my:MetadataStop xsi:nil='true'></my:MetadataStop><my:ItemChangeStop xsi:nil='true'></my:ItemChangeStop><my:GroupTasks>false</my:GroupTasks></my:myFields>";

workflowParameters.LoadXml(strXml);

//Guid for the workflow templateId

Guid guid = new Guid("{5C65AB69-11BC-430D-B730-71050250F576}");

//form URL needs to be replaced

XmlNode result = workflowService.StartWorkflow("http://siteURL/formlibrary/test.xml", guid, workflowParameters);

if (result != null)

thisXDocument.UI.Alert("Result: " + result.Value);

}

catch (SoapException ex)

{

thisXDocument.UI.Alert("SoapException: " + ex.Message + " " + ex.Detail.Value);

}

catch (Exception ex0)

{

thisXDocument.UI.Alert("Exception: " + ex0.Message);

}

How to create a custom timer job in SharePoint 2007 (MOSS)

jingmeili — Wed, 06 Jun 2007 18:51:00 GMT

Came across Andrew's post about how to create a custom timer job in MOSS. I'm working on a Lotus Notes application migration project and I'm planning to recreate some Lotus Notes application Agents (scheduled jobs and notifications) in MOSS using custom timer job. Will post follow-ups on this later...

http://www.andrewconnell.com/blog/articles/CreatingCustomSharePointTimerJobs.aspx

Issues found this Andrew's timer job:

I used the wsp file that Andrew provided and deployed to my customer's MOSS dev environment successfully but got Unknown Error when trying to activate the feature through Site Settings->Site Collection Features UI. The event viewer showed the insufficient permission to write to SharePoint_config database, etc. Then I performed stsadm -o activatefature -id ##### -url http://server/sites/siteName through command and it worked.
Sometimes changes made to the code were not reflected till the SharePoint timer service was restarted.

How to create your own custom 404 error page and handle redirect in SharePoint 2007 (MOSS)?

jingmeili — Sun, 08 Apr 2007 17:05:00 GMT

People alway ask how to use their own 404 file not found error page vs. the generic one from IE in MOSS environment. The following example catches the 404 error and sends users to a redirect page.

Here's the steps:

1. In your MOSS server, make a copy of

%systemdrive%\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\TEMPLATE\LAYOUTS\1033\sps404.html

and call it my404.html

2. Create a Virtual Directory in IIS under your MOSS root web application. For example /errors

3. Create your own redirect aspx page, for example /errors/my404redirect.aspx and code your redirect logic in there. This is a normal asp.net page.

4. In my404.html, make the following change:

STSNavigate("/errors/my404redirect.aspx?oldUrl=" + requestedUrl);

5. Create a Console Application and insert the following code and run it in MOSS server

System.Uri webApplicationUri = new Uri(http://MyMOSSServer/);

SPWebApplication webApplication = SPWebApplication.Lookup(webApplicationUri);

webApplication.FileNotFoundPage = "my404.html"; //*note

webApplication.Update();

*Note: By default this is set to null. FileNotFoundPage needs to point to a html file that lives in %systemdrive%\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\TEMPLATE\LAYOUTS\1033. The file needs to be html only.

6. Now when you browse to a page that doesn't exist, you should expect to be brought to the redirected page.

*Another note:

In IE there's a "Show friendly HTTP error messages" setting which is ON by default in Internet Options->Advanced. With this setting on, sometimes your custom error page is not displayed. In order to override this setting, both my404.html and /errors/my404redirect.aspx from the above steps need to be larger than 512 bytes in size. Refer to the following KB about this setting: http://support.microsoft.com/kb/218155

* This seems to be working within a site collection context only, i.e. http://MyMOSSServer/sites/siteA if sites is a wildcard inclusion managed path and siteA doesn't exist in MOSS then this URL will NOT trigger the custom 404 error page set to SPWebApplication.FileNotFoundPage property.