Automation 360

March 1, 2023
Legal Notices
© 2023 Automation Anywhere, Inc. All Rights Reserved.
See the list of Automation Anywhere trademarks at https://www.automationanywhere.com/trademark.

All other customer or partner trademarks or registered trademarks are owned by those companies.

The information contained in this documentation is proprietary and confidential. Your use of this information
and Automation Anywhere Software products is subject to the terms and conditions of the applicable
End-User License Agreement and/or Nondisclosure Agreement and the proprietary and restricted rights
notices included therein.

You may print, copy, and use the information contained in this documentation for the internal needs of
your user base only. Unless otherwise agreed to by Automation Anywhere and you in writing, you may
not otherwise distribute this documentation or the information contained here outside of your organization
without obtaining Automation Anywhere’s prior written consent for each such distribution.

Examples and graphics are provided only as reference information and might not match your site.
Content

Getting started with Process Discovery. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Process Discovery users. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Create Process Discovery users and assign roles. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Create your event reporting password. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Create a URL and application list. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Configure Observer activity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Create a cycle. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Classify application screens and create web applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Review Events and filter data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Select and annotate instances. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Creating groups for the process and generate a PDD. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
 Automation 360 - Getting started with Process Discovery

Automation 360
Getting started with Process Discovery
Process Discovery enables organizations to accelerate the automation of business processes and discover
the fastest path to process optimization and business ROI (return on investment). You can use Process
Discovery in various industries such as: healthcare, life sciences, and finance.

What is Process Discovery

Process Discovery is the first step in automation used to identify which processes can be automated in a
business. Process Discovery uncovers business processes by capturing user interactions with various systems
and analyzing the interactions to identify patterns. You can capture and analyze user interactions with any of
these systems:

• Enterprise solutions: ERP (enterprise resource planning), CRM (customer relationship management),
BPM (business process management), and ECM (enterprise content management)
• Personal productivity applications: Microsoft Excel and Outlook
• Terminal and virtual environments: Citrix XenApp and Remote Desktop

Why use Process Discovery

Many companies begin their automation projects with manual observation and documentation. Manual
production and review of process documentation requires interviewing business users and mapping work
flows while they are performing daily operations. This involves additional resources which can be time-
consuming for all involved. This additional effort is also subject to inaccuracies due to users behaving
differently while being monitored. As a result, many of the automation opportunities remain undiscovered.
Process Discovery uses visualization tools to view process details and metadata, and review identical
processes that differ across regions, teams, or apps.

Scalable optimization capabilities

You can use Process Discovery to identify the processes in your business that you can automate. Process
Discovery helps you:

• Capture, parse, and analyze user interactions with various systems.

• Identify and map all relevant pathways (including variations) and automatically documents the most
common workflow.
• Compare the potential ROI from automating these processes and enables Business Analysts to
accelerate automation and maximize RPA ROI.
• Convert automation opportunities into bot prototypes using the Process Definition Document (PDD)
for further development and deployment by the Automation Developer.

© 2023 Automation Anywhere. All rights reserved. 4

 Automation 360 - Getting started with Process Discovery

Process Discovery end-to-end workflow

The following diagram shows the Process Discovery end-to-end workflow for Admin, IT, and power users:

1. Set up users and assign Process Discovery roles.

