RE -FRAMEWORK interview question

Learning Hub
, ,
1
  1. What are the modifications required if the transaction item is data table or array or list rather than a queue item?
  2. How to retry Business exception if needed in REF ?
  3. How to retry 3 times though error has occurred at init state?
    Can anyone help me with these question, please?
2

Hi @sujith_naik,
I’m pretty sure you will find these answers on forum by searching the topics about re-framework as well as I suggest to check out Academy traings and documentation.

ReFreamework is a very usefull template which includes exception handling and repeating function and understanding how it work is beneficial as well as helpful for future :slight_smile: You can do it!

3

This is a year old at this point so you probably don’t need this anymore but I’ll offer a couple of solutions, and there are many ways to answer these.

  1. What are the modifications required if the transaction item is data table or array or list rather than a queue item?

    • So the ReFramework is setup to work with a config file and a Queue item in the orchestrator. You can just rip out the Queue related stuff and insert an Excel scope type of thing or if the array is setup in a json file or something like that have the bot read that in a notepad format and import it into the process. I believe you can also just take out the Queue specific stuff and alter a section in the config file to basically target the specific file (excel, json, ets.) to open in that.

  2. How to retry Business exception if needed in REF ?

    • It is already setup to retry a business exception the REF. You may have to default the number of retries you want it to have but I believe that is more specifically tied to the System.Errors. Either way you can add a count in a variable, in the config file or individually in the Business exception section by creating a variable and have a count each time it is hit.

  3. How to retry 3 times though error has occurred at init state?

    • So the REF is setup to stop the bot when it hits an error at the init state. I’m guessing the answer they are looking for is to tie in another state variable module to make this happen but you can also just put the part of the init state into a while loop. The loop will have a boolean variable set to it to continue to run as long as the value is false. Inside of the loop the bot will do its init setup and then have a section where it checks whether it is on the correct screen you wanti t to be - if it is then you have an if statement make the boolean value exit out of the loop, if its on the wrong part then the bot will reset the process and try again and also add a counter of 1 to it (using an int variable). If the counter ever gets to 3 then it will terminate the process, just make sure before the while loop the boolean value is again reset to false and the int value set to ‘0’.

There are many ways to solve a solution to the above, mine might not be the most eloquent but its the one that make most sense to me.

5 Likes