Epiplex500

Best Practice Guide

Version 10.5

(C) Epiance Software, 2020. All rights reserved. As per The Copyright Act 1957, no part of this document may
be reproduced, distributed, or transmitted in any form or by any means, including photocopying, recording,
or other electronic or mechanical methods, without the prior written permission of the Epiance, except in
the case of brief quotations embodied in critical reviews and certain other noncommercial uses permitted
by copyright law. For permission requests, write to the Epiance Software Pvt. Ltd.
.
Epiplex500
Best Practice Guide

Dos and Don’ts during Capture

1. Keep all the relevant process ready, before start capturing.
2. Use the Mouse as far as possible to navigate between fields.
3. Avoid Tab keys, Arrow keys, Page Up/Down keys, etc.
4. Avoid shortcuts like ‘F5’ for ‘New (+)’ button. Instead, click the button using Mouse.
5. To enter data in a field, click on the field and enter data.
6. Avoid any typing mistakes while entering the data. If you make a mistake, erase the data completely and
type again. You can also edit all the steps with a mistake in Process Editor.
7. Avoid entering long names. Keep data simple. It will be easier for the learner while taking the test.
8. Try to enter data on a form of logical sequence, where it is easier for the end-user to remember.
9. If the application is slow to fetch the data, wait for the screen to refresh before you do anything.
10. Avoid right-click using the Mouse.
11. Avoid dragging the Mouse (to select data).
12. If all control regions are wrong when you Capture, check if the system DPI is 100%.
13. Avoid typing to search data from the List/Drop down list.
14. Use Mouse click instead of shortcut keys to capture executing top-level menu commands. Sometimes it
still cannot capture the menu name.
15. While capturing on any application, avoid unnecessary Mouse Clicks/Keys as everything is being
recorded.
16. Wait for the system to respond to each action before the next action.
17. While capturing on Web Applications, wait for the page to load, before you move the mouse.
18. While interacting with menu items, please click each item for better capture.
19. You can temporarily suspend capture, if you need to perform other tasks which are not related to this
capture. Use the “Pause Capture” menu item from the system tray icon.
20. If you are capturing on Internet Explorer 7 or above, please set the page zoom percentage to 100%.
Otherwise, the control regions will be displaced.
21. Perform slow capture for Type text step on the browser-based application and this is common for
normal capture and browsers add-on capture.
22. To perform capture on browser add-on, launch the browser application and then start the capture.
23. If the control information in the capture file is improper after adding an extension, restart the browser
add-on or refresh the browser page and then start the capture.
24. Make sure that, the Edge browser capture starts by click on the title bar.
25. Launch the chrome application and then start the capture.
26. If the images captured with DPI change looks Blur\Shrink in Contents, it is recommended to capture the
application, based on content (User) view point.
 After entering the data in the text box, the user need to click in the DOM area before navigating to the
next page.

Process Capture Settings

1. Set the appropriate Screen Capture Area for the best result, example ‘’Full screen” mode for dual-screen
support.
2. It is good to add applications that you do not want to capture, to the Exclude Applications list. You can
do this at the “Application Filter” tab of Capture Settings. This will ensure that you don’t capture on
these applications accidentally.
3. Update the appropriate Process Summary. It reflects in the generated Documents.

2020 © epiplex500 Page 2 of 4

Epiplex500
Best Practice Guide

4. To get the best result for Process captured on Opera application running in any DPI, it is advised to hide
the side bar in Opera browser.

Repository
1. Use Different Repository while working on the different projects.

Process Editor
1. The field or button you clicked should have a Control Region around it. Redraw the region if it is not
correct.
2. Use Noise Step Rules to filter noise steps automatically.
3. Use Filter capability to delete steps manually.
4. Use Control Properties to modify the step sentence automatically.
5. If the Control Name is not user-friendly, use the Alias Name from Edit menu.
6. You can add missing steps into an existing process by using Insert Capture. Navigate to Edit 
Insert/Append Capture  Insert Capture.
7. You can use Append Capture for appending steps to an existing capture file. Navigate to Edit 
Insert/Append Capture  Append Capture.
8. Use SIM Rule Editor to create rules for automated masking.
9. User manual Masking to secure sensitive information.
10. Highlight region drawn should be saved before applying Reorder process steps.
11. After performing reorder process steps, attach exception should be performed to obtain proper process
flow.

Developer Editor
1. Use Callouts/Sticky Notes/Rollover/Text Box to add tacit knowledge and to share additional information.
2. Use Highlighter to highlight Screen Areas to explain Key information.
3. Delete unwanted steps, duplicate or captured by mistake or not useful for the end-user.
4. Use Callout Sequencing to set the sequence of multiple Callouts in a screen.
5. Use Step Duration to define time duration for steps to give enough time for viewing.
6. Enable Callout/Sticky Note region to set the accuracy of callout/sticky note placement.
7. Do not exclude System outcome steps unless you exclude the whole group. The only reason to exclude
the whole group is, if you want those steps in simulation but not in the document.
8. Review “EPSS Sentence” in Step Properties. This sentence is used in Documents.
9. Review ‘’Annotation Sentence’’ in the Step Properties.
10. If you are adding Info Steps for Scenarios/Sections in the step group, it should be the first step in the
group.

11. The icon in the Simulation Inclusion column indicates that this system outcome will be included in
the generated document. To exclude the step, click . The icon indicates that the same step will not
be included in the Simulation.
12. You can set the process information such as Introduction to the process and objectives of the module.
Navigate to File  Process Information.
13. Click on the annotation objects border area to select it.
14. Close the appropriate application while Generating Word/PPT/Excel document. Document Generation
may fail if the word/ppt/excel application is opened.
Note: For more information, refer Help Files and Training Manual.

2020 © epiplex500 Page 3 of 4

Epiplex500
Best Practice Guide

Contact Information
You can contact our customer support or technical support for any further queries, suggestions and feedback
about epiplex500 product.
Note: Please refer to the online help files, in case you need more assistance in each of the epiplex500 modules.

Customer Support:
Visit us online at https://epiplex500.com
Email us at epiplexsupport@epiance.com

Technical Support: (Helpline Number)

Epiance India/Asia Pacific Epiance Middle East/South Africa

+91 80 4178 5045 +27 105 009 785

Epiance Europe Epiance America

+44 203 514 0620 +16 46 568 6207

Epiance Software Pvt. Ltd About Epiance

Corporate Headquarters:
Epiance Software Pvt. Ltd
Maruthi Towers, 9th ‘B’ Main,
Ex-Chairman Layout, Banaswadi Main Road,
Bangalore – 560043, India
Tel: +91 80 4178 5000
Epiance is the leading provider of enterprise software that helps companies manage their IT
driven business process transformations successfully. Our products deliver a combination of
learning, performance support and process improvement capabilities that de-risk business
change and increase productivity and performance.
The copyright/trademarks of all products referenced herein are held by their respective
companies.

2020 © epiplex500 Page 4 of 4