Open /modules/Tasks/Dashlets/MyTasksDashlet/MyTasksDashlet.data.php

Initially it looks like this:

'contact_name' => array(
 'width'   => '8',
 'label'   => 'LBL_LIST_CONTACT'
),

To make this field link to the contacts module:

'contact_name' => array(
 'width'   => '8',
 'label'   => 'LBL_LIST_CONTACT',
 'link' => true,
 'action' => 'DetailView',
 'module' => 'Contacts',
 'id' => 'CONTACT_ID',
 'related_fields' => array('contact_id')
 ),

The main fields are:
link: True/False
module: The name of the destination module
action: DetailView or EditView
id: The field that contains the ID for the related field. If it doesn’t work lower case, try it in uppercase
related_fields: The field that contains the relation ID – This should be the same as ‘id’

Example:

You can hid the Leads SubPanel into Accounts module by customizing the custom/modules/Accounts/Ext/Layoutdefs/layoutdefs.ext.php, which is a upgrade safe customization. Add the following to the end of the file, before the closing PHP tag.

unset($layout_defs['Accounts']['subpanel_setup']['leads']);

When you create a new relationship through Admin -> Studio -> -> Relationships, Sugar create several files at custom folders:

Left Side Hand Relationship (module from which you created the relationship):
custom/Extension/modules/{moduleName}/Ext/Vardefs/{relationshipName}.php
custom/Extension/modules/{moduleName}/Ext/Layoutdefs/{relationshipName}.php
custom/Extension/modules/{moduleName}/Ext/Language/{relationshipName}.php

Right Side Hand Relationship:
custom/Extension/modules/{moduleName}/Ext/Vardefs/{relationshipName}.php
custom/Extension/modules/{moduleName}/Ext/Language/{relationshipName}.php

Relationship itself:
custom/metadata/{relationshipName}Meta.php

Table Dictionary:
custom/Extension/application/Ext/TableDictionary/{relationshipName}.php

Edit custom/application/Ext/TableDictionary/tabledictionary.ext.php file and delete include(‘custom/metadata/{relationshipName}.php’);

To remove the relationship, you need to delete these files. After removing all these files you should need to go to Admin -> Repair -> Quick Repair and Rebuild

Original post:

http://www.sugarcrm.com/forums/showthread.php?t=37781

For the latest version, go here

https://github.com/redinkdesign/Social-Group-Icons-in-Postbit

Contents should be the following:

$entry_point_registry['entry_point_name'] = array('file' => 'path/to/custom/code.php', 'auth' => true);

/**
	 * A wrapper for sugar's mail class
	 * Sends emails to everyon in $tos array.
	 * $tos['user name'] = 'username@domain.com';
	 *
	 * @example : 	$tos['Some User'] = 'SomeUser@somewhere.com';
	 * 				$tos['Some User 2'] = 'SomeUser2@somewhere.com';
	 * 				sendSugarPHPMail($tos, 'hi', 'hello fellas');
	 *
	 * @param associative array
	 * @param string $subject
	 * @param string $body
	 * @return boolean
	 */
	function sendSugarPHPMail($tos, $subject, $body){

		require_once('include/SugarPHPMailer.php');
		require_once('modules/Administration/Administration.php');

		$mail = new SugarPHPMailer();
		$admin = new Administration();
		$admin->retrieveSettings();

		if ($admin->settings['mail_sendtype'] == "SMTP") {
			$mail->Host = $admin->settings['mail_smtpserver'];
			$mail->Port = $admin->settings['mail_smtpport'];

			if ($admin->settings['mail_smtpauth_req']) {
				$mail->SMTPAuth = TRUE;
				$mail->Username = $admin->settings['mail_smtpuser'];
				$mail->Password = $admin->settings['mail_smtppass'];
			}

			$mail->Mailer   = "smtp";
			$mail->SMTPKeepAlive = true;

		}else{
			$mail->mailer = 'sendmail';
		}

		$mail->From     = $admin->settings['notify_fromaddress'];
		$mail->FromName = $admin->settings['notify_fromname'];
		$mail->ContentType = "text/html"; //"text/plain"

		$mail->Subject = $subject;
		$mail->Body = $body;

		foreach ($tos as $name => $address){
			$mail->AddAddress("{$address}", "{$name}");
		}

		if (!$mail->send()) {
			$GLOBALS['log']->info("sendSugarPHPMail - Mailer error: " . $mail->ErrorInfo);
			return false;
 		}else{
 			return true;
 		}
	}

