Custom Visibility Code

RE: Custom Visibility Code

Dmitrii Mikhalchenko — Thu, 21 Sep 2023 00:52:31 GMT

Hi Jacub,

where did you locate CustomDisableTeamsLink.php file?

I have placed my custom file into custom/modules/Accounts, gave it namespace

Sugarcrm\Sugarcrm\custom\modules\Accounts

but after R&R instance get broken and error in logs:

AH01071: Got error 'PHP message: PHP Fatal error: Uncaught Error: Class "extendedSubpanelLink" not found in /home/websites/speedpanel.loadedstage.com/wwwroot/include/MetaDataManager/MetaDataConverter.php:338

RE: Custom Visibility Code

Jakub Valenta — Mon, 07 Mar 2022 12:41:05 GMT

Hello to anybody who found this article.

I've done something similar (if I got the question right) by creating custom link file:

class CustomDisableTeamsLink extends Link2 {
    /**
     * @see Link2::buildJoinSugarQuery()
     */
    public function buildJoinSugarQuery($sugar_query, $options = []) {
        if ($sugar_query->from->module_name === '<moduleInSubpanel>') {
            // disable teams
            unset($sugar_query->join[strtolower($this->getRelatedModuleName()).'_tf']);
        } else {
            return parent::buildJoinSugarQuery($sugar_query, $options);
        }
    }
}

(Don't forget to override the subpanel to use this custom link.)

The only issue is, it opens preview when clicking the preview icon.

Best regards,
Jakub

RE: Custom Visibility Code

Matthew Rees-George — Tue, 08 Jun 2021 23:34:30 GMT

Recently I've had to make some fields read only based on business rules, and the custom ACL way is definitely the way to go. It's quite an elegant framework.

Previously I've done it using client side code, but that doesn't apply to the mobile app or web client.

Note that you need to call your custom ACL 'SugarACL<whatever>' for the auto loader to pick it up.

RE: Custom Visibility Code

Dan Petersen — Fri, 04 Jun 2021 13:38:34 GMT

My apologies for not including out version of Sugar as we are on Professional. I am going to look into possible upgrading for this feature when we have more time to investigate next week. Thank you for sending this over!

RE: Custom Visibility Code

Dmytro Chupylka — Thu, 03 Jun 2021 19:23:59 GMT

Yeah, unfortunately, "The team-based permissions feature is not available in Sugar Professional" according to https://support.sugarcrm.com/Knowledge_Base/Users_Teams_Roles/Understanding_Team-Based_Permissions/ ...

Anyway, there is still a no-code solution for Pro - with some configuring efforts, but fairly working

RE: Custom Visibility Code

Dmytro Chupylka — Thu, 03 Jun 2021 19:13:34 GMT

Thank you, Nastya!
It's always a pleasure to learn from the teammates :)

RE: Custom Visibility Code

Vincent Amari — Thu, 03 Jun 2021 17:08:06 GMT

for sake of completeness, even on Enterprise, that Team 'Selected' option doesn't appear until you enable Team based permissions

RE: Custom Visibility Code

Francesca Shiekh — Thu, 03 Jun 2021 17:05:00 GMT

That explains it, thank you! :)

Looks like I had not refreshed my page and didn't see your comment on Team-Based permissions.

RE: Custom Visibility Code

Vincent Amari — Thu, 03 Jun 2021 17:02:44 GMT

hi Francesca, I don't believe Team Based permissions is an option for Sugar Professional?

RE: Custom Visibility Code

Francesca Shiekh — Thu, 03 Jun 2021 17:00:47 GMT

Interesting example, what version of Sugar are you using?

I do not see the "Selected" option on Sugar Professional and I was wondering when and where it was introduced.

thanks,
FrancescaS

RE: Custom Visibility Code

Vincent Amari — Thu, 03 Jun 2021 16:56:10 GMT

I just seen this and was about to reply the same, Team-Based permissions will solve this

RE: Custom Visibility Code

Anastasiia Gubanovych — Thu, 03 Jun 2021 16:33:26 GMT

Hi:)

Looks like Team-Based Permissions should solve this task:
Let's say - Sarah has default teams: Global (primary) and Blue (selected)

Will has default teams: Global (primary) and Red (selected)

Both they are under Role that has the following settings:

When Sarah creates Opportunity 'BLUE TEAM', this Opportunity has Teams Global (as primary) and Blue (with 'enabled additional permissions')

