The following diagram shows what a basic integration with Enate should look like using the Enate VBO. It should follow the logic of:
Authenticate Pass credentials to Enate and get a token, this will be used in all future calls to Enate.
Get More Work This action will return a small JSON object with details on what the next piece of work is.
Get Action This will get the full JSON object representing the piece of work assigned to the bot (assuming it’s an action)
{process object using BP commands/actions or the Enate JSON Get/Set} - this is where you are going to manipulate the JSON object before updating this back to Enate. Change status, add notes, send email etc.
Update Action This action will send the updated JSON object back to Enate for updating.
Is Work Available This last stage is to check if there is any more work for the bot to process, if there is then go back to the start to Get More Work
There are lots of different things you can do with the Enate VBO, this is one example. You could also have a process which could iterate through an excel document and create a case/ticket in Enate for each row in the document. This would not use the get more work action and would use a combination of the BP looping along with the Enate Create Ticket action. The Get more work action is used where you are asking Enate for work and you should then keep checking until there is no more work to do. The bot can then rest until it’s next scheduled time to run.
In order for you to be able to schedule the process you need have published it to the control room.
If you double click on the process information box (or right click choose properties)
Then you will get the process information windows displayed. At the bottom of this screen there is a checkbox you need to ensure is ticked:
This process will then be available to schedule in the control room.
Now head to the Control section of Blue prism which looks like this:
Right click on schedules and choose new schedule:
Now give it a name and configure how often you want this schedule to run:
After you have configured this, you’ll notice on the left in the tree there is a new task under the schedule:
Click on this task and then we need to configure the process we are going to run and what resource to run this on:
You need to drag the process onto the relevant resource:
This will then create an entry at the bottom to show this is a scheduled session:
Click the apply changes button at the bottom left to ensure the schedule is saved:
If you click on the timetable in the tree you can see that the task is now scheduled to run:
