Details about this thread
  • State Suggested Answer
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 322 subscribers
  • Views 295 views
  • Users 0 members are here
Related content from around SugarClub

Conditional tab in record layout by using Studio only

SugarCRM Support IT

Hi there,

Situation :  we want to add a RFP tab (a panel would do too) to the Opportunity layout, a tab that only needs to be visible if the RFP flag is set for that opportunity.

Searching the web for a solution I found out that Sugar Logic using the visibility attribute of the panel can handle that ,  but it would require also a .php file etc... That's beyond my capacity.

I was wondering : can it be done with only using Studio ?

Thanks for your advice,

;-)

Hugo

Parents
  • 0

    Hi Hugo,

    This method requires the "RFP Flag" to be a Dropdown (e.g., values "Yes"/"No") rather than a Checkbox, as Studio does not support layout switching based on checkboxes.

    Navigate: Admin > Studio > Opportunities > Layouts > Record View.
    Find the "Layout Determined By" dropdown at the top.
    Select "Dropdown Field".
    Choose your RFP Status dropdown field.
    Default/No: Configure the layout without the RFP tab.


    Then select "Yes" in the value dropdown, then add a New Panel (display it as a tab if your system settings allow) and populate it with your RFP fields.
    Save & Deploy.

    Hope that helps

    Vincent

    .

    CRM Business Consultant

  • 0 in reply to Vincent Amari

    Well Duh!  THANKS  - I remember the Role Based Layout option, but in the early days when I was making lots of changes it was too cumbersome to make changes to 8 or more role layouts with the same field placement change

    THANK YOU for pointing this out! 

    Bud Hartley | Cape Foulwind, NZ (and Oregon, USA)

  • 0 in reply to Bud Hartley

     to avoid making the same changes to the layout for each of the Roles we defined "Layout Roles", so I could then mass assign that Layout Role to multiple people who have different Roles and maintain one layout, say, for the whole of Sales independent on their access Roles.

    Pros: I only maintain one or two special layouts.
    Cons: We have to remember to name the Roles appropriately to indicate clearly what they are controlling, and be careful in our Role assignment.

    Similarly we have added Roles that simply Deny access to a given module, so when the majority of users need to have their Roles updated to deny access to a specific module I can just mass update everyone to add the "Deny Module XYZ" Role to them and then remove that role from the handful of people who actually should have access.

  • 0 in reply to Francesca Shiekh

    Thanks , It was about 10 years ago when I gave up on having multiple layouts and just started hiding fields and limiting access based on other factors like roles and other field values.

    It's probably time for me to rethink the implementation.

    Bud Hartley | Cape Foulwind, NZ (and Oregon, USA)

Reply Children