When I login as Will, I see 2 Opportunities on Subpanel (because in Will's Role there is 'All' access to List and Will is in Global Team), but I can't open record view from Blue Team (because in the Role there is 'Owner & Selected Teams' and neither Will is Owner nor part of a Blue Team).

And Sarah sees two Opp-s as well, but can open Opp of Blue Team:

And let's say there is Sally from the Blue team - Sally sees both Opps, but can open only the blue one:

Dan Petersen what are your thoughts on using Team-Based permission to solve this task?

RE: Custom Visibility Code

Dmytro Chupylka — Wed, 02 Jun 2021 11:35:35 GMT

Hi Dan,

Since my Integros team has experience of extending the Roles permission matrix with additional columns (including introducing Create end separating it from Edit) along with rebuilding the OOTB security model for the sake of speeding up cascade updates of hundreds of thousands of records for on-prem customers - to avoid updates of Team for very each the subordinate records whenever the parent Account gets new AssignedTo and Team - I would strongly recommend avoiding core security adjustments until it is critical for Sugar adoption and renewal.

If the purpose is to help users with their business target while keeping team restrictions in place and OOTB, let me suggest a simple no-code solution that is implemented in 2 steps:

1. Add a new custom module "Opps Digest" with Studio and relate it to Accounts as many-to-one.

2. Configure logic that would refresh the OppDigest records - with data necessary and sufficient for business decision - no extra Opp info.
For example, show in OppDigest module all open Opps regardless of the team and sales rep the Opp is assigned to.

Therefore, users could benefit from the information available for decision making while having team-restricted access to Opps via both interface and reports.

Interface for Will from BLUE_TEAM on the left and for Sarah from RED_TEAM on the right:

The example implementation:
step 1 - zip provided by Studio no-code tool - the OppDigest module (only please add relation to accounts manually via Studio)
sugarclub.sugarcrm.com/.../OppDigestModule.zip

step 2 - zip generated by Logic Builder (https://logicbuilder.integroscrm.com) no-code tool - the logic to create/update/delete OppDigest record automatically on Opp is updated
sugarclub.sugarcrm.com/.../LogicThatRefreshesOppDigest.zip

Please feel free to use the solution.
Let me know if any questions or need some logic adjustments to make the example work for your company as prod

In case you are curious about the logic configuration for create/update/delete OppDigest, here is the flowchart (please zoom in an follow the white line to read)

RE: Custom Visibility Code

Dmytro Chupylka — Wed, 02 Jun 2021 06:04:44 GMT

Record View to None might switch off access for editing for all the Opps for the Team members - neither Red nor Blue team could access to Opps even for editing their Opp records.
In addition, OOTB "Ownership" in Sugar is personal (represented by assignedTo user), not team-based, and therefore restricting by Ownership could hardly work too.
Am I wrong?

RE: Custom Visibility Code

Alex Nassi — Tue, 01 Jun 2021 22:53:08 GMT

Hi Dan,

I don't have a direct answer, but I wonder if you can disable the "Record View" role option with Team Based Permissions to achieve what you're looking to do?

From the first link above:

When "Record View" is set to "None", the module's list view displays record's names, but the names are not hyperlinked to their corresponding record views like they are for users with the View permission enabled.

This help article, https://support.sugarcrm.com/Knowledge_Base/Users_Teams_Roles/Introduction_to_Roles, may help as well depending on your familiarity with Roles.

I hope this helps!

RE: Custom Visibility Code

Dan Petersen — Tue, 01 Jun 2021 19:00:04 GMT

Hi Dmytro,

Basically exactly what you said. We need all teams to see that their are opportunities under an organization, but not allow them to click into the record if they are not part of the opportunities team (we should not be competing against the teams). Technically we could hide a few fields within the opportunity from unrelated teams, but it is my understand that if someone ran a report then the hidden fields would show on that given report.

RE: Custom Visibility Code

Dan Petersen — Tue, 01 Jun 2021 18:55:02 GMT

Thanks Francesca I appreciate you sending that over. I will have to look into this!

RE: Custom Visibility Code

Dmytro Chupylka — Sun, 30 May 2021 09:50:45 GMT

hi Dan,

Could you clarify the business purpose by describing the use case from the business perspective? That might help with the implementation options

Do you need, e.g. Blue team members to be aware of the Opp managed by the Red team so that not compete with the Red team for the same Customer?

What info specifically should help Blue team to decide not to create the Opp? E. G. product name/product category, some specific Opp contact involved, else?

RE: Custom Visibility Code

Francesca Shiekh — Sun, 30 May 2021 00:08:38 GMT

Hi Dan,

I can't think of an out of the box solution for this, but you might be able to override the teams limitations on a per-view basis limiting non team members to read-only on list and subpanel views only.

In your shoes, I would start with reviewing the acl code, and trying to reverse-engineer it:

data/acl/SugarACLParentModule.php

then seeing how Enrico Simonetti's post here:

https://enricosimonetti.com/powerful-customisations-with-sugars-acl/

can be adapted to your particular situation.

There may be something in the context variable that will tell you what kind of view you are, in which case it should not be hard to customize it based on Enrico's code.

I'll be interested to see if others come up with different ideas...

Good luck!

FrancescaS