Marketplace session

1. UiPath Marketplace

2. Speakers
Jeevith Hegde
Helse Midt-Norge IT
Senior Integrasjonsutvikler (RPA)
Andreea Stroe
UiPath
Manager, Marketplace Programs
Anuj Tiwari
UiPath
Product Program Manager

3. 3
Agenda
Introduction to
UiPath Marketplace
Building a UiPath
Marketplace component
UiPath Marketplace
Publishing Process
Q&A

4. 4
UiPath Marketplace is a web library that contains over 1600 ready-to-use automations. It serves as a resource
for users to discover, access, and utilize a wide range of pre-built automations to enhance their
automation initiatives and achieve greater efficiency and productivity.
These automations are designed to extend and complement the functionalities and use cases offered by
UiPath's core products.
In addition to code
files, users
are provided
with information on
the automation's key
features, as well as
relevant technical
details such
as product compatibiliti
es, dependencies,
demo videos, and user
guides, all of which
serve to expedite
the configuration proce
ss.
They are created
by UiPath, as well as
by third-party
contributors,
such as UiPath
partners, customers,
and
community contributor
s, making
the Marketplace a
diverse
and comprehensive re
pository of
automations that
span across various
industries and sectors.
The automations
available on UiPath
Marketplace cover a
diverse suite of popular
technologies, including
Microsoft, Google,
Oracle, and others.
The automations
on UiPath Marketplace
are carefully vetted to
ensure their quality,
security,
and functionality, throu
gh the Marketplace
Security Certification
program.
By leveraging
the automations
available
on Marketplace, users
can optimize and scale
their automation
journey without having to
build everything from
scratch repeatedly.
These pre-
built automations can be
easily integrated into
UiPath workflows, saving
time and effort in
development
and implementation.
About Marketplace

5. 5
Benefits
 Discoverability with the help of
search engines – let your automations
get discovered by users searching on
Google, Bing and other engines.
 Accessibility within UiPath Products
– users can employ your automations
directly in Studio, StudioX and Assistant.
 Free of cost – there is no cost involved
for using the Marketplace, from both
publisher and consumers standpoints.
 Global presence – UiPath Marketplace
is available globally, there are no
geographical limitations.
 Promotion – benefit from being a part
of our newsletters and Social Media
campaigns.

6. 6
Publisher Journey
Support
Building the Automation Submitting on Marketplace Marketplace Security Certification
Pick-up in demand ideas
- Search the Marketplace and identify
potential gaps or areas where there are
few automations developed.
- Check the Forum and see what are users'
needs that are not yet catered to.
- Marketplace Publishing Guidelines will
assist you in this process, as this document
help with detailed descriptions on what type
of information is required for every field in
the Create Listing form.
1 2 3
Promotion
- Make sure to announce on your Social Media
channels, Forum and other platforms about
your automations getting published.
- This can ensure visibility and increase the
consumption rates.
4 5
- Keep your automations up-to-date with the
latest UiPath product releases.
- Answer the questions users might have for you
on Marketplace or Forum.
- Incorporate users' feedback when case (reports
of issues or enhancement requests).
- Encourage users to drop a review on the
Marketplace page.
- Content Quality Checks
- Security Testing
- Functionality Testing

7. 7
Generic Themes
Generative AI /
Specialized AI
Reporting &
Analytics
Information
Exchange
Collaborative
Work
Automated
Testing
Spreadsheet
Automation
Work
Planning

8. 8
What can be published?
Product​ Category​
Studio​ Custom Activities, Connectors, Templates, Snippets,
Solutions and Tools​
StudioX Templates​
AI Center​ ML Models​
Assistant​ Ready-to-go automations​
Apps​ Solutions and Templates​
Integration Service​ Connectors​
Process Mining App Templates

9. 9
How to publish?
Title – catchy &
to the point
Follow the naming convention
as described in our Publishing
Guidelines
Summary – short &
simple
Summarize your listing in a
short phrase that will best
explain what it is about.
Overview – brief yet
detailed
Mention the business
challenge(s), use case(s), the
target audience, pain points
Features – strong
and relevant
i.e. X hours saved, X process
automated, X% cost reduction
Screenshots & Video
Add informative screenshots.
And a video proving the use
case(s) it solves while
showing the execution
Documentation
Upload user/implementation
guides with detailed how-to’s
Access a full guide here
It is important to fill in the Marketplace Create Listing form in accordance with our Publishing Guidelines.

