Table of Contents
This Wiki page introduce the concept of script group authorization for interactive script.
Script group Authorization controls user access to Interactive Scripting Editor.
- The user could assign a script to a script group.
- The user can only modify/delete scripts depending on the authorization profile of his/her user master data
The authorization object that gets checked is CRM_IC_SCR. And you can debug at class CL_CRM_IC_GRP.
Customzing and Test Scenario
1.Corresponding customizing path to define Script Authorization Groups：
T-code: SPRO-> Customer Relationship Management->Interaction Center WebClient-> Additional Functions->Define Script Authorization Groups.
2.Usage of this customizing:
In this IMG activity, you define groups that are used in determining script authorization levels in the interactive script editor. Both scripts and roles use these script authorization groups. The role determines the specific authorization level, for example, delete, for each script authorization group. Any users assigned to the role then inherits the authorizations. If you do not assign script authorization groups to scripts, then all users can see the scripts.
3. Example that we will customize and test:
Let's define script authorization groups A and B.
In the script editor, we assign our script to group B.
We assign authorization group B, with only display authorization (Activity 03, Script Authorization Group ID B for authorization object CRM_IC_SCR), for the IC manager role.
We assign our user assigned to this IC manager role with only script display authorization.
=>Then after we logon WebUI by this user and IC_MANAGER role, we will find that this user can only display the corresonding our script.
4.Customizing and test steps in detail:
1.Run T-code: CRMC_ISE_GRP to maintain the script authorization groups. (Or go to customizing path: T-code: SPRO-> Customer Relationship Management->Interaction Center WebClient-> Additional Functions->Define Script Authorization Groups.)
2.We assigned script authorization group B to our script ZLJ_bruce01.
3.We assign authorization group B, with only display authorization for the IC manager pfcg role and assign this pfcg role to our Interactive Scripting Editor user.
4.Relaunch WebUI by IC_MANAGER role and our user, open script editor and the debugged is launched at our breakpoint in class CL_CRM_IC_GRP.
5.Since in step 3 we maintained B only with display authorization(can also be seen in above debugger screen), and in step 2 we assigned script authorization group B to our script ZLJ_bruce01,
So the test user can only display script ZLJ_bruce01, and can't edit it.
Related Notes and KBAs
2267203 CRM IC: Problems when using scripting for agent guidance
2050414 CRM IC: Problems when loading IC Script Editor
Related WIKI Page