M
mpiscoso@gmail.com
Guest
My suggestion doesn't need for you to disable the standard new, edit, and view pages, in fact I actually use them all in the process. I posted this at another place but it might help you out as you have almost the same inquiry: Try using client-side script to redirect to the correct new, edit, and view page depending on the "type" of record. - Create multiple new, edit, and view pages. - Remove everything from the "base" new, edit, and view pages before anything else - On your "base" new page >> Add a picklist (or identifier) field. - onchange of the field, redirect the user to page 1 or page 2 depending on the "record type", sample script below: var x = rbf_getPicklistCode('picklist'); if (x == "1") window.location.href = "{!page1#URL}"; else if (x == "2") window.location.href = "{!page2#URL}"; //you can get the URL tokens in helpers, near the bottom of the 2nd helper picklist - This would mean that the "base" page would be your jump page towards the correct pages that a user needs to land on. - The same logic will be used on View Pages and Edit Pages with the slight modification of exchanging the getPicklistCode() with your identifier token (e.g. var x = "{!picklist#code}"). For view and Edit, you don't really need anything on the page except the script. The process of it is that you would always have a jump page for each type of transaction (new,view,edit) to lead the user to the correct landing pages depending on the "record type". Hope this helps you out. I'm also waiting for the said 2017 enhancement to roll-in so that we can have a no-code record type solution. Cheers!
Continue reading...
Continue reading...