I would like to know if it would be possible to block the channel interfaces functionality so that users do not have access to: Web Mashup, Mobile, Digital Messaging, Email as is the case today with Alexa, which users are not allowed to create.
If you’re access groups are correctly configured then end users will not be able to access the channels interface anyhow. Users should never be given access to app/dev/admin studios.
I would actually like to prevent a specific group of developers from having access to this functionality. So I created a group and removed access to these classes: Data-Channel-Configuration-BotAgent, Data-Channel-Email, Data-Channel-Mashup, Data-Mobile-Application, but they can access the channels but cannot save.
I would like to know if there is a specific class that blocks access to these buttons. I couldn’t find anything about it.
Can you try to find the section where the channels are listed? There you can add the condition as given in Alexa for a group of users.
There would not be this specific section of Alexa. Alexa remains padlocked, I know that in this case the component is not installed in the application. I'm trying to manipulate the data, but I can't because it's a version that has closed the version, referring to the design and there's no way to change it. It would be in the pxGetAppViewTypes activity and the pxIsAvailable variable that is in the Java logic that sets true.
Would it be possible to manipulate this variable to false automatically after completing this design logic?
You cannot edit pxGetAppViewTypes as its Final. Though you can logically set pxIsAvailable to false in your own way, you need to trace and see if there’s any extension point available after pxGetAppViewTypes has been processed. But that is too much customization on Pega’s OOTB rules and its not recommended.
@SohamM95 Thank you very much for clarifying my doubts. I’ll leave it the way I did even restricting class access.