Advanced Consolidated Exercise
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
16-12-19 11:29 PM
Hi Bot Builders,
I am doing BP Advanced consolidation Exercise.
In the initial stage just wanted to know,"Is it really necessary to have 3 different Objects for one process?I have debugged the objects but process uses 2 different BP Objects to Launch and login.I am able to attach "BP- Basic Action Object" but when process moves to "BP-Login Object"it again detaches or opens up new Log In window.
I am thinking to club all 3 objects together to mitigate this issue but "Solution document is asking for 3 different Objects".
Please help if someone doing "BP- ACE-Create Quotes"
Regards
------------------------------
Gaurav Dhiman
------------------------------
I am doing BP Advanced consolidation Exercise.
In the initial stage just wanted to know,"Is it really necessary to have 3 different Objects for one process?I have debugged the objects but process uses 2 different BP Objects to Launch and login.I am able to attach "BP- Basic Action Object" but when process moves to "BP-Login Object"it again detaches or opens up new Log In window.
I am thinking to club all 3 objects together to mitigate this issue but "Solution document is asking for 3 different Objects".
Please help if someone doing "BP- ACE-Create Quotes"
Regards
------------------------------
Gaurav Dhiman
------------------------------
Gaurav Dhiman
RPA developer,ROM Architect
Melbourne,VIC,Australia
0413 930 960
1 REPLY 1
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
19-12-19 11:41 PM
Hi Gaurav,
The general best practice when automating a UI is to have one object per screen with Get/Set methods. However, this isn't written in stone. You're free to do as you like, but there are some reasons for this sort of granularity:
------------------------------
Eric Wilson
Director, Partner Integrations for Digital Exchange
Blue Prism
------------------------------
The general best practice when automating a UI is to have one object per screen with Get/Set methods. However, this isn't written in stone. You're free to do as you like, but there are some reasons for this sort of granularity:
- More developers can work concurrently. If someone is working on a VBO for the "orders" screen someone else can be working on a VBO for the "payments" screen.
- With more VBO's, the size of the application model for each VBO is smaller thereby allowing it to load faster and respond faster.
- A running process consumes only the actions it requires.
- If a change is made in the object layer the potential impact to the process layer is minimized.
------------------------------
Eric Wilson
Director, Partner Integrations for Digital Exchange
Blue Prism
------------------------------
