Currently we can only overwrite the New button using programmatic tools (ex. Visualforce, LWC), which is not admin-friendly at all. Luckily, besides overwriting, we can also create a new “New” button and replace the original one. All we need to do is to create a simple screen flow!
With the Fields and Section features, you can create a prettier, more flexible creation page that fits your needs better. Furthermore, this solution can even help you set up some naming convention, or bypass sharing and system constraints if needed. Doesn’t that sound exciting? Let’s check out how to make this happen!
Lulu Mobile uses standard Opportunity object to track their deals. They have two types of deals – for Existing Customers and New Customers. The team wants to enforce the naming convention as [Account Name] – [Type] – [Create Month/Year]. They also want to set a default Close Date. They want to close the deals in three months for new customers, and in one month for existing ones. Furthermore, if the opportunity is for the existing customers, they want to skip all the stages prior to Negotiation/Review.
The team doesn’t want to spend time filling in the fields that are to replace. Thus, they want to remove those fields from the creation page and let the system assign the values dynamically.
We will build a simple screen flow to achieve this by utilizing the Section and Fields features. We will also build formula resources and Decision elements to assign values dynamically. We will then build buttons and put them on List Views and Related Lists.
Note that some of the field types are not available for Fields, we have to use other components to create those fields.
Please wait while flipbook is loading. For more related info, FAQs and issues please refer to DearFlip WordPress Flipbook Plugin Help documentation.
|How to get myDomain with $API|
|How To Redirect Users When Flows Finish|
|Screen Flow||Create Records||Decision|
|Screen Element||Record Id||Assignment|
This idea occurred to me when working with Manufacturing Cloud. For some major objects (ex. Account Manager Targets), standard users have no access rights without the “View Setup and Configuration” permission (It throws cross-reference error). To resolve this, created a screen flow to run in the system context.
Does the solution solve your problem? If not, write us what your problem is and we will build the flow for you!