ed04548c-c53c-4757-8427-8bb5728a8f41.zip

The template contains 4 states:

  

1\. **Initialize** - For reading config / running initialization healthcheck. If Healthcheck pass, go to **Process**, otherwise go to **End.**

2\. **Process** - For copying files to working folder and starting your main framework/sequence, after that go to **Archive.**

3\. **Archive** - Copying working folder to archive folder, after that go to **End.**

4\. End

  

REFramework is not 100% generic (maybe apart from the Init state), it is process specific and cannot be simply migrated to other processes without changing variables/arguments (because processes have different data sources such as queues / tables / DB etc). Hence adding a generic framework allows you to separate generic steps and process-specific steps. What are the differences?

  

a. Generic steps include:

1.  Reading config file
2.  System Health checks
3.  Copying files to working folder
4.  Archiving files

b. Process specific steps include:

1.  Getting queue data
2.  Reading input file
3.  Reading DB
4.  Running main process flow

Makes use of the Initialization check activity available [here](https://marketplace.uipath.com/listings/2483).

Generic framework applicable to any process, and can be built on top of your own processes. Easy to configure.

1927c57b-fc16-4efe-abb0-7cc5f9290d83.png

MIT License Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the 'Software'), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED 'AS IS', WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

Visual Basic

26f95bf9-ff7a-48d7-a5e8-29b913e54590.pdf

Generic Framework