Configure a .Net activity

  1. Add an activity to the map.

    By default, the Configuration tab is open in the properties panel of the activity.

  2. Change the default Name of the activity to something meaningful.
  3. On the Type list, select Common > .Net.
  4. Click Configure for Parameters. The Configure .Net activity dialog box is displayed.
    1. On the Assembly file path list, select a Local.Net or Store.Net and select the assembly file path. (Default: Local.Net)
      The associated class and method of the assembly is populated in the Class and Method list.
    2. If you select Load assembly using full name, the application loads a .Net object from the Global Assembly Center (GAC), using the display name of the .Net assembly object.
      • This option is available only for local assemblies.

      • For Designer running in On-premise multi-tenant and Azure environment, only existing local assemblies and assemblies from the Store are available. You cannot add new local assemblies but you can add Store assemblies.

      • If a .Net call contains classes within classes, all available levels of classes appear.

      • If the classes are recursive, only three levels of classes appear.

      • If a .Net call contains arrays within arrays, all available levels of arrays appear.

    3. Map variables to the parameters using dynamic or static values.
      • You can only provide static values for an input variable.

      • A parameter type containing a question mark (for example, Boolean?) indicates the parameter is nullable.

      • TotalAgility does not support Dynamic Complex variable mappings on more than two levels.

      • The Dynamic Complex variables are always passed as an object to the custom .Net method. For example, a String array (public boolean methodName (string[][] StringArray) as an input parameter on your custom dll does not work, as TotalAgility passes a Dynamic Complex variable as an object. Instead, use public boolean methodName (object StringArray,) and then convert the object to string[][] in your method.

      • To help transfer asset binary data, map string variables as an input or output to byte[] array type parameter. The variable must contain asset ID as value. If mapped to output variable, this value can be empty.

      • DataSet parameters are not supported.

    4. Click OK.
  5. Save the process map.
  6. Configure other properties for this activity. See Activity properties.