Can anyone tell me why we need to configure the config file in Init state only? My question is like why in init state and why not in init state.
Of course, That’s what serve the purpose.
The config file we are using is to have some reusable constants and assets which can be referenced any number of times and easy to update it.
Since it’s going to be used throughout the program and all the necessary details are dumped inside that we are dumping that into our program in the init state to make it available to start processing.
Hi! Welcome back to community!
For better understanding Have a view on this thread
Because you use the config-file also for e.g. queuename, assets and/or credentials. And because of that it’s the best place to configure process-wide-settings at this point once Otherwise you can’t access credentials that you read from the orchestrator in the following ref-framework-sequence initallapplications.
Can’t we create/change its position to any other state?
You can but it won’t serve the purpose.
In Init we can process till the dispatcher.
for example: if you wants to login to the particular website by entering the credentials.
In config will store the url of the website and credentials of the person.
All these things we can stored it in the config. next the process what you wants to do next means after log in to the website these things will takes care by Next state.
So you have to use the config in init state only.