Updated to version 1.1, see latest post below
=========
Hi everyone, i’d like to share my new workflow template. Feel free to use it and ask any questions. This is a generic template that can be used with any process and you can build it on top of your own frameworks. This is just a basic template and you can add your own steps if your own process requires it, but i want to share this because adding another framework on top of my REFramework has really saved me a lot of time when developing multiple processes for the same company
The template contains 4 states:
-
Initialize - For reading config / running initialization healthcheck (Makes use of the Initialization check activity available here.) . If Healthcheck pass, go to Process, otherwise go to End.
-
Process - For copying files to working folder and starting your main framework/sequence (you can call your own frameworks e.g. REFramework from here) , after that go to Archive.
-
Archive - Copying working folder to archive folder, after that go to End.
-
End
Why use generic framework?
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:
-
Reading config file
-
System Health checks
-
Copying files to working folder
-
Archiving files
b. Process specific steps include:
-
Getting queue data
-
Reading input file
-
Reading DB
-
Running main process flow
Benefits
- Applicable to all processes, only requires changing config file between different processes.
- Make your process more modular by adding an additional layer (to separate process-specific and non process-specific logic).
- Can be built on top of your own main frameworks / sequences.