Changeset 6
- Timestamp:
- 2010-11-23 16:54:29 (18 months ago)
- File:
-
- 1 edited
-
Lexnet - Person Accounts/README.txt (modified) (1 diff)
Legend:
- Unmodified
- Added
- Removed
-
Lexnet - Person Accounts/README.txt
r4 r6 1 1 2 2 INSTALLATION 3 After code has been installed, the Account objects view functionality needs to be overriden to use the AccountRedirect 3 2 fields are added to the org as part of the installation. A field called Contact_Id__c which is used to contain the contact 4 Id when there is a single contact and it is a Person Account. The second field is flag to determine that the account was originally 5 created as an individual contact. See the use cases below for more information on how the functionality works 6 7 After code has been installed - 8 9 Remove the required attribute on the account for all contact page layouts that will be allowed to create Person Accounts 10 11 The Account objects view functionality needs to be overriden to use the AccountRedirect 4 12 Visualforce page. 13 14 Be sure to also setup security for the code for all profiles. 15 16 USE CASES 17 #1) When a contact is inserted that does not relate to an account, a new account is created using the format "<FirstName> <LastName>". When 18 you click on the account for a this contact you will be redirected to the contact record and as such no record maintenance is done at the account level. 19 20 #2) If you add a second contact to an account that was originally setup as an individual account, the account/contact functionality will work the same as 21 it normally would in Salesforce. The fact that account was created as an individual account is retained in the Person_Account__c field for future use. 22 23 #3) If you add another contact to the same account in use case #2 you get the same result, just 3 contacts. 24 25 #4) if you delete the first contact, you will have the same results as use case #2 26 27 #5) if you delete the second contact you added, then if the account was originally created as a Person Account you will get a person account again, with an account name of the last contact remaining 28 with the contact id set so when you click on the account you get redirected back to the contact as you would in use case #1. 29
Note: See TracChangeset
for help on using the changeset viewer.