10. Marketplace Security Certification
Program

11. 11
Standards for Quality
Important General Guidelines
High Reusability Originality Diversity Difficulty to Replicate Completeness
It is important not to
duplicate functionalities
already available in the
official/core/UiPath Team
activities in UiPath Studio or
already present on the
Marketplace unless the
automations have an
extended functionality on top
of the existing ones.
When thinking about
creating content, keep in
mind that it should be
highly reusable in the
sense that it can be used
in multiple processes and
can be easily adapted to
different cases, by a
large number of users.
It is recommended that the
automations bring
something new in terms of
use cases or a fresh
approach to the already
existing ones.
The effort required to
develop the automation
should be reasonably high
so that it cannot be
replicated easily.
The listing should cover a
large part of all the major
functionalities to automate
requirements for the
chosen Application or
Platform.

12. 12
Phases
Functionality Testing
The functionalities provided by the
automation according to the
Description and User Guide as well
as similar additional checks.
Content Quality Check
All fields in the Create Listing Form
need to be filled in accordingly to our
Publishing Guidelines.
Security Checks
Malware/malicious files, multi-
technology software analytics, security
measurement, and malicious code.
1 2 3
The purpose of the Marketplace Security Certification is to increase the level of trustworthiness of the content published on
UiPath Marketplace by introducing extra security verification checks applied to all submissions.
Marketplace Security Certification applies to all listings prior to being published on UiPath Marketplace. This program comes as
an enhancement to the previous curation process all published listings have undergone before being published on the
Marketplace.

13. 13
Resources
• UiPath Marketplace - https://marketplace.uipath.com/
• Marketplace General FAQ - https://docs.uipath.com/marketplace/automation-cloud/latest/user-
guide/faq
• Register a Profile – https://docs.uipath.com/marketplace/automation-cloud/latest/user-guide/register-
a-profile
• Marketplace Standards for Quality - https://docs.uipath.com/marketplace/automation-
cloud/latest/user-guide/publishing-guidelines-standards-for-quality-content
• Marketplace Publishing Guidelines - https://docs.uipath.com/marketplace/automation-
cloud/latest/user-guide/publishing-guidelines-how-to-submit
• Marketplace Security Certification Program - https://docs.uipath.com/marketplace/automation-
cloud/latest/user-guide/certification-program-overview
• For any questions, please feel free to reach out to andreea.stroe@uipath.com and
anuj.tiwari@uipath.com.

14. Building a Marketplace
Component
19.07.2023
jeevith.hegde@hemit.no

15. 15
Jeevith Hegde, Ph.D.
Senior Integration Developer
Automator
DIY’er
Researcher
My superpower is accelerated learning
jeevith.hegde@hemit.no

16. 16
1. Selecting the type of submission
2. Creating the component
3. Testing the component
4. Packing and documenting the component
5. Version control of component and resources
Agenda - Building a Marketplace Component

17. Selecting the type of
submission

18. 18
Monetization Platform Type of component
Selecting the type of submission
Paid
Free to use *
• One time payment
• Per usage (SaaS)
• No subscription model yet
• UiPath account required
• Per usage (SaaS)
• Depending on the license agreement *
Windows Legacy
Windows
Cross-Platform
• No forward compatibility
• Submissions closed
• Older packages need to be update
• No backwards compatibility
• Default project type in Studio
• Wider user base
• Not all standard activities are available
• Needs to be tested on all platforms
Activity
Connector
Template
Solution
Tool
• A collection of activities published as a library
project in UiPath Studio of Visual Studio
• Activities which connect to features from other
products
• A set or collection of reuseable workflows
performing a function
• An approach which solves a single defined
problem
• A collection of solutions packaged together
• This in my view is the least published type of
component in UiPath Marketplace
Snippet
• A single reuseable workflow performing a
function

