RPA Bot Status

The simplest way we've found so far is to have the bot call an Appian Process Model to save a status to a DB.  Then, in the SAIL of your main application, you can have a query grab rows from that table every 30 seconds, or whenever user mashes a "Refresh" button.  So, when you don't get any rows, bot hasn't started yet.  Once rows come in, they should show what step the bot just completed, assuming it started the next one.  In our design, the last thing the bot did before shutting down was send off one last status update saying it was done with everything.

The simplest way we've found so far is to have the bot call an Appian Process Model to save a status to a DB.  Then, in the SAIL of your main application, you can have a query grab rows from that table every 30 seconds, or whenever user mashes a "Refresh" button.  So, when you don't get any rows, bot hasn't started yet.  Once rows come in, they should show what step the bot just completed, assuming it started the next one.  In our design, the last thing the bot did before shutting down was send off one last status update saying it was done with everything.

I did not get your point . Will You please explain with example .

 Thanks 

From the front end, I don't now if you can demonstrate whether a bot is up and idle, or down.  You can do that from the RPA Console, but I don't know if end users can access the same info.

You can use the method I describe to show end-users what the bot just finished doing.  If it's doing things, then it's definitely up.