UiPath has made great strides towards allowing developers to securely store assets and credentials in the UiPath Orchestrator while using Excel config files for any solution configuration that we might need to store or manipulate, specifically when using the REFramework. There are a few challenges that pop up when using Excel files which do have work arounds available. Developers have explored more robust, longer term, solutions to get around this with additional functionality. During this session, we hope to work through some of these solutions.

1. Configuration
Management
Andrew Harmse and Jacqui Muller

2. Methods Of Config
• Hardcoding
• Excel
• JSON files
• Assets
• SQL

3. Ever seen
any of
these
errors?

4. So what
about SQL?
Pros
Great for central storage
Allows multiple access
Auditable
Securable
Scalable
Bulk changes can be made
Cons
Not everyone is a SQL expert, especially not end users
Not very friendly on the eyes
Resource intensive
Harder to see different versions of config

5. Portal Based
Config
• Human friendly view
• Processes can be grouped
• Editable by anyone that can use a browser
• Securable – per line-item security can be applied
• Fields can be individually validated
• Gives you the potential to use the same portal for
other purposes
• Ability to display both Dev, QA and Production
values
• All the benefits of SQL

6. What do you
need?
Method to
identify the
process -
GUID

7. So how does it
work?
Studio needs to talk
to DB using unique
identifier (GUID)
Build a
library/activity to
pull config
• Could potentially
add process to
SQL, create the
GUID
DB sends back datatable with
config items
Deconscruct
datatable into a
dictionary
Same as
REFramework

9. Demo