19. 19
Selecting the type of submission
Monetization
Paid
Windows
Legacy
Activity Connector
Template Snippet
Solution Tool
Windows
Activity Connector
Template Snippet
Solution Tool
Cross-
Platform
Activity Connector
Template Snippet
Solution Tool
Free to use*
Windows
Legacy
Activity Connector
Template Snippet
Solution Tool
Windows
Activity Connector
Template Snippet
Solution Tool
Cross-
Platform
Activity Connector
Template Snippet
Solution Tool
Brainstorm on what you want to publish
Think as if you were the end user of your
component

20. Creating the component

21. 21
Design your activity
Creating the component
KISS (Keep it simple and short)
Each workflow / code activity
does one thing well
Make the function intuitive
User gets the necessary
details to run the component
Annotate as much as possible
Annotate arguments,
variables and
sequences/activities
Handle success and exceptions
Try-Catch is a vital.
The user then knows what
worked/failed.
Customize your activity.
Avoid use of Misc fields.
Only include required dependencies
Keep imports minimal.
Can avoid dependency
overlaps.

22. Testing the component

23. 23
Testing the component
A test-suite helps in future-
proofing your component
Avoids
«works on my machine but
fails in another»
Create once, use it when
publishing/updating many
versions
Provides feedback to improve
your component
Test each activity in isolation.
If possible using data driven
tests
Test edge cases and negative
cases
This is where you level-up
Test Suite
Replicate the end usage

24. 24
Testing the component – A library example
Nuget Package
Activity 1
Activity 2
Activity 3
Test Suite
TestCase_Activity 1
TestCase_Activity 2
TestCase_Activity 3
Creating
Component
project
Activity 1
Activity 2
Activity 3
Test
Cases
passed?
Ready for packaging
and documentation
No
Yes
Consume the nuget package
Export project as nuget package

25. Packing and documenting the
component

26. 26
Packing and documenting the component
• Provide some basic information about the activities in
the component
• Ensure you rename your version number of the package
before publishing (for example, Version 1.0.0)
• I like to include the dependencies and a short
description of the component
• If it is a library, mention the activities available as part of
the component. This can be done in the project
description if using UiPath Studio
• Create an icon for your component
• Nuget Explorer is a great tool to use to manipulate
package meta data of published/exported nuget
package
• Licensing is another aspect to be updated using Nuget
Explorer
Edit Mode (Ctrl+K)
View Mode

27. 27
Packing and documenting the component
• Keep it short and concise
• Show how the activity looks and the
required arguments
• Show a simple example output
• Provide usage suggestion to the
end user
• If there is room for user
customizations, show an example

28. 28
Packing and documenting the component
 Check project properties are updated
 Include a good description of the component and activities
packaged within it
 Remove unwanted log messages or message box
activities (before publishing in Studio)
 Check that the package name
 If publishing for a company
Company.PackageName.Activities
 If publishing from personal account
PackageName.Activities
 Update the License URL with the license you will use.
Nuget Explorer can help edit this.
 Check that the NugetPackage description contains the
dependencies as well. This will help users known what
dependencies are required before they update (in Studio)
 Write a Documentation / User Manual on how to use your
component. Detailed manual for each activity.
 Choose where you would like to save your
documentation. A user manual is a must, but in addition
you can also document using video walkthroughs.
 In a public Github repository or on a public cloud
bucket
 Create 4 to 5 images which can be used in the listing.
Remember to use high resolution images.
 My learning was to NOT use dark mode screenshots
as the Marketplace UI does not have a dark theme
Packing Checklist Documentation Checklist

29. Version control of component
and resources

30. 30
Version control of component and resources
• A component is not just a single submission file. It contains,
- Concise description and usage instructions
- Release notes
- Images
- Written documentation
- Video documentation and
- The component itself
• You will need all of the above when you try to update your component in the
future
• Versioning all the files would aid you in maintaining your component
• Possible tools to help here is Azure DevOps, GitHub or GitLab

31. 31
Version control of component and resources - Example
Resources
• All related files and folders used during the submission process
Test Suite
• Each activity will have its own TestCase
• If there are multiple sequential activities, an integration test is included
Component Project
• The workflows and logic used in the project
• This could also be a visual studio project or a PowerShell script etc.
Azure DevOps – Git Repo’s
An effective way to
maintain the lifecycle of a
component.

32. Questions?

33. Q&A

34. Thank You!