Select all for pre-existing rule conflicts during import
I have an enhancement request. We need a "Select All" checkbox during the import process for "Pre-existing rule conflicts". In 7.1.9 I have to tick each checkbox when importing pre-existing rules. There are 20 rows per page, and in this case I have 8 pages. It is time intensive and error prone to tick each of these 160 checkboxes; a "Select All" checkbox would solve this problem.
Sean
Pegasystems Inc.
US
Reasonable request, for internal members, you should be able to enter the enhancement request yourself: Entering Enhancement Requests in PMF.docx. Marissa Rogers, is this the right process?
Pegasystems Inc.
US
That file looks a little outdated so I'll just take care of it, Kevin Zheng!
Pegasystems Inc.
US
You're welcome! Here is your Enhancement Request: FDBK-14374
Pegasystems Inc.
US
Thanks Kevin and Marissa. Eric to answer your question, this issue appears when we are importing updates to curriculum on Pega Academy. The updates include changes to courses and lessons, but the import process says the content already exists "in a different RuleSet" which is not correct. The content is work objects that don't belong to RuleSets. The updates must overwrite the existing content so I have to tick all these checkboxes which takes too much time and is prone to error.
Pegasystems Inc.
IN
- until the enhancement is in place
- would defaulting the value of checkbox to true in private version of the section rule makes sense as a work-a-round?
- please share your comments, Thank you!
- would defaulting the value of checkbox to true in private version of the section rule makes sense as a work-a-round?
Pegasystems Inc.
IN
From long I am using the following workaround (if it helps):
1. Change pagination for the involved Grid to large Number (e.g. 1000)
2. Run a script to select ALL checkbox to true in browser console.
Updated: 17 Apr 2016 14:05 EDT
Pegasystems Inc.
US
Thanks for your reply Phani. I tried it, however the default value on the private checkout of the section was not applied during the import - so the instance was not imported.