I have a couple of questions about this control MSOFileTransferButtons.
Why is it in Pega-AppDefinition? I have a number of teams that forked the rule -- possibly because they didn't see the AppDefinition as being in the peroper "foundation" layer, like Pega-UIDesign.
Secondly, it's curious to note that MSOFileTransferButtons is flagged by the Security Analyzer. Well, the Pega version is not, but any forked version in a local ruleset is. This is a problem through v7.1.5, for those of you scoring at home.
Now, this is probably not a huge risk, since parameters to controls are always passed explictly; there's no option to pass the existing parameter page. Still, it probably should be addressed, so as not to show up by any code scanner.
The control is in Pega-AppDefinition because it was built and used for DCO at a time when Pega-AppDefinition was shipped outside of the "core four" rulesets. Of course, since then we've expanded the number of Pega- rulesets and the entire list of Pega- rulesets consists of "foundation" rules for building on Pega 7. Internally that control has not been used elsewhere so it has never needed to be migrated to a different ruleset. In fact, internally it is no longer used at all as it was built for the AP and AA wizards which are deprecated in Pega 7.
The proper UI to replace this control is a Button element with an onclick action set.
Posted: 7 years ago
Posted: 23 Mar 2016 5:37 EDT
Marije Schillern (MarijeSchillern)
Senior Knowledge Management Specialist