Question
Coforge Limited
IN
Last activity: 9 Mar 2017 13:08 EST
How can we restrict or delete Standard skills (eg french, english) from the skills drop down in Operator Id set up?
Hi All
I am trying to remove some unwanted OOTB skills from skills drop down. Is there anyway to do so? My pega product is PRPC 6.3 SP1.
Thanks in advance
Pankaj Sharma
-
Like (0)
fredy alexander arango prieto -
Share this page Facebook Twitter LinkedIn Email Copying... Copied!
Accepted Solution
Pegasystems Inc.
IN
- sorry Pankaj. Could be missing something... but
- seeing RULE-ADMIN-SKILL FRENCH & RULE-ADMIN-SKILL ENGLISH (instances) as available rule.
- may be we could try withdrawing as quick test
- seeing RULE-ADMIN-SKILL FRENCH & RULE-ADMIN-SKILL ENGLISH (instances) as available rule.
- or if operator should not be configured with any of the values populated from dropdown
- we could try extending the following rules
- pyRMActionPreSave
- CheckForCustomWarnings
- PreSave
- we could try extending the following rules
Pegasystems Inc.
IN
HI
i am afraid, these skills cant be deleted. Please refer this support article : https://community.pega.com/support/support-articles/unable-delete-out-box-skills
Accepted Solution
Pegasystems Inc.
IN
- sorry Pankaj. Could be missing something... but
- seeing RULE-ADMIN-SKILL FRENCH & RULE-ADMIN-SKILL ENGLISH (instances) as available rule.
- may be we could try withdrawing as quick test
- seeing RULE-ADMIN-SKILL FRENCH & RULE-ADMIN-SKILL ENGLISH (instances) as available rule.
- or if operator should not be configured with any of the values populated from dropdown
- we could try extending the following rules
- pyRMActionPreSave
- CheckForCustomWarnings
- PreSave
- we could try extending the following rules
Coforge Limited
IN
Thanks Phani
By withdrawing the rule I was able to restrict the dropdown list.
Sorry for the late reply.
Capgemini
US
Hi All,
I have the same requirement, but i am not able to restrict from the dropdown by withdrawing the rule.
@Pankaj,please let me know whether you made any other changes.
Coforge Limited
IN
In my case the requirement was: Create an activity which runs for all the operators in the application and compares their skills with the skills of the operator to select and create a pagelist of the operators who has skills same or more than the same skills as of the operator scheduling the absence.Here are the steps in the activity I wrote.
Step 1: Create a new Page where we can list all the operators eligible to work as substitute to original operator.
Step 2: Retrieve list of all the operators present in the application
Step 3.0: Loop over all the operators present in the application one by one and for each substitute operator sets the property Local.AllSkillsPresent as true and Local.IndexCount as the current index of the loop.
Step 3.1: Inner loop which iterates for each skill present for the original operator. In precondition 1 (@(Pega-RULES:Utilities).IsInPageList (OperatorID.pySkills(<CURRENT>).pySkillName,pySkillName,operators.pxResults (Local.IndexCount) .pySkills)) it checks if the operator’s skill is present in the skills of the substitute operator. If not present then set Local.AllSkillsPresent as false.
In my case the requirement was: Create an activity which runs for all the operators in the application and compares their skills with the skills of the operator to select and create a pagelist of the operators who has skills same or more than the same skills as of the operator scheduling the absence.Here are the steps in the activity I wrote.
Step 1: Create a new Page where we can list all the operators eligible to work as substitute to original operator.
Step 2: Retrieve list of all the operators present in the application
Step 3.0: Loop over all the operators present in the application one by one and for each substitute operator sets the property Local.AllSkillsPresent as true and Local.IndexCount as the current index of the loop.
Step 3.1: Inner loop which iterates for each skill present for the original operator. In precondition 1 (@(Pega-RULES:Utilities).IsInPageList (OperatorID.pySkills(<CURRENT>).pySkillName,pySkillName,operators.pxResults (Local.IndexCount) .pySkills)) it checks if the operator’s skill is present in the skills of the substitute operator. If not present then set Local.AllSkillsPresent as false.
Step 3.2: Copy the details of the valid substitute operator to OperatorsFilter page. In precondition 1 (Operators.pxResults(<CURRENT>).pyUserIdentifier!= OperatorID.pyUserIdentifier) it checks if substitute operator is not the original operator. In precondition 2 (Local.AllSkillsPresent is true) which means all the skills the original operator has is also possessed by the substitute operator.
I did this in Pega 6.2. There may be a better way to do it in PEGA 7.
Wellcare
US
We also had no luck withdrawing the rules, they still appeared in the dropdown for the users to add (we have a custom UI to display the operator update but it still used the OOB skill add). What worked for us was just copying the pySkillName property to an application rule set and then changing the UI control. We then used the Auto Complete control in the UI (pyOperatorSkillsUpdate saved to the application rule set as well) and sourced it from a report that displayed the Skills only from our application. That worked just fine.