UiPathTeam.WpfFormCreator.Activities 0.0.6824.28668

WPF Form Creator

UiPathTeam.WpfFormCreator.Activities

Installation

UiPath Studio

Package Manager -> Right Click -> Configure Sources -> Add https://gallery.uipath.com/api/v2.

Detailed Documentation with examples for the Xaml Form Creator activity here: https://github.com/RaduPantelimon/UiPathActivities/blob/master/WpfFormCreator/XamlFormCreator.docx

Objectives:

  • Provide a possibility to launch highly customizable forms by receiving some sort of Markup file.
  • Allow the developer to dynamically initialize the values of the fields in inside the form and capture user input and use it inside workflows
  • Find a way for users to globally customize and design the workflow through a StyleSheet (basically, like an .css file for an html page)

Technical Approach:

All of the objectives above are achieved by leveraging the features of the Windows Presentation Foundation framework. This way, we can receive as input a custom Xaml (or Json) mark-up from which we can generate a Form which we can further initialize with whatever data the developer passes to our custom activity. This means that, inside our forms, we can use any type of UI element (also called controls) that we could normally use in a standard WPF form. Since the WPF library is quite extensive and provides plenty of controls and of configuration options, we can make sure that, this way, the users of this custom activity are provided with all the flexibility and customization possibilities they need.

Basically, the custom activity is designed to receive a XAML file with a Grid control as its parent element which will contain all the controls of our current page. This mark-up is passed to a WPF window and the form gets launched. The developer can optionally pass a XAML file which contains a ResourceDictionary control. This control can contain styles which will be applied to the entire form.

In order to enhance the number of possible elements in our forms, we also include the Extended WPF Toolkit in this package. Therefore, all controls in this library can be used in our forms.

This package provides some minimal visual enhancements in addition to the standard WPF look, this is done by using the MetroLight theme.

More information about this approach can be found here:

  • WPF Framework: https://docs.microsoft.com/en-us/dotnet/framework/wpf/
  • Metro Light: https://www.nuget.org/packages/Infragistics.Themes.MetroLight.Wpf/
  • Extended WPF Toolkit: https://github.com/xceedsoftware/wpftoolkit

Repository: https://github.com/RaduPantelimon/UiPathActivities

Structure:

This solution will contain several activities which will perform the same basic functionality, launching WPF forms. Them main differences between these activities are all going to have a different format for the input files (Json, XAML, etc.)
The main point to consider is that all packages using files with different formats from XAML will translate these files into XAML mark-up and use the same exact logic with the XAML Form Creator activity.

Detailed Documentation with examples for the Xaml Form Creator activity here: https://github.com/RaduPantelimon/UiPathActivities/blob/master/WpfFormCreator/XamlFormCreator.docx

Objectives:

  • Provide a possibility to launch highly customizable forms by receiving some sort of Markup file.
  • Allow the developer to dynamically initialize the values of the fields in inside the form and capture user input and use it inside workflows
  • Find a way for users to globally customize and design the workflow through a StyleSheet (basically, like an .css file for an html page)

Technical Approach:

All of the objectives above are achieved by leveraging the features of the Windows Presentation Foundation framework. This way, we can receive as input a custom Xaml (or Json) mark-up from which we can generate a Form which we can further initialize with whatever data the developer passes to our custom activity. This means that, inside our forms, we can use any type of UI element (also called controls) that we could normally use in a standard WPF form. Since the WPF library is quite extensive and provides plenty of controls and of configuration options, we can make sure that, this way, the users of this custom activity are provided with all the flexibility and customization possibilities they need.

Basically, the custom activity is designed to receive a XAML file with a Grid control as its parent element which will contain all the controls of our current page. This mark-up is passed to a WPF window and the form gets launched. The developer can optionally pass a XAML file which contains a ResourceDictionary control. This control can contain styles which will be applied to the entire form.

In order to enhance the number of possible elements in our forms, we also include the Extended WPF Toolkit in this package. Therefore, all controls in this library can be used in our forms.

This package provides some minimal visual enhancements in addition to the standard WPF look, this is done by using the MetroLight theme.

More information about this approach can be found here:

  • WPF Framework: https://docs.microsoft.com/en-us/dotnet/framework/wpf/
  • Metro Light: https://www.nuget.org/packages/Infragistics.Themes.MetroLight.Wpf/
  • Extended WPF Toolkit: https://github.com/xceedsoftware/wpftoolkit

Repository: https://github.com/RaduPantelimon/UiPathActivities

Structure:

This solution will contain several activities which will perform the same basic functionality, launching WPF forms. Them main differences between these activities are all going to have a different format for the input files (Json, XAML, etc.)
The main point to consider is that all packages using files with different formats from XAML will translate these files into XAML mark-up and use the same exact logic with the XAML Form Creator activity.

Release Notes

Form is now focused when it is started. Added "Always Top" feature for a form

Version History

Version Downloads Last updated
0.0.6824.28668 (current version) 15,755 9/7/2018
0.0.6765.36265 4,096 7/10/2018