This example uses a custom helper function called ’sendSugarPHPMail’ which can be found here http://redinkdesign.net/open-source/simple-sugarcrm-e-mail-wrapper.

In this example, we’re going to email someone when a Case’s status is set to ‘Closed’.

To make this upgrade friendly we’re going to create two files in ‘custom/modules/Cases’.
First file: logic_hooks.php – Loaded automatically by Sugar.
Second: case_closed.php – Our custom code.

The contents of logic_hooks.php are:

<?php

	if (!defined('sugarEntry') || !sugarEntry) die('Not A Valid Entry Point');

	$hook_array = array();

	$hook_array['before_save'] = array();

	// array(hook execute order, 'hook name', 'hook code location', 'hook code class name', 'hook code function to execute')
	$hook_array['before_save'][] = array(1, 'case_closed', 'custom/modules/Cases/case_closed.php', 'case_closed', 'case_closed');

?>

Our array parameters must be the following:

1. hook execute order
2. hook name
3. hook code location
4. hook code class name
5. hook code function to execute

$hook_array['before_save'][] = array(1, 'case_closed', 'custom/modules/Cases/case_closed.php', 'case_closed', 'case_closed');

The contents of case_closed.php are:

<?php

	if (!defined('sugarEntry') || !sugarEntry) die('Not A Valid Entry Point');

	class case_closed{

		function case_closed(&$bean, $event, $arguments){

			// make sure the status was actually changed to closed
			// $bean->fetched_row['status'] is the stored status of the case
			// $bean->status is the status it was changed to
			if ($bean->fetched_row['status'] !== 'Closed' && $bean->status === 'Closed'){

				$subject = "Closed: Case {$bean->case_number} - {$bean->name}";
				$body = "Assigned to: {$bean->assigned_user_name}<br />";
				$body .= 'Description: ' . (empty($bean->description)? ' n/a ' : $bean->description);

				$to['Mr. Bean'] = 'mrbean@whatevs.com';

				if (!sendSugarPHPMail($to, $subject, $body)){
					$GLOBALS['log']->info("Could not send case closed notification:  " . $mail->ErrorInfo);
				}
			}
		}
	}

?>

Application hooks

These hooks do not make use of the $bean argument.
after_ui_frame
Fired after the frame has been invoked and before the footer has been invoked
Available in version 4.5.0 and later
after_ui_footer
Fired after the footer has been invoked
Available in version 4.5.0 and later
server_round_trip
Fired at the end of every SugarCRM page
Available in version 4.5.0 and later

Module hooks

before_delete
Fired before a record is deleted
Available in version 4.5.0 and later

after_delete
Fired after a record is deleted
Available in version 4.5.0 and later

before_restore
Fired before a record is undeleted
Available in version 4.5.0 and later

after_restore
Fired after a record is undeleted
Available in version 4.5.0 and later

after_retrieve
Fired after a record has been retrieved from the database. This hook does not fire when you create a new record.
Available in version 4.5.0 and later

before_save
Fired before a record is saved.
Note: With certain modules, like Cases and Bugs, the human-readable ID of the record (like the case_number field in the Case module), is not available within a before_save call. This is because this business logic simply hasn’t been executed yet.
Available in version 4.5.0 and later

after_save
Fired after a record is saved.
Note: With certain modules, like Cases and Bugs, the human-readable ID of the record (like the case_number field in the Case module), is not available within a before_save call. This is because this business logic simply hasn’t been executed yet.
Available in version 4.5.0 and later

process_record
Fired immediately prior to the database query resulting in a record being made current. This gives developers an opportunity to examine and tailor the underlying queries. This is also a perfect place to set values in a record’s fields prior to display in the DetailView or ListView. This event is not fired in the EditView.
Available in version 4.5.0 and later

Hooks for Users module

before_logout
Fired before a user logs out of the system
Available in version 4.5.0 and later

after_logout
Fired after a user logs out of the system
Available in version 4.5.0 and later

after_login
Fired after a user logs into the system.
Available in version 4.5.0 and later

after_logout
Fired after a user logs out of the system.
Available in version 4.5.0 and later

before_logout
Fired before a user logs out of the system.
Available in version 4.5.0 and later

login_failed
Fired on a failed login attempt
Available in version 4.5.0 and later

Here’s a list of all available logic hooks…

http://developers.sugarcrm.com/docs/OS/5.1/-docs-Developer_Guides-Developer_Guide_5.1-DevGuide.1.101.html