2. Install Privacy Enhanced Gateway (PEG) in the On-premises Cloud to limit Personally Identifiable
Information (PII) and sensitive data capture.
3. Install Neo Sensor on multiple end-users (Observer's) machines for simultaneous process capture.
4. Verify and configure Observer data capture to ensure you only capture what you want.
5. Create cycles for event data based on groups of observers, applications used, or time frame.
6. Classify application screens and create web applications for mining.
7. Review events and filter data to identify key mining parameters.
8. Create mining runs to discover patterns and prepare for automations.
9. Map and compare workflows in data visualization tools. Prioritize processes based on ROI and select a
process for automation opportunities.
10. Select and annotate instances and create a Process Definition Document (PDD) for bot developers,
compliance, training, or process improvement.

• Process Discovery users

Learn about the various users in the Process Discovery platform and their privileges from creating
mining runs and exploring processes, to creating web applications and creating a Process Definition
Document (PDD).
• Create Process Discovery users and assign roles
As an Administrator user, you can create users and assign roles in the Process Discovery platform.

© 2023 Automation Anywhere. All rights reserved. 5

 Automation 360 - Getting started with Process Discovery

• Create your event reporting password

As an Administrator user, you can create your own password for the Event Reporting interface.
• Create a URL and application list
Learn how to create a domain list (containing the URL) and application list for data that you want to
capture or exclude on an Observers machine.
• Configure Observer activity
As an administrator, you can configure an individual Observer or a group of Observers to capture or
exclude specific sets of data from collection on an Observers machine. This topic describes how to
enable or disable the capture settings (screenshots, keystrokes, title, and keyboard) and apply this to
specific applications.
• Create a cycle
Learn how to create a cycle for each data collection and add permitted users to the cycle so they can
access the associated events for data analysis. Cycles are defined as a collection of events based on a
set of Observers during a given time range.
• Classify application screens and create web applications
You can review unclaimed browser events such as Google Chrome, Internet Explorer, and so on, to
assign them to a specific web application.
• Review Events and filter data
You can review and filter Events collected from the Observers machine to develop mining insights.
• Select and annotate instances
Before you create groups for the process and generate the Process Definition Document (PDD), you
can select and annotate instances.
• Creating groups for the process and generate a PDD
Learn how to create different groups with start and stop events, and use the groups to design a
Process Definition Document (PDD).

Process Discovery users

Learn about the various users in the Process Discovery platform and their privileges from creating mining
runs and exploring processes, to creating web applications and creating a Process Definition Document
(PDD).

The Process Discovery platform includes the following user types:

Administrator
Creates users in the Process Discovery platform and has administrative permissions to manage the
tenant, cycles, users, observers, and integrations.

Power user
Creates mining runs, explore processes, classifies application signatures, and creates web applications.
The power user does not have administrator privileges.

© 2023 Automation Anywhere. All rights reserved. 6

 Automation 360 - Getting started with Process Discovery

Discovery user
Creates mining runs and processes, and can review events.

Limited user
Can access only the Client Dashboard and assets attached by a higher permission user.

Data Review user

Selects and reviews data for all observers in the Process Discovery platform. The data reviewer user has
access only to the Review tab and Data Review page.

Create Process Discovery users and assign roles

As an Administrator user, you can create users and assign roles in the Process Discovery platform.

Procedure

1. Log in to your Process Discovery platform as an administrator.

2. Click your account initials in the upper-right corner and select Manage Users.
3. Click Create User.
The Create New User window appears.
4. Enter the first name of the user in the FIRST NAME field.
5. Enter the last name of the user in the LAST NAME field.
6. Enter the email address of the user in the EMAIL field.
This is also the unique user ID for the user.
7. In the ROLE field, click the drop-down to select a Process Discovery role for the user.
8. To select an avatar for the user, click Choose Image file.
9. Navigate to an image on your computer and click Open to select the image.
10. Click Create User.
Process Discovery automatically generates and sends an email inviting the user to log in and use the
platform.

Note: If the user does not activate the account within 24 hours of receiving the email
invitation, click the Didn't receive confirmation instructions link on the login page to
resend the confirmation email. Enter the email address in the field provided and click resend
confirmation instructions.

11. To reset a user password for a fully registered user, click Actions > Force Password Reset.
12. Click Yes to reset the user password.
A message appears notifying you that the user will have to change their password on the next login
attempt.

© 2023 Automation Anywhere. All rights reserved. 7

 Automation 360 - Getting started with Process Discovery

Create your event reporting password

As an Administrator user, you can create your own password for the Event Reporting interface.

The Event Reporting interface uses Kibana which provides you reports about how people interact with
applications and screens. Using the reports, you can determine where to focus your process discovery.

Procedure

1. To create your Event reporting password, log in to your Process Discovery platform tenant.
2. Click your account initials in the upper-right corner and select Manage Users
3. Locate your account details in the users list.

Tip: To quickly locate your account, click Filter. Enter your email address, select a role,
and click Apply.

4. In the Actions column, click the drop-down arrow and select Set Event Reporting Password.
The Set Event Reporting Password window displays.
5. Enter your password and click Set Password.
The password is ready to use the next time you log in

Create a URL and application list

Learn how to create a domain list (containing the URL) and application list for data that you want to capture
or exclude on an Observers machine.

Prerequisites

This task is performed by an Administrator. Before you configure Observer activity for data collection, you
create domain list and application list.

To create a domain list, perform the following steps:

1. Log in to your Process Discovery platform as an administrator.

2. Click your account initials in the upper-right corner and select Domain List.
3. Click Create List.
4. In the Name field, enter a name for the list.

For example, enter Business applications.

5. In the Type field, select Allow to capture URLs or Block to exclude the URLs.

Note: The blocked URLs will not be displayed in the screen shots from the Events page.

© 2023 Automation Anywhere. All rights reserved. 8

 Automation 360 - Getting started with Process Discovery

6. In the Domain field, enter the full URL address.

For example, enter www.servicenow.com, www.sap.com, or www.oraclefinancials.com.

Note: When specifying domains, you must explicitly indicate what domains to include or
exclude. For example, if chase.com is blocked, the secure05c.chase.com would not be
blocked. You must include secure05c.chase.com on the list.

7. Click Add to add the specified domain to the list.

8. Click Create List.

You can now select this Block or Allow URL list from the Observers page for data you want to capture
or exclude, for an individual observer or group observers, based on your requirements.

To create an application list, perform the following steps:

1. Click your account initials in the upper-right corner and select Application List.
2. Log in to your Process Discovery platform as an administrator.
3. Click Create List.
4. In the Name field, enter a name for the list.

For example, enter Business applications.

5. In the Type field, select Allow or Block from the drop-down.

6. In the Application field, select an application from the drop-down or enter an application in the text
field.
7. Click Add to add the application to the list.
8. Click Create List.

You can now select this Block or Allow Application list from the Observers page for data you want to
capture or exclude, for an individual observer or group observers, based on your requirements.

Note: To create a default Block and Allow URL or Application list for all new observers in
a tenant, click your account initials in the upper-right corner and select Manage Account. In
the Observer Settings section, update the URL or Application Block and Allow List.

Configure Observer activity

As an administrator, you can configure an individual Observer or a group of Observers to capture or exclude
specific sets of data from collection on an Observers machine. This topic describes how to enable or disable
the capture settings (screenshots, keystrokes, title, and keyboard) and apply this to specific applications.

© 2023 Automation Anywhere. All rights reserved. 9

 Automation 360 - Getting started with Process Discovery

Prerequisites

After the Neo Sensor is installed on the Observers machine, ensure that you:

• Enabled the sensor recording. For more information on enabling or disabling the recording, refer to
Enable and disable the users recording.
• Created your domain and application list before you configure Observer activity.

Note: To enable or disable the recordings for new observers in a tenant, click your account
initials in the upper-right corner and select Manage Account. In the New Observer Recording
section, select Enable or Disable to set the recording configuration for all new observers. Click
Save to save your changes.

To configure an individual observer or group configure observers for data collection with capture settings,
perform the following steps:

Procedure

1. Log in to your Process Discovery platform as an administrator.

2. Navigate to Data > Observers.
3. To configure all observers, select Configure <number> Observers.
This configuration is for all observers using the current filter. You can create filters for specific
departments in your organization (for example, HR or Finance) to filter data collection for a subset of
Observers. Click Filters to create filters.
4. To configure an individual observer, navigate to the Actions column for the Observer and select
Configure from the drop-down arrow.
5. In the Capture section, use the individual toggles to capture or exclude screenshots, keystrokes, title, or
clipboard globally for all applications.
6. In the URL Block and Allow List section, select one of the these options:

Option Action

None No action to select. All URLs are captured by the Neo Sensor.

Allow Select the Allow URL list you created from the Domain List page from the
drop-down field.

Block Select the Block URL list you created from the Domain List page from the
drop-down field.

7. In the Application Block and Allow List section, select one of the these options:

© 2023 Automation Anywhere. All rights reserved. 10

 Automation 360 - Getting started with Process Discovery

Option Action

None No action to select. All URLs are captured by the Neo Sensor.

Allow Select the Allow Application list you created from the Application List page
from the drop-down field.

Block Select the Block URL list you created from the Application List page from
the drop-down field.

8. In the Configure Applications window, enter specific applications in the text field you want to
capture and click Add.
Based on your business needs and the applications you set to capture or exclude, you might need to
capture Screenshots and Titles for data processing of screen signatures.
The application is listed in the Application Name column.
9. To disable capture settings for the application, select the icon for Screenshots, Keystrokes, or Titles.
An X mark appears on the icon.
10. To configure observers by a single user, or group of observers with the same user name, select Use
configuration for observers owned by this user (<user name>).
This option is available for an individual observer only.

Note: When you use this option, the allow and block list that is created for new
observers is used for users with the same user name.

11. Click Configure.

The capture settings are now set for Observers.
12. To enable the capture settings for all observers by default, click your account initials in the upper-right
corner and select Manage Account.
13. In the Observer Settings section, perform steps 5 through 7.
14. Click Save to save your changes.

Create a cycle
Learn how to create a cycle for each data collection and add permitted users to the cycle so they can
access the associated events for data analysis. Cycles are defined as a collection of events based on a set of
Observers during a given time range.

© 2023 Automation Anywhere. All rights reserved. 11

 Automation 360 - Getting started with Process Discovery

Prerequisites

Administrators have access to all event data, and can define which Permitted Users (Data Review, Discovery,
or Power user roles) can access the cycle data throughout the Process Discovery platform. The
Administrator informs users when the cycle is ready for them to review. Power users and all other non-admin
users do not have access to create their own cycles and cannot review data until the Administrator creates
the cycle for them. Creating a cycle for Power and all other non-admin users allows the users to access the
data to review events and mine for processes.
To create a cycle, perform the following steps:

Procedure

1. Log in to your Process Discovery platform as an administrator.

2. Navigate to Data > Cycle.
3. Click New Cycle.
4. In the CYCLE NAME field, enter a name for the cycle.
For example: Cycle 1: Order Entry and Processing.
5. In the PERMITTED USERS field, select the users that you want to give access to.
Permitted users include only the Data Review, Discovery, or Power user roles. You do not need to add
Admins as permitted users because Admins can access all event data.
6. In the OBSERVED AT field, select the time data range from the Start date to the End date for the set of
Observers.
7. In the OBSERVERS section, you can multi-select Observers or Observer Users from the drop-down
lists. Alternatively, you can select a tag from the Observer tag drop-down list to populate the Observers.
You can create Observer tags from the Observers page and can use them to identify a team for a
cycle. For example, the team is payroll or recruiting in HR where you can select as many Observers as
required. In a VDI environment, we recommend that you select Observers from the OBSERVER USER
section. This option enables you to easily select from hundreds of Observers and customize based on
the cycle you want to create.
8. (Optional) APPLICATION NAMES, click the drop-down list to select applications.
9. (Optional) In the START SIGNATURES, click the drop-down list to select a start signature.
10. (Optional) In the END SIGNATURES, click the drop-down list to select an end signature.
11. (Optional) In NOTES, enter any notes you want to share with the permitted users.
12. Click Create Cycle.

Classify application screens and create web applications

You can review unclaimed browser events such as Google Chrome, Internet Explorer, and so on, to assign
them to a specific web application.

When using web applications from the Process Discovery platform, the browser name is captured but the
web application or software as a service (SaaS) is not. Web application events (where the application name is
not captured) are stored in the Unclaimed Browser Events section of the Web Applications page. To classify

© 2023 Automation Anywhere. All rights reserved. 12

 Automation 360 - Getting started with Process Discovery

web application events that are related to the task or process, you must create specific web applications for
the events to be claimed in the application. From the Web Applications page, you can:

• Review events in the Unclaimed Browser Events section to locate and filter related process events from
their native browser applications. Typically, Google Search, personal searches, or web mail events are
not relevant to a task or process.
• Create specific web applications that are used in the task or overall process flow, for example: Amazon
Web Services, Slack, Zendesk, and so on.

To review events in the Unclaimed Browser Events section and create web applications, perform the
following steps:

Procedure

1. Log in to your Process Discovery platform as a power user.

2. Navigate to Data > Web Applications.
In the Existing Rules section, you will see previously created web applications. In the Unclaimed
Browser Events column, you will see various browser application events.
3. In the Unclaimed Browser Events column, click:
• Grouped by: Title to organize the browser events listed in the column by Title.
• Grouped by: URL to organize the events by URL.
4. To filter events in the column, use the data range option under the Unclaimed Browser Events header.
Select the start date (Month/Date/Year) and end date (Month/Date/Year). The events column will
update and display your results.
To filter events by specific event tiles, use the search icon. Enter the title in the search field. The events
column will update to display your results.
5. To view a browser event, click the link to view the set of events from the Events page.
The browser events with the highest frequency titles or URLs are displayed at the top of the column.
These are the most important events for processes that users are recording.

6. From the Events page, verify what web application the events belongs to.

Tip: We recommend that you note the web titles or URLs as you review the events
because you will create a web rule pattern (regular expression or regex) for each of the
targeted web applications. Additionally, you can use the Filter option to locate specific web

© 2023 Automation Anywhere. All rights reserved. 13

 Automation 360 - Getting started with Process Discovery

applications by Observer Name (for example) and click through the events in their workflow.
Based on your situation, you might filter on URLs because URLs are unique, whereas titles are
not necessarily unique. For example, if you have two applications with HOME as the title, you
should use a URL web based rule instead of the title.

7. From the Unclaimed Browser Events column, continue to review the set of browser events from the
Events page and determine if the events need to be claimed as web application events.
8. After you have located the titles or URL that you need to create web applications, navigate back to the
Web Applications page.
9. Click Create Web Application.
10. In the APPLICATION NAME field, enter the name of the application.
For example, enter Google Search ICD 10 Lookup.
11. In the APPLIED RULE TYPE section, select the rule type (Title or URL) to use.
For example, select Title.
12. In the RULE PATTERN (REGEX) section, enter a pattern that matches the title or URL of your target
application in the text box.
For example, enter icd10 lookup in the text box. We recommend that you remove "Google Search"
from the application name because there may be similar events (icd10 lookup) in other browsers that
you can also include in the rule pattern.
You can also click the copy icon to copy the title of the web application and paste into the text box.

For example, you only need the title, KTBSonline and there are two KTBSonline titles listed in the
browser events column. The two titles are:
• Verify Login Information | KTBSonline - Google Chrome
• Enroll in Open Enrollment Benefits | KTBSonline - Google Chrome
To capture the events from both titles, you can enter the rule pattern as: Verify Login Information \|
KTBSonline - Google Chrome|Enroll in Open Enrollment Benefits \| KTBSonline - Google Chrome, or
you can just enter KTBSonline and keep the rule pattern simple.
Continuing with the example for KTBSonline, the backslash (\) character precedes the vertical (|)
character to indicate that this is not an OR function in the rule.
To include more than one title in the rule pattern, use the vertical bar (|) character to indicate the OR
function. For example, to include results for PDFfiller OR pdfFiller, enter the rule pattern as: PDFfiller|
pdfFiller.
The caret (^) character is another commonly used character for creating web rules. Use the caret
character at the beginning of the rule pattern when you want to match the exact event title at

© 2023 Automation Anywhere. All rights reserved. 14

 Automation 360 - Getting started with Process Discovery

beginning of the text. For example, you want events only where KTBSonline is at the beginning of the
text in the application. In the text box, enter the rule pattern as: ^KTBSonline.
13. Click Create.
The system takes a few minutes to create the web application. To verify that the rule is updated, click
the magnifying glass icon in the Actions column. After the web application has completed, a pop-up
notification appears in the bottom left corner.

Review Events and filter data

You can review and filter Events collected from the Observers machine to develop mining insights.

Prerequisites

We recommend that you collect Observer events for at least two to five weeks to ensure that all processes
assigned to Observers are completed before data analysis. After a few weeks of collecting Events, you can
review the Events. From the Events pages, power users can:

• Review events to ensure that data is collected from Observers.

• Use the Filter option to sort and display events by single or multiple Observers, application, Observed
at (date range), and so on.
• Enlarge individual screens to view Observer events (mouse clicks and keystrokes) in detail.

To review and filter Events, perform the following steps:

Procedure

1. Log in to your Process Discovery platform as a power user.

2. Navigate to Data > Events.
3. In the upper left side, click the drop-down to select an Observer.
By default, all Observers events are displayed on the Events page.
The events collected by the Observer are displayed in the Events table. The total number of Events
collected by the Observer is displayed in the Events text box above the table.
4. Click through the event IDs to view the date range (Observed At), Application, Title, and Field columns.
Click the gear icon to select additional data to view. The selected data displays a green checkmark. For
example, you can select Screen signatures, Application, Field, and so on. The data displays in another
column within the Events table.

Note: In the Events table, the Observed At date and time range is the time that a user is
looking at the events in the application. The Observed At date range is not related to the
Observers location. For example, if the Observer is in India and the user is looking at the
events in the application in California, the Observed At date and time is in California time.

© 2023 Automation Anywhere. All rights reserved. 15

 Automation 360 - Getting started with Process Discovery

For each Event ID, the associated Event screen appears to the right. The following image and table
describe the metadata (1-4) details associated with the screen and the icons (5 and 6) used to enlarge
the image.

Metadata Description

1 Event ID The ID number associated with the event.

The exact date (Month/Day/Year) and recording time of the

2 Observed At
event captured by the Observer.

The application screen associated with that event. Each

3 Signature
application has a unique ID.

A unique label pattern applied to an application screen to

enable process mining.
Screen
4
Signature
Note: Although, Screen signatures are partially
automatic, modifications are required for data mining.

© 2023 Automation Anywhere. All rights reserved. 16

 Automation 360 - Getting started with Process Discovery

Metadata Description

As long as the Screen Signature is logical, multiple

Events may share the same Screen Signature. It is
important that Screen Signatures describe the screen
appropriately because they enable further process
mining.

When you are ready to modify your Screen Signatures work,

we recommend that you work with a Process Discovery
Business Analyst.

Image Viewer
5 Enlarges the image to full screen mode.
icon

6 Slider Expands the width of the image.

5. Click Filter to customize the events you want to view.

Filtering events allows you to better understand the individual steps as part of the overall process you
might optimize. For example, you might refer to the Field column for potential start and end tasks of
process.
6. To filter events for a cycle, select a cycle from the Cycles drop-down and Click Apply.
The Events table is updated and updates events for that cycle.
7. To filter events using a set of rules with conditions (AND, OR) or create a group (combination of rules),
select from the following options or a combination of options:

Option Action

Add Rule A Rule is single condition. Use this to add additional conditions, such as
AND, OR. Refer to the AND,OR examples for more information.

AND Filter events only which satisfy BOTH conditions will be included.

For example, the AND operator is selected and you

select Application Name = Acrobat and Application

© 2023 Automation Anywhere. All rights reserved. 17

 Automation 360 - Getting started with Process Discovery

Option Action

Type = web. The filer rules include events from both

Acrobat and web.

OR
Filter events only which satisfy EITHER condition will
be included. For example, the OR operator is
selected and you select Application Name = Chrome
and Application Type = windows. The filter rules will
include only events EITHER in Chrome or in
windows.

Add group Use this to filter for a combination of rules. A Group can also be a
collection of Groups, or a mix of both.

For example, there is a combination of Groups, each

with their own group of Rules, collected by an OR
operator. The filter rules will include events that are
either (on machine AAIComputer_7 AND in Chrome)
OR (on machine AAIComputer_4 AND in Excel).

Operators Select from one of the following operators:

Option Result

The condition is equal to the input. For

example: Application Name=Google. This filter
=
rule will include events where the application is
Google only.

The condition is greater than, or less than those

>, <
in the input. For example: ID > 1000. This filter

© 2023 Automation Anywhere. All rights reserved. 18

 Automation 360 - Getting started with Process Discovery

Option Action

Option Result

rule will include events where the ID is greater

than 1000.

Note: This applies only for

Observed At and ID conditions. The
Observed At filter is the quantity of
any event that is recorded in that
exact time.

The condition is greater than or equal to, or less

than or equal to those in the input.

>=, <=
Note: This applies only for
Observed At and ID conditions.

Note: The examples provided include some of the more

commonly used operators. The full list of operators include:
• In
• !=
• Not In
• Is Null
• Is Not Null
• Matches

8. Click Apply to apply your filter settings and view events.

Select and annotate instances

Before you create groups for the process and generate the Process Definition Document (PDD), you can
select and annotate instances.

© 2023 Automation Anywhere. All rights reserved. 19

 Automation 360 - Getting started with Process Discovery

Prerequisites

• Before you create a PDD, you create a mining run from the Mining Runs page. (Alternatively, you can
also create a PDD from a set of events from the Events page using the Import to Graph option.)
• From the Process Explorer page, review the various paths taken by the observers, where the thickest
path is the most frequent path taken.
• Identify the path you want to view from an event-level.
• Click the View in Instances Viewer icon to navigate to the Instances Viewer page where you can
select and annotate events to include in a PDD. You can also select a process to annotate directly from
the Instances Viewer page.

Procedure

1. Log in to your Process Discovery platform as a power or discovery user.

2. Navigate to Data > Instances Viewer.
3. In the upper-left side next to View Instances, click the drop-down to select a process to visualize.

4. After the process displays on the page, click the drop-down to select the instance to include in the
PDD.
5. Click the gear icon to add the Include in Process column.
The Include in Process column provides you a check box for each line order (refer to the Order
column) used to specify which steps to include in the PDD.
6. Click Annotate to update field labels for the selected steps. For all steps that you want to include in the
PDD, leave the box checked and update the action and label from the screen on the right.
Two fields will appear above the screen image.
7. From the drop-down, select a Control Type.
The Control Type refers to the selection performed in the application.
8. In the text field, enter a control label description for the Control Type and click Update.
We recommend that you enter a label description that corresponds with the label in the screenshot so
that when users review the PDD, the output makes sense to them.

© 2023 Automation Anywhere. All rights reserved. 20

 Automation 360 - Getting started with Process Discovery

For example, select Button from the Control Type drop-down and enter Click New Ticket in the
description field.
The Ann column will display user and the Field column will display the description entered in the text
field.
9. Repeat steps 6 through 8 for all steps that you want to annotate.
The Save Instance to Process button is enabled for all checked items that include both a label and
description. You must annotate all instances you want included in the process for the Save Instance
to Process button to appear.
10. Click Save Instance to Process.
The View Process Details button appears.
11. Click View Process Details to name the process.
12. In the Name field, enter a name for the process using this suggested format: 5577-21245E Instance 1
for <Mining Run><Process><Path><Instance>.
13. Click Save Process to save the process with a name.
A message appears at the bottom left side notifying you that the process is saved successfully. Click the
hyperlink to return to the Process Explorer page. You can now create groups for the events and
generate a PDD.

Creating groups for the process and generate a PDD

Learn how to create different groups with start and stop events, and use the groups to design a Process
Definition Document (PDD).

After you selected your instances, you can create groups for the events and build your PDD.

Procedure

1. Click Create Group to place the steps in different groups for the PDD.
You can create groups for tasks that are part of the process.
2. In the Create Group window, drag a step from the process workflow and move it into the Start Node.
The Start Node is the beginning of the task. For help building the group of steps as tasks in the overall
process, refer to the View Instances page for the selected screens. For example, to create tasks
related to completing fields on a checkout page, you can
• Group all steps in one group and name the group Checkout; or
• Create multiple groups for individual tasks like Add Payment in one group or add Shipping address
in another group.
3. Select the last step in the group and place the screen in the End Node(s).
The End Node(s) is the end of the task.
4. Enter a name in the Group Name text box.
5. Select a color for the group from the drop-down next to the Group Name text box.
6. Click Save to save the group.
7. Repeat steps 2 through 6 for all steps you want to group.
8. Open a new browser tab and navigate to the Process Discovery platform.

© 2023 Automation Anywhere. All rights reserved. 21

 Automation 360 - Getting started with Process Discovery

9. From the left pane, navigate to Models > Diagram Composer.

In the Browser Processes and Groups section, the instances and groups are displayed.
10. Click the + sign to add a flow box for each group.
Each flow box appears on top of the previous box. Move these boxes into a row or column. The
groups are listed in reverse order from when they were created.
11. To connect one flow box to another flow box, click the > on the side of the flow box and drag the
arrow to connect the boxes.
12. To document a process with branches, click the Decision Point.
A diamond share flow box appears in the composer.
13. In the Details window, click the pencil symbol to enter a name for the decision point.
14. Repeat steps 10 through 13 until you have completed adding flow boxes for all groups in the PDD.
15. Click Auto Layout to display any missed connections.
16. Update the flow boxes as needed.
17. To save your PDD, specify a name in the text field and click Save.
The Generate PDD button appears.
18. Click Generate PDD to start generating a PDD.
19. Select Yes or No to include an image appendix.
The image appendix includes full-sized screen shots of the steps.

Note: The default images for each step is a zoomed-in snippet of the events interaction
point.

The events interaction point is the area on the screen where the user is focused which is
typically denoted by a red circle on the screen shot.

The Process Specifications page appears and the message Generating PDD displays in the bottom left
corner.
20. Click Download PDD to open the PDD document.
The generated Word document is available from your Downloads folder on your machine. The zip file
contains all the images.
21. Review and modify the document, (if needed) and then save your PDD.

© 2023 Automation Anywhere. All rights reserved. 22