Is there any way to disable branch usage from customer decision hub portal with using OOTB functionality?
Hello dears,
I mentioned OOTB functionality in subject because I do not want to override some section rule in some ruleset to hide branches drop down. This is not a good option. Is there any option like marking particular branch as not relevant record in order to not allow them to appear on studios or portals like customer decision hub?
I would like to restrict usage of branches associated with one of pega marketing application from customer decison hub.
For instance, I would like to avoid operators who try to create segment or any rule creation allowed from customer decision hub, under branch ruleset.
Is there any way to hide branches in context part of rule creation screen from customer decision hub portal?
Regards.
Mert.
NCS Pte. Ltd
SG
Hi @m.caldag: I don't think there is a OOTB option for this.
BTW, are you trying this in DEV / test environments? If this is in test environments, ideally branches should not be deployed to test environments. If this is in dev environment, one option I cold think about is to control it with the access groups and application (not adding branches for application used by users).
Thanks.
Bentego
TR
@ArulDevan Thanks for reply. I will check that is there any privilege associated with this branch dropdown or any access group includes privilege related branch dropdown for customer decision hub. You are right. Ideally, branches must be used and then merge with actual rsv on dev environment and then start deployments on higher environments. However, there was an exceptional situation revealed.
I imported a branch on test environment for a reason. This particular change includes some other system's service request parameter change and nobody was able to confirm that this change will cover the expected scenario on target system side so that I decided to not touch actual application rulesets (like saving as rule some 99 patch version directly on test environment - that is known and general way to try things with this approach - In my opinion this is also not a good practice) on test environment till we see the behaviour of target system whether it covers scenario or not after tests. In case scenario is failed, delete branch with using "delete from system" functionality. If confirmed, merge branch to actual rsv on dev environment and restart deployment lifecycle.
Regards.
Mert.
NCS Pte. Ltd
SG
HI @m.caldag: Thanks for sharing info. In this case can you please check locking the branch (Open Branch -> Action -> Lock) solves your problem. Though the branch is listed, it will restrict creation of new rules in the branch.
Thanks.
Bentego
TR
@ArulDevan Good recommendation. I have already realised lock feature before importing and have already locked branch and then import to test environment. Btw, you are right. I checked it that even if branch locked, it still appears on branches dropdown on rule creation screen under customer decision hub. However, after selecting branch and create and saving rule itself, it is not creating any rule under branch behind the scenes and there is no error shown to user. This is another point that should be covered by platform like applying some validation rule to warn operator.
Anyways, the thing here is that this branch's ruleset has been unlocked on T time due to try something else and I guess some another team's member decided to do some work on customer decision hub and create the segment rule under this branch without awaring branch selection or wonder about it and select branch. =D It is quite funny all intersects with the same time coincidently. It's rare scenario and quite low chance to be repeated because branches are not frequently imported to test environment. Nevertheless, if branch would be imported, same scenario could be happened and better to find a way to hide it completely from customer decision hub.
Regards.
Mert.