Creating a new tab for a new type of accounts
My company wants to reestructure all the organization of the company.
They want to categorize our clients in a better way than they are now and they want to improve the way our sales managers see everything.
The main thing they want to do its to create tabs for each different client of client. In that way, the sales manager that works with agencies will see a tab Agencies accounts where he will have that kind of accounts. The sales manager that works twith tour-operator will have a tab called TO accounts where he/she will have that kind of accounts.
My question is that I dont know if that is completely correct. In order to create new tabs I will need to create new objects. But those new objects will be very similar to the tab account. In addition, I will not use the tab accounts any more, because i will define the accounts as different objects...And because this objects are not accounts any more, we wont be able of creating follow ups related to them....
I proposed them to create one different kind of record type for each kind of client we will have and in that way everything will work as i think it should. But they insist in that they want a different tab for each kind of client in order to the sales manager being able of accessing his/her tab....
What do you think is the best solution?Any recommendations?
Thanks a lot!
In all seriousness it is a bad idea.
Yes the Record Type idea is much better and this way you can set up certain Account list views associated to the different Record Types and restrict the Record Types on certain profiles etc.
Your assumption is correct if they want tabs, creating new object is one option but I am really not sure on what you meant by follow ups. If those are just activities on account then you can definitely have activities on all the objects when you create them. But by creating the Custom objects you will lose the core functionalities of account and the objects will be just any other custom object unless you implement everything again and not everything can be recreated (in terms of functionality of accounts). There are lot of things tied around accounts, like relationship to contacts which I bet you cannot replicate, although you can create a look up or master detail but the relationship is something much more than those(I call it hybrid, as it have both the features of Master detail and Look up), account teams which you probably might escape from this by using manual sharing on the object and account team custom object. This is like trying to replicate the entire Salesforce functionality and as I said no everything can be replicated and this would take a major architectural change and time consuming. So I suggest the best way to do this to do it through Record Types as you suggested. You might even get away by using visual force pages and custom development depending on the exact requirements. Please let me know if this helped in anyway.
You just made clear to me the reason why I dont want to create objects for each different client. What I said, if you havean object account with all its functionalities,why would you want to replicate it? And in addition you will never get the same functionalities that salesforce already developed for the object account.
I think we will go for record types. One for each client and each sector. This will involve a big amount of record types but its easier than a big amount of new objects.
Rajith, about the visualforce pages I didnt really get into it very deep, so I dont really know the facilities they can bring or scope the have.... can you really change a lot the Salesforce user interface or you see yourself very restricted just like with the page layout tool?
As I said earlier using VF pages you can easily solve this. All you have to do is create different VF pages for each type of account you want and you can create tabs for those VF pages. You can create as many tabs as you want for one object and many VF pages (provided you stay under the Salesforce Limits). And it is not too hard to create a VF page. In fact you can create one VF page and handle data differently in all the tabs based on the User who is being logged in(Preferably profile info). Please let me know if you think this might help you if you have some developers or even if you are a button click admin you can do it. VF pages give you more flexibility than that page layout tool. There are all sort of thing you can do if you incline towards the Custom development using at the least VF pages. Let me kow if you need more details or any help.
I would be very interested in what you said of creating many tabs for the same object and each one of the tabs showing a different vs page. That would really solve my problem giving a solution to me as a developer and to my company with their requirements.
Any farther explanatio or document where I could find this info?
Please give me more details on how many account types are you talking about and how many tabs are we talking about. All you have to do is create a VF page for each type of account you want fields you want to display in that page, It will be just like your standard page (this just like creating a new page layout for accounts but using Visual force). Then go to Setup--> create --> Tabs --> scroll down you will see a section called VF Tabs, using that you an create tabs and assign the VF page to the tab. Regarding creating the VF page for your need is I know will be a basic stuff and do not need much of development experience, and admin can do it. I am an admin and I can do it. The documentation on how to create a VF page is here:
this link will give you all the details you need. Also feel free to let me know if you need any help.
This really helps me!Im getting into VF pages!
Or I can think of one more way which is all configurations. You can use the list views and in combination with Public groups you can restrict the users to have only one List View for the user based on the group or even per user base, then use the record type on the record to control the data visibility. But in this case if they are running reports on Accounts there is always possibility that they will see other accounts depending on how you are using the reports, their structure and their permissions.
I would say give them all the options, Caveats, and specifically convert everything in terms of level of effort and the investment involved in the options and let them pick which one will be the biggest bang for the buck.
I am actually a Software developer and they just me got me involved in this project of Salesforce in my company. Thats why I am kind of new in all this of salesforce and I am trying to find out as many things as possible in order to know how far we can go with this tool.
What do you mean with Apex controller?Where can I find info about this?
Is there any way to make a relation between the VF pages and the record type, for example, filtering the accounts you will show.
If this is possible you can create a VF page for each record type. Doing this I will get the tabs view that the company wants without creating new objects and the apex controller doesnt seem very difficult.
Im not really into it a lot, so I cant really appreciate if something is really timetaking and difficult or not, thats why I would like to know your opinion!
Hm... I think we might be thinking in a wrong way regarding the record type usage here. I am any situation, I think the whole purpose of the creating the tabs is to just separate the accounts based on the type of the account. But by using the RT and page layouts you can restrict what fields a user can see on the account but not restrict him from accessing the Account of different Type. So I would say Record types are ruled out in this case. All I can see is taking the route of VF pages and Controller to filter out the accounts and display based on the type in each VP page related to a tab or create List Views that will filter out the accounts and those views are available to the users. Instead of tabs they can select the views.