Use assets when you need to store and retrieve sensitive information securely.
Use assets for data that needs to be shared across multiple workflows or projects.
When to Use Config Files:
Use config files when you need to store the data that may change over time.
Use config files when you want to separate configuration from the workflow logic for easier maintenance and updates.
It’s common to use both assets and config files in a UiPath project. Config files can store generic settings, while assets can handle sensitive data.
You can retrieve the value to Assets from Config file by storing them in Assets Sheet. If you are storing a Credential then you must give in Settings sheet so that the particular Asset can be used.
In UiPath, assets and configuration files serve different purposes, just as in software development in general. Let’s break down their practical uses in the context of UiPath:
Assets:
In UiPath, assets are primarily used to store values that may change over time or need to be shared across multiple processes or robots. Practical uses of assets include:
Credential Management: Storing usernames, passwords, API keys, or other sensitive information securely in assets rather than hardcoding them into workflows.
Configuration Values: Storing configuration values such as URLs, file paths, or database connection strings that may vary between environments or need to be updated frequently.
Global Variables: Storing values that are used across multiple workflows or processes, such as constants, flags, or thresholds.
Dynamic Data: Storing data that needs to be accessed dynamically during runtime, such as customer information, product details, or system parameters.
Reusable Components: Storing reusable components or libraries that can be shared across projects or processes.
Configuration Files:
In UiPath, configuration files are typically used less frequently than assets, but they can still serve certain purposes:
Environment-specific Settings: Storing settings or parameters that vary between different environments (e.g., development, testing, production), such as orchestrator connection details or logging levels.
Advanced Configuration: Storing complex configuration settings that require more structured formats, such as XML or JSON files, which may include nested configurations or hierarchical data.
Integration with External Systems: Storing configurations related to integrating with external systems, such as API endpoints, authentication tokens, or service account details.
When to Use Config Files versus Assets in UiPath:
Use Assets:
When you need to store sensitive information such as credentials or API keys securely.
When you want to store values that may change over time or need to be shared across multiple processes or robots.
When you need to define global variables or constants that are used across workflows.
Use Configuration Files:
When you need to store environment-specific settings that vary between different deployment environments.
When you want to store more complex configuration data that requires a structured format like XML or JSON.
When you’re integrating with external systems and need to store configuration details specific to those integrations.
In summary, assets in UiPath are primarily used for storing dynamic or reusable data, including sensitive information like credentials, while configuration files are used for storing environment-specific settings or more complex configuration data. The choice between using assets and configuration files depends on the specific requirements and design considerations of your UiPath automation projects.