MichaelD4660 Member since 2017 13 posts
Fifth Third Bank Bank
Posted: 2 years ago
Last activity: 2 years 6 months ago

The data type for Execute parameter and associated proxy is incomplete in automation XML

In our team's project, we have extracted a System.Collections.Generic.Dictionary data structure from a script component. In the parent automation, the output of the script is extracted into a proxy (see attached image "DataStructure-1a.jpg"). When trying to use this as an input parameter in another automation (see "DataStructure-1b.jpg" and "DataStructure-2.jpg"), we get an error relating to a null parameter for the dictionary. We have found by looking at the automations' XML that the type attributes seem to be incomplete compared to the original shown in images DataStructure-4.jpg and DataStructure-3.jpg, respectively. We also found experimentally, that we could get it to work by editing the XML, and completing the type attributes.

The trouble is that the "fix" is not always reliable. I suspect that it has to do with the different level of detail seen in the attributes. Sometimes the type definition is abbreviated, and sometime more complete. For example, see the following XML snippet, and image "DataStructure-3.jpg."

Value="System.Collections.Generic.Dictionary`2[[System.String, mscorlib],[System.String, mscorlib]], mscorlib"
Value="System.Collections.Generic.Dictionary`2[[System.String, mscorlib, Version=, Culture=neutral, PublicKeyToken=b77a5c561934e089],[System.String, mscorlib, Version=, Culture=neutral, PublicKeyToken=b77a5c561934e089]]"

My question is twofold: Is there a better way other than editing the XML? That can be confusing and error prone.
If no alternative exists, what are the guidelines for filling in the above attributes with the abbreviated version, versus the more complete version discussed above?

I'm using Visual Studio 2015 with the Pega plugin v. 8.0.1081

Data Integration Robotic Process Automation
Moderation Team has archived post
Share this page LinkedIn