Frd x el_arate_ea_researchtool

Information Technology
Functional Requirements Document
xELArate EA Research Tool
Revision #: 1.0
Last Revised: Sep-18-2013
PPM #: 113327
PPM Link: http://ppmprodapp1.vmware.com:8080/itg/project/ViewProject.do?projectId=63926

Requested By: WW Customer Operations
Author: Ajith Kethireddy

Error! Unknown document property name.Error! Unknown document property name.Error!
Unknown document property name.xELArate Release 1
Functional Requirement Document

Table of Contents
Table
1.
2.
3.
4.

of Contents .........................................................................................
EXECUTIVE SUMMARY ........................................................................
GOALS & OBJECTIVES ........................................................................
SCOPE ................................................................................................
PROPOSED SYSTEM SUMMARY ...........................................................

2
4
4
4
6

4.1

Business Requirements.................................................................... 6

4.2

Post November Requirements .......................................................... 6

4.3

Out of scope Requirements .............................................................. 7

4.4

Assumptions and Constraints ........................................................... 8

4.5

Risks ............................................................................................. 8
SOLUTION DESIGN ........................................................................... 10

5.1

To-Be High Level Flow ................................................................... 10

5.2

E2E Rule Execution and Result Categorization .................................. 17

5.2.1

E2E Rule Execution ....................................................................... 17

5.2.2

Result Categorization .................................................................... 18

5.3

Display and Manage Research Results ............................................. 20

5.4

Rules .......................................................................................... 28

5.4.1

Eligibility ..................................................................................... 28
5.4.1.1 To-Be Flow ......................................................................................................28
5.4.1.2 Steps .................................................................................................................28

5.4.2

Saved EA ..................................................................................... 29
5.4.2.1 To-Be Flow ......................................................................................................29
5.4.2.2 Steps .................................................................................................................29

5.4.3

Orders ......................................................................................... 31
5.4.3.1 To-Be Flow ......................................................................................................31
5.4.3.2 Steps .................................................................................................................31

5.4.4

DUNs .......................................................................................... 34
5.4.4.1 To-Be Flow ......................................................................................................34
5.4.4.2 Steps .................................................................................................................35

5.4.5

Cases .......................................................................................... 35
5.4.5.1 To-Be Flow ......................................................................................................35
5.4.5.2 Steps .................................................................................................................36

5.4.6

Quotes ........................................................................................ 37
5.4.6.1 To-Be Flow ......................................................................................................37
5.4.6.2 Steps .................................................................................................................37

5.4.7

Contacts ...................................................................................... 39

5.

VMware

CONFIDENTIAL

Page 2 of 69

Error! Unknown document property name.Error! Unknown document property name.Error!
Unknown document property name.xELArate Release 1
5.4.7.1 To-Be Flow ......................................................................................................39
5.4.7.2 Steps .................................................................................................................39
5.4.8

Addresses .................................................................................... 41
5.4.8.1 To-Be Flow ......................................................................................................41
5.4.8.2 Steps .................................................................................................................41

5.4.9

Email Domain ............................................................................... 42
5.4.9.1 To-Be Flow ......................................................................................................42
5.4.9.2 Steps .................................................................................................................42

5.4.10

Company Master........................................................................... 44
5.4.10.1 To-Be Flow ......................................................................................................44
5.4.10.2 Steps .................................................................................................................44

5.4.11

Normalized Name ......................................................................... 46
5.4.11.1 To-Be Flow ......................................................................................................46
5.4.11.2 Steps .................................................................................................................46

5.5

Retrieve and Manage Saved EA Relationships ................................... 47

Wireframe-IB-ELA-14 ................................................................................ 47
............................................................................................................... 49
Wireframe-IB-ELA-15 ................................................................................ 49
Wireframe-IB-ELA-16 ................................................................................ 50
Wireframe-IB-ELA-17 ................................................................................ 53
5.6

Application configuration ............................................................... 55

5.6.1

Setup Rules ................................................................................. 55

Wireframe-IB-ELA-18 ................................................................................ 55
5.6.2

Setup Profiles ............................................................................... 58

Wireframe-IB-ELA-19 ................................................................................ 58
5.6.3

User Preferences .......................................................................... 59

Wireframe-IB-ELA-20 ................................................................................ 59
5.7

Tracking & Omniture Requirements ................................................. 60

5.8

System Diagrams & Architecture .................................................... 61

5.9
Appendix
Appendix
Appendix
Appendix
Appendix
Appendix

VMware

Business Intelligence (BI) & Reporting Requirements (optional) .......... 64
B: Document Change History ...................................................... 65
C: Open and Closed Issues.......................................................... 65
D: Glossary/ Definitions ............................................................. 67
E: Related Documents/References ............................................. 67
F: Project Team .......................................................................... 67
G: Review and Sign-off ............................................................... 69

CONFIDENTIAL

Page 3 of 69

Error! Unknown document property name.Error! Unknown document property name.Error! Unknown document
property name.xELArate – EA Research Tool
Page 4 of 69

1. EXECUTIVE SUMMARY
The EA research tool’s purpose is to assist users in determining which EA’s belong to a ‘customer’.

Multiple VMware teams, partners, and large customers routinely expend effort to research which EA’s belong to a
given customer.
Today, several internal/externally facing EA lookup tools exist, but they all require users to enter imprecise search
criteria (name or email domain) and then use their knowledge of VMware data and business rules to try and
interpret the customer  EA relationships.

This has proven to be, at best, inefficient; and at worst inaccurate and error prone. In the IB ELA project (which is
sponsoring this tool), almost 20% of the IB ELA quotes undergo revisions due to inaccurate list of EA’s supplied for
the IB pull. In addition, teams such as GSS licensing routinely spend multiple hours assisting the field with EA
research on quotes where the customer is questioning the IB listed on the quote.

2. GOALS &OBJECTIVES
The EA research tool will be designed to emulate much of the expertise that a VMware expert would employ to
determine an accurate customer EA list. The end result will be that VMware teams involved with manual EA
research and eventually Partners and Customers will have a tool that will significantly optimize this effort.

The new EA Research tool will:

1) Automatically research VMware data sources to gather a list of potential EA’s associated to the ‘customer’.
2) Automatically evaluate and prioritize those EA’s to rank the EA’s which are most likely associated to the
customer. Also allow the user to adjust those EA’s based on customer interaction.
3) Save the results for future use, so that subsequent EA research needs for that customer will be minimized.

3. SCOPE
Description
In Scope
EA research tool (launch-able from VMStar, BI
Dashboard, Admin Portal as well as standalone)
to produce a prioritized list of EA’s associated to
that VMStar account/that EA.

Comment

Integration of VMStar, MyVMware, and Oracle
and other data sources to be used in the
research.

One tool searches all data sources

Integration with the new customer master

EA Research tool will leverage the EA

VMware

CONFIDENTIAL

Page 5 of 69
system.
Functionality to save/manage EA relationships to
support future transactions.

Ability to select EA’s to launch the new one-click
view (Quotable Assets View) to display all
products that are quotable along with their
details
Out of Scope – 1st release (November)
EA data cleanup

relationships stored in that system.
Allow different business functions to manage
their EA/customer relationships (Support, Sales,
Partner, or VMware corporate, each may have a
different view of the EA to account relationship.)

Data errors, EA merge/split tools, and EA
governance will not be impacted by this project.

Feedback to Customer Master on changes to
customer hierarchy based on saved EA
relationships.

This is an important activity, but will need to be a
process created under a separate initiative.

Partner, customer implementations

The tool will be designed to anticipate
customer/partner usage, but this will not be
implemented in phase 1.

VMware

CONFIDENTIAL

Page 6 of 69

4. PROPOSED SYSTEM SUMMARY
4.1 Business Requirements
Link to BRD
:https://vmshare.vmware.com/it/pmo/Tier%201%20Project/IB%20ELA/Shared%20Documents/1.%20SD
LC%20Documents%20-%20Release%201/1.%20Define/BRDs/IBELA_BRD-EA_ResearchTool_v1.2.docx
Note : All requirements otherwise called out in section 4.2 or 4.3 will be delivered for November

4.2 Post November Requirements

BR #

6.01

Description

Application Setup/Configuration

Comments

Even though application configuration (setup
rules, setup profiles) is documented in the FRD.

User Preferences

This may not be delivered for November and
hence for any changes that are required, we
would need to work with IT (pre and post
production) to make any configuration related
changes.

6.17

Categories: Company Master, Saved EAs, DUNS, etc

Need further analysis of the details that need to be
shown for each category and then find a viable

Users can click/hover on any match criteria to drill down

solution that is not complex and does not require

into the rule/data that is involved in making the match.

the maintenance of huge set of individual rules to
be stored.

6.12

A.1.1.1

Note (System Generated)

The following items in this requirement
need complex logic to be built and
hence will be delivered in the next
releases.

Contains a note that the system generates using specific
rules. The intent of this note is to give advice to users about
which may help the user determine the overall usefulness
of the EA.

VMware

CONFIDENTIAL

√ If there have been any merges, or LATF‟s for
the EA; display LATF (IN) for licenses transferred
in; display LATF out (if licenses were transferred
out).

Page 7 of 69

Logging of Rule Matching Process

A.1.1.2

Will need detailed requirements from Biz
. Some of it is available, will need to
build few more and find the right
database to host this data without
impacting performances

Application that can take an admin user step-by-step for

Will need detailed requirements from Biz and then
analysis of these requirements to

each sub-rule

4.3 Out of scope Requirements

BR #

1.05

Description

One-click view (Refine Results)

Comments

Will not be fulfilled as written here. We no longer
have „One click View‟. A link to EA research tool
be available to be launched from „Quotable assets

When the user has used the one-click view to display IB,
they should be able to invoke the EA Research tool to help

view‟. Just a simple link to EA research tool with a
blank state.

refine results.

4.2.1

Hoovers : It would be desirable if there could be a search of

Based on the feedback, Hoovers is a subsidiary of

the Hoover‟s data to determine any other subsidiary/parent

D&B and helps in analyzing the D&B data. As we

names associated with the VMStar Account or EA.

are already using D&B data and using our own
analysis in creating a VMware hierarchy, the
thought is that this might not be needed. If proven
otherwise, we will need to buy new hoovers
license and use it in future enhancement

4.10.1

License Key : Supplied license key matches EA number.

This is no longer required based on the other rules
that are being run and the direction that research
is based on either an Account ID or an EA number

Ability to View and Manage Saved EA relationships in

View and managing Saved EA‟s will be available

VMStar.

7.03

thru the EA research tool. User can click on the
tool button in VMStar and see the Saved EA

VMware

CONFIDENTIAL

Page 8 of 69
relationships

7.07

Users can change the status of the saved EA

relationship when opportunity status is changed.

6.12

(VMStar) System prompts sales rep to confirm save EA

relationships as required thru the tool

Note (System Generated)

The following items in this requirement cannot be
fulfilled as ACF‟s / iACF‟s are attached to the case
and not to the EA itself.

Contains a note that the system generates using specific

√ Display any information if the EA contains
ACF‟s, iACF‟s, non-std LATF.

rules. The intent of this note is to give advice to users about
which may help the user determine the overall usefulness
of the EA.

4.4 Assumptions and Constraints

BR #

Comments

VMSTAR Normalized Name equals EA Name Normalized

Company master currently does not maintain a EA

Name

4.8.1

Description

normalized name and hence a workaround of using
the normalized name of the parties that form the
EA will be used.
Hence the requirements in 4.8.3 & 4.8.4 will not
performed as well as these will no longer be
required.

4.5 Risks
Requirement
Single Sign-On from BI,
A.1.1.3
SFDC to EA research tool

VMware

Issue
Single sign-on capability is being evaluated
A.1.1.4
and has not been confirmed yet

CONFIDENTIAL

Impact
Users will need to sign-on to the EA
research tool again from these invocation
points using Horizon / VPN

Page 9 of 69
Address Rule

VMware

A.1.1.5

DEV has performance concerns on running of
A.1.1.6
this rule as this involves string based matching.
They would evaluate this rule during the
implementation phase. If it comes out to be a
big SLA, we will have to remove the rule.

CONFIDENTIAL

This is a Deep rule and „Want‟ from biz. At
the same time the number of EA‟s that
this might independently produce (other
than UUID / DUNs / Company Master
rule) are minimal and hence the risk would
be acceptable

Page 10 of 69

5. SOLUTION DESIGN
5.1 To-Be High Level Flow

SFDC
(Account,
Account Plan,
Opportunity,
Vmstar Tab

BI Dashboard

Yes

User enters
additional
account
names or
EA’s as
search
criteria (if
required)

New EA
Research
Portal

Initiate research
to gather EA’s
based on Saved
EA , Order/
Bookings,
Contacts, E-mail
Domain,
Normalized
Names,
Company
Master , etc

User shown EA’s
in groups of
strong match,
probable,
possible along
with the criteria
that was used
find this (match)
the EA

FR Number

FR Description
The following are the various ways a user can access the IB-ELA Research Tool
1)
2)
3)
4)
5)
6)
7)

User selects 1
or more EA’s
and selects
‘Show
Quotable
Assets’

Punch out to BI
dashboard as a
single sign-on. Pass
EA’s selected to BI.

End

XXVM

EDW

VMStar Account page
VMStar Account Plan page
VMStar Opportunity
VMStar Tab
BI Dashboard
Admin Portal
Standalone portal – Currently accessible to internals only

Wireframe-IB-ELA-01

VMware

No

User can
save the
results

Admin Portal

FR-IB-ELA-01

Need to
search for
additional
EA’s

CONFIDENTIAL

BR Number
1.01, 1.02,
1.03, 1.04,
1.05, 1.06,
1.07

Page 11 of 69

Wireframe-IB-ELA-02

Wireframe-IB-ELA-03

Wireframe-IB-ELA-04

VMware

CONFIDENTIAL

Page 12 of 69

Wireframe-IB-ELA-05

FR Number
FR-IB-ELA-03

FR-IB-ELA-03.1
FR-IB-ELA-03.2

FR-IB-ELA-03.3

FR-IB-ELA-03.4

FR-IB-ELA-03.5

FR-IB-ELA-03.6

FR-IB-ELA-04

FR-IB-ELA-04.1

VMware

FR Description
For the Account detail page layouts that are associated with record type “End
Customer Accounts”, add a new button called “EA Research Tool” as shown in
Wireframe-IB-ELA-01
In the Account Plan detail page add a new button called “EA Research Tool” as
shown in Wireframe-IB-ELA-02
For the Opportunity detail page layouts that are associated with record type
“Managed Sales Opportunity”, add a new button called “EA Research Tool” as
shown in Wireframe-IB-ELA-03
Create a tab in VMSTAR called “EA Research Tool”. The tab should be visible to
all profiles in VMSTAR. Include the tab in the “Sales” and “Call Center” app to
provide easy navigation for the sales users.
In the new BI Dashboard that is specific for „Quotable Assets‟, add a new link
called „EA Research Tool‟. This will be available in all the 4 tabs available. Check
Wireframe-IB-ELA-04 for details
In the EA detail page of admin portal, a new button called „EA research Tool‟ would
be available for all users that can access the page. Check Wireframe-IB-ELA-05
for details
Users should have the capability to go to the EA research tool directly. All internal
users that currently have AD access will be able to login using their existing AD
credentials
When users click on the “EA Research Tool” button from any of the launch points,
the tool will be launched in a new window.

BR Number

The following information should be provided to the EA Research Tool if launched

1.01, 1.02,

CONFIDENTIAL

1.01

1.02
1.03

1.06

1.04, 1.05

1.07

1.0

1.01, 1.02,
1.03, 1.04,
1.05, 1.06,
1.07

Page 13 of 69
from VMSTAR
1. User ID of the user launching the tool

2.
3.
4.
5.
6.

FR-IB-ELA-04.2

1.03, 1.06

First/Last Name of the user
SFDC profile Name of the user
Name of the SFDC Account from which the tool was launched
Customer ID of the SFDC Account from which the tool was launched
Opportunity ID if launching from Opportunity page

Note: Technical team should evaluate to integrate the portal page in vmstar within
an iFrame with the SFDC tabs at the top and the sidebar to the left and the SFDC
footer at the bottom.
from BI Dashboard

1.04, 1.05

2. First/Last Name of the user
FR-IB-ELA-04.3

from Admin Portal

1.07

2. First/Last Name of the user
3. EA Number from which the tool was launched
4. EA Name from which the tool was launched
FR-IB-ELA-05

Access to the EA lookup tool is restricted to users that currently have access toVMStar, BI

8.02

Dashboard, Admin Portal
No additional restrictions needed. Anybody that has the link from the source
system (Admin Portal, SFDC, BI Dashboard) will have access to the EA research
portal.
For internal users, there is no restriction once you can access the system. All data
will be available.
Note : Could leverage AD group for this
FR-IB-ELA-06

FR-IB-ELA-07

User should not be asked to sign-in again (single sign-on) if they are accessing the EA
research tool from any of the launch points
Note : Single Sign-on is not possible for Admin Portal as it uses a different type of
technology for deriving access than others and hence will require the additional sign-on
A xELArate profile would be attached to each user that is logging into the EA research tool.
This will be determined based on the SFDC Profile to xELArate profile mapping that will be
created.
When a user logs in, we would check if they have a SFDC profile and if yes, we would find
the related xELArate profile from the mapping table and assign as the user profile. If an
SFDC profile does not exist for the user or if a SFDC profile to xELArate profile mapping
does not exist or if a SFDC profile to xELArate profile mapping exists but rules are not
defined , then the we will default to „Others‟ (default) profile
We need to derive the same xELArate profile consistently irrespective of where they are
logging in. ex : SFDC, BI Dashboard, Admin Portal, Standalone
Current values for xELArate profile are 1) Sales 2) GSS / License Compliance 3) Renewals
4) Others
Note: An initial load of SFDC profile to xELArate profile will be required.

VMware

CONFIDENTIAL

1.01, 1.02,
1.03, 1.04,
1.05, 1.06,
1.07

6.02

Page 14 of 69

Wireframe-IB-ELA-06

FR Number
FR-IB-ELA-02

FR Description
When launching the tool from any of the following pages, the VMStar Account-ID +space
+VMStar Account Name that the user started out from will be defaulted and can be
deleted from the listif the user chooses to
1)
2)
3)

FR-IB-ELA-02.1

FR-IB-ELA-02.2
FR-IB-ELA-08

VMStar Account page
VMStar Account Plan page
VMStar Opportunity

When launching the tool from Admin portal, the EA Number+space +EA Name that the
user started out from will be defaulted and can be deleted from the list if the user
chooses to
Information that pops up on a hover will be provided where an „i‟ icon is shown and a link
to a KB article will be required where ever a „?‟ is shown
Once the user lands on the EA research tool, they can enter additional VMStar Account
ID‟s or EA Numbers by using on the „EA/VMStar Account Lookup‟ only. User cannot
enter an input parameter directly.
Clicking on the „EA/VMStar Account Lookup‟ button will open an overlay where the user
can enter search criteria like order number, contract number, license key, party name,
etc to find additional VMStar account-ID or EA‟s that can then be used as input criteria to
perform the research itself

VMware

BR Number
2.01

CONFIDENTIAL

2.02

6.0

6.05, 6.07

Page 15 of 69

Wireframe-IB-ELA-07

FR Number
FR-IB-ELA-08.1

FR-IB-ELA-08.2

FR Description
The top of the page will have the following labels
„Add additional Account EA Names to be Researched‟ and next to that will be an
additional label „Use if there are additional subsidiary name(s) to be added or if the
initial EA research is missing EA‟s‟
A new lookup with the label „Search Criteria‟ will be available. This LOV will contain the
following fields and will provide results related to a VMStar Account or EA
VMStar Account
1) VMStar Account Number
2) VMStar Account Name
EA
3) EA Number
4) EA Name
5) Sales Order Number
6) License Key
7) Contract Number
8) EA SU/PC Domain
9) Party Name
10) EA User Domain
11) Instance Number

FR-IB-ELA-08.3

FR-IB-ELA-08.4

VMware

User should be able to select one of the above search criteria
User should be able to enter an alpha numeric value including special characters in the
search string field and click on the „Search‟ button (enabled only if „Search Criteria‟ ,
„Search String‟ and minimum 3 characters without counting the „%‟ are entered)
If user selects the search criteria of „VMStar Account Number‟ and provides a string
related to that, then clicking on the „Search‟ button will search SFDC for an account
number that matches the VMStar Account Numberprovided and returns the VMStar

CONFIDENTIAL

BR Number
6.07

2.04, 2.05,
2.06, 2.07,
2.08, 2.09,
2.11

2.04, 2.05,
2.06, 2.07,
2.08, 2.09,
2.11
2.03

Page 16 of 69
Account Number and VMstar Account Name related to that.

FR-IB-ELA-08.5

FR-IB-ELA-08.6

FR-IB-ELA-08.7

FR-IB-ELA-08.8

FR-IB-ELA-08.9

FR-IB-ELA-08.10

FR-IB-ELA-08.11

An exact search will be made for the input provided
If user selects the search criteria of „VMStar Account Name‟ and provides a string
related to that, then clicking on the „Search‟ button will search SFDC for account names
that match the VMStar Account name provided and returns the VMStar Account
Number and VMstar Account Name for each of the matches found.
User can include „%‟ to perform a wild card search. Minimum 3 chars (not counting %)
are required for search.
If user selects the search criteria of „EA Number‟ and provides a string related to that,
then clicking on the „Search‟ button will search EMS for an EA that matches the EA
number provided and returns the EA Number and EA Name related to that.
If user selects the search criteria of „EA Name‟ and provides a string related to that,
then clicking on the „Search‟ button will search EMS for all EA‟s that match the EA
name provided and returns the EA Number and EA Name for each of the matches
found.
If user selects the search criteria of „Sales Order Number‟ and provides a string related
to that, then clicking on the „Search‟ button will search EMS for an EA that is related to
the sales order number provided and returns the EA Number and EA Name related to
that.
If user selects the search criteria of „License Key‟ and provides a string related to that,
then clicking on the „Search‟ button will search EMS for an EA that is related to the
License Key provided and returns the EA Number and EA Name related to that.
If user selects the search criteria of „Contract Number‟ and provides a string related to
that, then clicking on the „Search‟ button will search EBS for an EA that is related to the
owner party of the contract number provided and returns the EA Number and EA Name
related to that.
If user selects the search criteria of „EA SU/PC Domain‟ and provides a string related to
that, then clicking on the „Search‟ button will search EMS for all EA‟s where the super
user or procurement contact have the same domain as the domain provided and
returns the EA Number and EA Name related to that.

2.03

2.03

2.03

2.04

2.05

2.06

2.07

FR-IB-ELA-08.12

If user selects the search criteria of „Party Name‟ and provides a string related to that,
then clicking on the „Search‟ button will search EBS for parties that match the party
name provided and returns the EA Number and EA Name for each of the matches
found.

2.08

FR-IB-ELA-08.13

If user selects the search criteria of „EA User Domain‟ and provides a string related to
that, then clicking on the „Search‟ button will search EMS for all EA‟s where atleast 1
user has the same domain as the domain provided and returns the EA Number and EA
Name related to that.

2.09

FR-IB-ELA-08.15

If user selects the search criteria of „Instance Number‟ and provides a string related to
that, then clicking on the „Search‟ button will search EBS for an EA that is related to the
owner party of the instance number provided and returns the EA Number and EA Name
related to that.

2.11

VMware

CONFIDENTIAL

Page 17 of 69

FR-IB-ELA-08.16

FR-IB-ELA-08.17

All the results will be shown in the space available and user should be able to scroll up
or down to see the full results. User should then be able to select one or more EA‟s or
Accounts from the results using the check boxes available in the beginning of each
record. A select All check will also be available that selects all the results available.
User should be able to click on the „Add‟ button (only enabled if atleast 1 record is
selected) to move the selected records to the right and into the appropriate section. If
the results are related to an Account Name & Number then they will be moved to the
„VMstarAccount Numbers to be researched‟ section and if the results are related to an
EA Name & Number then they will be moved to the „EA Numbers to be researched‟
section

6.07

6.07

Each record on the right hand side will be displayed as a single column using the
Number + Space + Name format

FR-IB-ELA-08.18

FR-IB-ELA-08.19
FR-IB-ELA-08.20

FR-IB-ELA-08.21

A maximum of 15 records can be added to each section
Each record on the right hand side will be individually selected or multiple records can
be selected by using the Ctrl or Shift keys. Once selected, the records can be removed
from the right hand side by clicking on the delete button at the bottom.
User should be able to enter a different search criteria and search for new set of results
to be added to the research list
Once the research list is finalized, user can either click on the „Cancel‟ button which will
close the overlay and does not take any of the EA‟s or Accounts selected to the
research page.
User can click on the „Ok‟ button to close the overlay and take the EA‟s or Accounts
selected to the research page. The list of EA‟s or Accounts selected will be added to
any existing list of research parameters already available.
If the total count of EA‟s or Accounts exceeds 15 then the following error message will
be shown at the top of the page.

6.07

6.07
6.07

6.07

„You have reached max. limit count of 15 for EA. Please remove and submit.‟

FR-IB-ELA-09

FR-IB-ELA-09.1

The user can then select and delete any additional records.
The first Account ID or EA Number entered (or defaulted) will be marked as the primary
(denoted with an asterisk next to it). This will then be used as key for saving the results.
User should have the capability to change the primary to any of the input parameters
entered.
User should have the capability to select between the standard and deep option based
on a radio button. By default, the standard option will be selected.

2.02

3.02

If „Standard‟ is selected, only those match rules / match sub-rules that are marked as
standard will be run

FR-IB-ELA-10

FR-IB-ELA-11

If „Deep‟ is selected, all match rules / match sub-rules that are marked as „Standard‟
and „Deep‟ will be run. Basically all the rules that are enabled for the profile will be run.
Once the required input criteria (Account-ID‟s or EA Numbers) are entered, user should
be able to click on the „Research Accounts‟. This button is only enabled when atleast 1
account-id or EA number is entered.
A spinning wheel or loading icon should be shown in the results section from the time
user clicks on „Research Accounts‟ to the time the actual results are shown.

5.2 E2ERule Execution and Result Categorization
5.2.1 E2E Rule Execution

VMware

CONFIDENTIAL

6.06
3.03

Page 18 of 69

Collect EA’s
and their
strengths using
Saved EA rules

Collect EA’s
and their
strengths using
DUNS rules
Collect EA’s
and their
strengths using
Email Domain
rules

Collect EA’s
and their
strengths using
Order rules

For all
Account ID’s /
EA Numbers
provided as
input

Collect EA’s
and their
strengths using
Case rules

Collect full list of
EA’s found so far
using standard rules.
Use the input
parameters as well

Collect EA’s
and their
strengths using
Company
Master rules

Collect EA’s
and their
strengths using
Quote rules

Collect all EA’s from
standard rule &
cumulative rules as
a single list along
with match criteria
and strengths

Run
categorization
rules for each
EA

Show results
on portal

Collect EA’s
and their
strengths using
Normalized
Name rules

Collect EA’s
and their
strengths using
Contacts rules

Collect EA’s
and their
strengths using
Address rules

FR Number

FR Description

FR-IB-ELA-13

For all Account-id‟s or EA numbers provided, first run the following standalone rules and
their sub-rules if enabled and collect EA‟s that are match the criteria along with the strength
(strong or weak)

FR-IB-ELA-14

FR-IB-ELA-15
FR-IB-ELA-16

1) Saved EA
2) DUNs
3) Orders
4) Cases
5) Historic Quotes
6) Contacts
7) Address
For the EA‟s gathered thru the above rules and the Account id/s or EA numbers entered as
input, run the following cumulative rules and their sub-rules if enabled
1) Email Domain
2) Company Master
3) Normalized Names
Collect the full list of unique EA‟s from the standard rules and cumulative rules as a single
list along with strengths and other attributes
For each EA in the list determine the category that the EA should be listed in based on the
below rules

5.2.2 Result Categorization

VMware

CONFIDENTIAL

BR Number
4.0

4.0

4.0
5.01

Page 19 of 69

For each unique EA
collected based on
all matching rules,
perform the next
steps

Is the EA matched
based on (Saved
EA Relationship or Domain
Match or Normalized Name
Match or Customer Master)
and strength = S

Yes

No

Is the EA match
strength = S in
atleast 1 other
matching rule

Yes

Categorize
EA as
‘Strong
Match ’

No

Is the EA match
strength = S in any
3 matching rules

Yes

No

Is the EA match
strength = S in any
2 matching rules

Yes

No

Is the EA match
strength = S in 1
non-transaction
matching rule

Categorize
EA as
‘Probable
Match ’

Display EA’s in
categories along
with EA details,
Match Criteria,
Match Strength

Yes

Yes

Is the EA match
strength = W in any
3 matching rules

No
No

FR Number
FR-IB-ELA-17

Categorize
EA as
‘Possible
Match ’

FR Description
Step 1: Check if the EA is matched based on either Saved EA Relationship or Domain
Match or Normalized Name Match or Customer Masterand the strength of the match is
equal to„S‟ (strong). If a match is not made, skip to the next step

BR Number
5.01

If a match is made, then check if a „S‟ (strong) match is made based on any other rule
excluding the initial rule.

FR-IB-ELA-18
FR-IB-ELA-19
FR-IB-ELA-20

FR-IB-ELA-21

VMware

If a match is made, then set the category for the EA to „Strong Match‟, else skip to the next
step
Step 2: Check if the EA is matched in any 3 rules with a strength of „S‟ (strong). If a match
is made, set the category for the EA to „Strong Match‟. Else skip to the next step
Step 3: Check if the EA is matchedin any 2rules with a strength of „S‟ (strong). If a match is
made, set the category for the EA to „Probable Match‟. Else skip to the next step
Step 4: Check if the EA is matched in atleast 1non transaction based rules (transaction
based rule = cases, orders, or quotes) with a strength of „S‟ (strong) and is matching 3
additional rules with a strength of „W‟ (weak) . If a match is made, set the category for the
EA to „Probable Match‟. Else skip to the next step
If a category is not determined based on any of the steps, set the category for the EA to

CONFIDENTIAL

5.01
5.01
5.01

5.01

Page 20 of 69
„Possible Match‟.
FR-IB-ELA-22

Display results in the results section based on the categories determined along with the
count of records in each category

6.08a,
6.08b

5.3 Display and Manage Research Results

Wireframe-IB-ELA-08
FR Number
FR-IB-ELA-23

FR Description
Following column names will be shown to the user for each EA that is gathered and in
the order specified below
1)
2)
3)

EA Name
EA Number
Country(s) - Display the 2 digit ISO code of countries (separated by „,‟)

associated to the EBS party/party sites that make up the EA. The first 5
codes will be displayed after which an ellipsis (…) will be shown. User
can hover/click on the ellipsis to see the full list of country codes
4)

5)

EA Comments (Notes) – System generated comments based on additional
rules that provide additional information about the EA (ex : No Active IB,
Federal / Personal Account, ELA contract, etc). Check requirement FR-IB-ELA24.1 below for details
Sites - Show the number of unique sites (city + country combination)

associated to the EBS Parties which make up the EA. Ex : A „unique‟
VMware

CONFIDENTIAL

BR Number
6.09, 6.10,
6.11, 6.12,
6.13, 6.15,
6.16,
6.16.1,

Page 21 of 69

6)

FR-IB-ELA-23.1

7) SU Name – Super User Name
8) SU Email Address – Super User Email Address
9) PC Name – Procurement Contact Name
10) PC Email Address – Procurement Contacts Email Address
EA Comments (Notes) field is available for each EA and will be populated based on the
below logic. All the rules will be executed and if a condition in the rule is met then the
appropriate comment will be added to the existing comments by using „,‟ (coma) as a
separator. The first 3 comments will be displayed after which an ellipsis (…) will be
shown. User can hover / click on the ellipsis to see the full list of comments
1)
2)
3)
4)
5)
6)
7)
8)

FR-IB-ELA-23.2

site is a city + country combination within the EA. If party 1 has a site at
101 Main Street, City A, NZ; and party 2 has a site at 345 A Street, City
A, NZ; then only one site will be counted.
Customer Domain - For each party associated to the EA find all unique
domains that are associated to the contacts in EBS. The first 3domains
will be displayed separated by a „,‟ and a new line after which an ellipsis
(…) will be shown. User can hover/click on the ellipsis to see the full list
of country codes

Check if there is atleast 1 active IB associated to the EA. If not, add the note
„No Active IB‟ to the EA comments field
If the EA is of the Type = Person then add the note „Individual Account‟
If the EA is of the segment = Federal then add the note „Federal Account‟
If the EA has an ELA contract that is currently active then add the note „Active
ELA‟
If the EA has an active contract of the type MCS or BCS, then add the note
„Active MCS / BCS‟
If a different EA has been merged into this EA, then add the note „EA
<Victim_EA> Merged‟
If an LATF has been made into this EA, then add the note „LATF (IN) from
<Source_EA> „
If an LATF has been made from this EA, then add the note „LATF (OUT) from
<Target_EA> „

User can double click on any of values in „Country‟, „Sites‟, and „Customer Domains ‟to
display additional details. Derive all the parties that belong to an EA and their respective
site details. Domain column will have all the unique domains that belong to the sites
contacts. There will be 1 row for each Address Line 1, City, Postal Code and Country
combination of a party.
1)
2)
3)
4)
5)
6)
7)

Party Number : Each row will have the EBS party number that is part of this EA
Party Name : The party name associated to each party number
Domain(s) : All the unique domains that belong to the sites contacts
Address Line 1 : Address Line 1 that corresponds to the sites location
City : City that corresponds to the sites location
Postal Code : Postal Code that corresponds to the sites location
Country : Country that corresponds to the sites location

Check Wireframe below for reference

VMware

6.12

CONFIDENTIAL

6.11, 6.13,
6.15

Page 22 of 69

Wireframe-IB-ELA-09

FR Number
FR-IB-ELA-24

FR-IB-ELA-27

FR Description
All the primary matching rules that currently exist will be displayed as individual columns
along with the strength where a match is made
1) Company Master
2) Saved EA
3) DUNs
4) Orders / Bookings
5) Cases
6) Historical Quotes
7) Email Domain
8) Normalized Name
9) Contacts
10) Address
11) Manual Add
Each EA shown in results section will have a check box available at the end. User can
select 1 or more checkboxes.

BR Number
6.17

6.18

A select all box would be available at the top which enables the users to select all the EA‟s.
Users should still be able to uncheck or check individual EA‟s as needed. Unchecking the
select all box will unselect all current selections including any that were manually selected.

FR-IB-ELA27.1
FR-IB-ELA-25

VMware

This checkbox will determine which EA‟s will be deleted / saved / show quotable assets
„Add Accounts‟, „Delete Selected Accounts‟, „Save‟ buttons will be shown at the bottom.
These buttons are always anchored to the bottom of the window and the user does not
have to scroll down to view or act on these buttons.
User should be able to select 1 or more EA‟s from the results using the check boxes and
click on the „Delete Selected Accounts‟ button (only enabled when atleast 1 EA is
selected). Clicking on the button will show a confirmation box as a pop-up which has

CONFIDENTIAL

7.01, 7.02

7.01, 7.02

Page 23 of 69

FR-IB-ELA-26

„Confirm‟ and „Cancel‟. Clicking on „Confirm‟ will delete all the EA‟s selected from the
results section, whereas the cancel or close of the pop-up will not delete the EA‟s and they
will continue to be shown in the results
User should be able to click on the „Add Accounts‟ to add an EA to the list. User will be
prompted to enter an EA number value in a new overlay which will also have an OK and
Cancel buttons. Any number entered and submitted will be validated against the active list
of EA‟s available. If an active EA is not found then a message „Value entered does not
belong to a valid EA‟. The user should be able to provide a new value if they wish or cancel
the add operation.

7.01, 7.02

Once a valid EA is found, then the EA will be added to the list under the „Strong Match‟
category. Other composite values of the EA (countries, notes, sites, etc) should also be
derived and displayed. Following list of attributes should be available for this record.

FR-IB-ELA-28

1) EA Name
2) EA Number
3) Country(s)
4) EA Comments (Notes)
5) Sites
6) Customer Domain
7) SU Name
8) SU Email Address
9) PC Name
10) PC Email Address
11) Manually Added flag in the match criteria section will be set to „x‟
Once the EA selection/s have been made using the check boxes in the end, user can click
on the „Show Quotable Assets‟ button (only enabled if atleast 1 EA is selected). Whenever
the user clicks on the „Show Quotable Assets‟ button, before launching the Quotable
Assets window a confirmation screen will be shown which asks the users if they want to
save the current result set before continuing.

Wireframe-IB-ELA-10

VMware

CONFIDENTIAL

6.19

Page 24 of 69
FR Number
FR-IB-ELA-28.1

FR Description
User will be shown an overlay as displayed above with the following details

BR Number
7.01

A header that reads as follows will be shown : „You will now be directed to a new window
that shows the quotable assets. Would you like to save the EA‟s that are currently shown
before going to the quotable assets window ?‟
2 buttons „Save EA‟s and continue‟ and „Continue without saving‟ will be shown
A note will be shown at the bottom of the window that reads as follows „Note : The
research window will still be available in the background and you can continue your
research in that window‟
If the user clicks on „Continue without saving‟ then the overlay will be closed and a new
window will be opened for the BI Dashboard.

FR-IB-ELA-28.2

If the user clicks on the „Save EA‟s and continue‟, the save operation is initiated based
on the next few requirements.
The Account ID or the EA number that is marked as primary in the input parameters will
be used as the key for saving the relationship. This primary Key along with the users
profile (Sales, Others, etc) will become the unique identifier for the relationship.

7.01, 7.04

If a saved relationship exists for the account ID or EA number and profile combination,
then user should be provided a choice of either replacing the full list or add any new
EA‟s to the existing list. If a saved relationship doesn‟t exist, then all the EA‟s that are
currently shown to the user will be saved for the unique key combination

Wireframe-IB-ELA-11

FR Number

FR Description

FR-IB-ELA-28.3

The overlay (that displayed the user the choice to save) will be refreshed and the above
screen will be shown to the user.

VMware

CONFIDENTIAL

BR Number
7.01, 7.05

Page 25 of 69
A header will be displayed as follows „A saved EA list already exists for the <<key type>
: <key value>> and <profile value>profile combination. Would you like to add your EA‟s
to this existing list or replace the existing list with your EA‟s.‟
The following 3 buttons would be displayed. „Add to existing List‟, „Replace existing list‟,
„Continue without saving‟.
A footer will be displayed as follows „Note: If you plan to replace the existing list with your
list, be mindful of the fact that other users that saved / using the existing list will lose their
data.‟
If user clicks on „Add to existing list‟, then all EA‟s from the result set that are currently
not available in the existing list will be added to the list.
If user clicks on „Replace existing list‟, then all EA‟s from the existing list will be deleted
and all EA‟s from the new result set will be added to the list.
In both the cases the status of the existing relationship will be flipped to „Interim‟
status.The date and time stamp of the save will be marked along with a comment of
„System save based on quotable assets view‟. The user that clicked on the show
quotable assets view will be marked as the user that performed the last save.

FR-IB-ELA-29

FR-IB-ELA-30

If the user clicks on the „Continue without saving‟, the save operation is aborted and user
will be taken to BI Dashboard.
The following list of attributes will be saved for each EA
1) EA Name
2) EA Number
3) Manual Add
4)
If the user chooses to continue without saving, the BI dashboard will be launched in a
separate window.

7.01, 7.02

6.19, 7.01

If the user choose to save the EA‟s (Add / Replace), then the BI Dashboard is launched
in a separate window only after the save operation is successfully completed.
The EA‟s that have been selected in the EA research tool will be passed as parameters
to the BI Dashboard. The BI dashboard should not ask the user for a sign-on.

FR-IB-ELA-31

FR-IB-ELA-32

BI Dashboard should take the EA‟s passed as input parameters and show the quotable
assets related to these EA‟s by default (without the user clicking on search or other
buttons)and in the format that is appropriate for the user‟s profile.
User should still be able to perform additional research or filter EA results in the EA
research tool and select a different set of EA‟s and click on the show quotable assets
view to launch the BI dashboard for the new set of EA‟s in a new window
Users should be able to filter the results by using either of the criteria

1) Filter by country : Show all EA‟s where the Country column has atleast

2)

3)

4)

VMware

1 of the country codes provided as filter. Multiple values can be entered
by using a Comma as separator. If multiple values are entered, an „OR
condition should be applied between the values entered
Filter by domain : Show all EA‟s where the domain columns has atleast
1 of the domain‟s provided as filter. Multiple values can be entered by
using a Comma as separator. If multiple values are entered, an „OR
condition should be applied between the values entered
Filter by name including a contains filter : Show all EA‟s where the EA
name column matches the name provided including a capability for
wildcard search. Multiple values can be entered by using a Comma as
separator. If multiple values are entered, an „OR condition should be
applied between the values entered
Filter for any rule matches (i.e.DUNS, Company Master matches) :
Show all EA‟s where the match rule/s selected have an S or W

CONFIDENTIAL

6.19

6.08c

Page 26 of 69
If multiple filters (country, domain, etc) are set, then an „AND‟ condition will be applied
between the different filters.

FR-IB-ELA-33

A clear all filters button should be available which will clear all the filters and refresh the
results and show all the data. (any EA‟s that are specifically removed using the
remove/delete capability will not be part of the results even after filters are removed, but
at the same time, any EA‟s that were manually added should be shown as part of the
filtered result set)
User should have the capability to export to CSV by clicking on the „Export Results‟ link
(enabled only if atleast 1 record is available in results) the CSV will only have the results
that are currently shown to them on the portal. If any filters have been applied, EA‟s
belonging to the filters should not be shown in export.

6.08d

An „Export All‟ link will also be available that exports all results by ignoring the filters that
have been set.
The list of EA‟s retrieved and all related details fields should be exported.

FR-IB-ELA-33.1

The prioritization levels (strong, probable, and possible) should be moved to Excel
columns and the results sorted based on these columns. The order would be Strong,
Probable, possible.
User can select 1 or more EA‟s and click on the „Save EA results‟ button (only enabled if
atleast 1 EA is selected)

7.01

Upon clicking the „Save EA Results‟ button, user will be provided a choice of saving the
result against an opportunity or quote

Wireframe-IB-ELA-12
FR Number
FR-IB-ELA-33.2

FR Description
User will be shown an overlay as displayed above with the following details
A header that reads as follows will be shown : „Would you like to save the results for a
specific transaction ?. If yes, enter the related opportunity ID or the quote ID‟
2 fields with a radio button capability will be available. „No‟ and „Yes‟. Default selection is
„No‟. If „Yes‟ is selected, the user will then be able to select the label „Opportunity ID‟ or
„Quote ID‟ or „Case Number‟ from an LOV and then enter its respective value. The value

VMware

CONFIDENTIAL

BR Number
7.01

Page 27 of 69
that can be entered can be an alpha-numeric value with special characters.
The default selection is „Opportunity ID‟. When „Opportunity ID‟ is selected, the value
column will become a LOV that also allows new values to be entered. The list of values
shown in the LOV will be all the open opportunity ID‟s in SFDC that are associated to
accounts that are inturn associated to the user. If the user landed here after initiating the
research from the VMStar Opportunity page, then the related opportunity should be
defaulted.
A comments field will be provided that can accommodate upto 300 characters including
special characters

FR-IB-ELA-33.3

User will be provided a „Submit‟ button (enabled only when a min of 10 characters are
entered in comments field) that they can click once the desired values are entered.
The Account ID or the EA number that is marked as primary in the input parameters will
be used as the key for saving the relationship. This primary Key along with the users
profile (Sales or Others) will become the unique identifier for the relationship.

7.01

If a transaction specific ID (Optty ID / Quote ID/Case number) is entered, then it will be
used as an additional attribute in creating the unique key
If a saved relationship exists for the unique key combination, then user will be provided a
choice of either replacing the full list or add any new EA‟s to the existing list, else the full
list of EA‟s selected would be saved for the unique key combination

Wireframe-IB-ELA-13

FR Number

FR Description

FR-IB-ELA-33.4

The overlay (that displayed the user the choice to save) will be refreshed and the above
screen will be shown to the user.
A header will be displayed as follows „A saved EA list already exists for the <<primary
key type> : <key value>>, <<secondary key type> : <key value>> and <profile value>
profile combination. Would you like to add your EA‟s to this existing list or replace the
existing list with your EA‟s.‟
The following 3 buttons would be displayed. „Add to existing List‟, „Replace existing list‟,
„Cancel Save‟.

VMware

CONFIDENTIAL

BR Number
7.01

Page 28 of 69
A footer will be displayed as follows „Note: If you plan to replace the existing list with your
list, be mindful of the fact that other users that saved / using the existing list will lose their
data.‟
If user clicks on „Add to existing list‟, then all EA‟s from the result set that are currently
not available in the existing list will be added to the list and the users lands back on the
EA results page.
If user clicks on „Replace existing list‟, then all EA‟s from the existing list will be deleted
and all EA‟s from the new result set will be added to the list and the users lands back on
the EA results page.
In both the cases the status of the existing relationship will be flipped to „Interim‟ status.
The date and time stamp of the save will be marked along with the commentsentered by
the user. The user that is performing this operation will be marked as the user that
performed the last save.

FR-IB-ELA-33.5

If the user clicks on the „Cancel Save‟, the save operation is aborted and user will be
taken to EA results page.
The following list of attributes will be saved for each EA
1) EA Name
2) EA Number
3) Manual Add

7.01

5.4 Rules

5.4.1 Eligibility
5.4.1.1

To-Be Flow
Eligibility

Is rule enabled
for users profile

Yes

Rule eligible for
type (standard /
deep) selected

No

Do not execute rule

No

Yes
Continue Rule
execution

5.4.1.2

Steps
FR Number

FR Description

FR-IB-ELA-33.6

For each Match rule or sub-match rule, check if the rule is eligible for the user profile and
user selected option (standard / deep)
Check if the rule is enable for the users profile, if not, do not execute the match rule or

FR-IB-ELA-33.7

VMware

CONFIDENTIAL

BR Number
6.01
6.01

Page 29 of 69
sub-match rule and skip to the next rule
If the above validation is a pass, then check if the type selected by the user (deep or
standard) matches the type defined for rule or sub-match rule , if matching execute rule,
else skip to the next rule

FR-IB-ELA-33.8

If user selected „Standard‟ : Execute all rules that are defined as Standard
If user selected „Deep‟ : Execute all rules that are defined as Standard and Deep

5.4.2 Saved EA
5.4.2.1

To-Be Flow

Start

For each Account ID
entered

For each EA Number
entered

Eligibility

Eligibility

Search in saved EA
relationships table
where the account
ID is the primary key

Search in saved EA
relationships table where the
EA Number is the primary key
or just part of the relationship

If a match is found, find
other relationships where
the EA’s in this relationship
are marked as primary

Gather all EA’s in
each of the
relationships found
For each of the EA’s found (There
will be duplicates from different
profiles), follow the below steps

Profile (Sales,
Renewals, etc) of
relationship ?

Different from users
profile

Same as the users
profile

Relationship
status ?

Interim

Set Saved EA flag as
‘W’ (Weak)

Certified

VMware

Set Saved EA
CONFIDENTIAL flag as
‘S’ (Strong)

Return all unique
EA’s with the
strength set to the
highest found.

6.01

Page 30 of 69

5.4.2.2

Steps
FR Number

FR-IB-ELA-34
FR-IB-ELA-35

FR Description
For each Account id or EA number entered perform the following steps
Account ID Rule (Standard): If an Account ID is entered and eligible to be executed, then
search in the saved relationships table for all saved searches where the Account ID is
marked as a primary. For each saved relationship found, create a list of the EA‟s and
their profile as output and for each unique EA‟sfind other relationships where this EA is
the primary key.For each saved relationship found, add the EA‟s and their profile to the
list

BR Number
4.03, 4.04
4.03

FR-IB-ELA-35.1

Note: Only those relationships that do not have a secondary key will be taken into
consideration.
EA Number Rule (Standard): If an EA number is entered and eligible to be executed,
search for all saved relationships where this EA is either the primary key or part of the
saved EA‟s list. Add all EA‟s and their respective profiles to the EA list

4.04

FR-IB-ELA-36

Note: Only those relationships that do not have a secondary key will be taken into
consideration.
For each EA found (including duplicates), perform the next set of steps. If no EA‟s are
found then end of this rule Check if the users profile matches the profile of the saved EA
relationship.

4.03, 4.04

If it matches, perform next step, else set the „Saved EA Flag‟ strength for the EA to „W‟
(weak)
If the status of the saved EA relationship is „Certified‟, set the „Saved EA Flag‟ strength
for the EA to „S‟ (strong). Else, If the status of the saved EA relationship is „Interim‟, set
the „Saved EA Flag‟ strength to „W‟ (weak)
Return all unique EA‟s collected with Saved EA rule and set the „Saved EA Flag‟
strength set to the highest gathered for an EA

VMware

CONFIDENTIAL

Page 31 of 69

5.4.3 Orders
5.4.3.1

To-Be Flow

Start

Account ID /
EA Number
provided ?

EA #

Eligibility

For each order, get
the Sold-to /
Licensed-to contact

Find all orders
associated to the EA

Find orders where the
contact is marked as a
Sold-to / Licensed-to
contact

For each contact

For each order, Find
associated EA
number

Account ID
Find other accounts
that match
normalized account
name + Country

Eligibility

For each Account
found

For each Account
found, get all
associated contacts
in SFDC

Find associated
UUID and then fetch
the related party (
account)

Eligibility

Find all associated
orders in SFDC

Eligibility

Remove contacts
with domains like
‘Gmail’ (Eloqua
rules).

For each remaining
contact

Find orders where the
contact is marked as a
Sold-to / Licensed-to
contact

Find all orders
where the account
has played any part
(Bill-To, Ship-To,
Deliver-To, etc)

associated EA
number

More than 1
VMStar contact has the
same email domain as
the primary domain
associated to EA

Yes

No
Is either
of the order
contacts marked as
a contact in SFDC
Account

For each order
found, get the
associated Sold-to /
Licensed-to contact

End of this search

Eligibility

associated EA
Number for EMS

Check if
EA's UCM account
normalized names =
Normalized SFDC
Account name

Match

No
Match
Domain of order
sold to/licensed to
contact = domain of
any EA user

Return all unique
EA’s with the
highest strength
found.

No

5.4.3.2

Set Order flag as ‘S’
(Strong)

Set Order flag as ‘W’
(Weak)

No

Steps
FR Number

FR Description

FR-IB-ELA-37


FR-IB-ELA-38

VMStar Contacts to Orders Rule (Standard): If an Account IDis entered and rule is
eligible to be executed, Find other accounts that match normalized account name +
Country.
For each account found, get all the associated contacts from VMStar. Remove all
contacts with domains like „Gmail‟

VMware

Yes
Check if
EA's UCM account
normalized names =
Input EA’s UCM
account normalized
name

CONFIDENTIAL

BR Number
4.3.1,
4.3.2,
4.3.3,
4.3.4
4.3.2

No

Page 32 of 69
List of Email domains to be excluded:

Email domains to be
excluded from contacts.xlsx

For each remaining contact, find orders in EBS where the contact is marked as the SoldTo or the License-To (stored in DFF) contact
For each order found, get the associated EA number from EMS. If found, check if the EA
primary users email domain is the also available as an email domain on the more than 1
VMStar contact

FR-IB-ELA-39

If found set the strength of the „Order Flag‟ to „S‟ (strong) , else set it as „W‟ (weak)
VMStar Orders to Contacts Rule (Deep): If an Account ID is entered and rule is eligible
A.1.1.7
to be executed, Find other accounts that match normalized account name + Country.

4.3.4

For each account found, get all the orders associated to the account in VMStar(SFDC).
For each order found, get the Sold-To or the License-To contact and check if the contact
is marked as one of the SFDC accounts contacts. If not found, find orders in EBS where
the contact is marked as the Sold-To or the License-To (stored in DFF) contact, else end
of this sub-rule
VMStar contact
FR-IB-ELA-39.1

VMStar UUID to Orders Rule (Standard): If an Account ID is entered and rule is eligible

4.3.1

For each account found, Find associated UUID and then fetch the related party (
account)
.
For each party / account found, Find all orders where the account has played any part
(Bill-To, Ship-To, Deliver-To, etc).

VMStar contact

A.1.1.8

A.1.1.9
FR-IB-ELA-40
A.1.1.10

VMStar Orders to EA Rule(Standard): If an Account ID is entered and rule is eligible to
be executed, Find other accounts that match normalized account name + Country.

4.3.1

For each account found, get all the orders associated to the account in VMStar(SFDC).
For each order found, get the associated EA number from EMS. If found, check if the
EA‟s UCM account normalized name is the same as the normalized name of the SFDC
account.
If matching set the strength of the „Order Flag‟ to „S‟ (strong) , else check if the Domain
of order sold to/licensed to contact matches the domain of any user in the EA.

FR-IB-ELA-41

VMware

If matching set the strength of the „Order Flag‟ to „S‟ (strong) , else set it as „W‟ (weak)
EA Number Order to Contacts Rule (Standard): If an EA Number is entered and rule is
eligible to be executed, Find all orders that are associated to the EA in EMS. For each
order found, get the Sold-To and License-To contacts from EBS and for each of the

CONFIDENTIAL

4.3.3

Page 33 of 69
distinct contacts find other orders in EBS which has these contacts marked as Sold-To
or License-To.

FR-IB-ELA-41.1

VMware

For each order found, get the associated EA number from EMS. If found, check if the
EA‟s UCM account normalized name is the same as the input EA‟s UCM account
normalized name. If same, set the strength of the „Order Flag‟ to „S‟ (strong), else set to
„W(eak)‟ and move onto the next record.
From all the EA‟s collected for Order rules, Return unique EA‟s with the „Order Flag‟
strength set to the highest gathered for the EA

CONFIDENTIAL

4.3.1,
4.3.2,
4.3.3,
4.3.4

Page 34 of 69

5.4.4 DUNs
5.4.4.1

To-Be Flow

Start

Eligibility

For each Account ID
entered

Fetch the DUNS
number on the
VMStar account

Is a DUNS value
available

No

Yes
Search EDW (not EBS) party data to see
which parties have the same DUNS
value and a EA number is available.
Where available fetch the EA #, Party
DUNS, Domestic Ultimate DUNS and
Global Ultimate DUNS

Is there match
based on Party DUNS or
Domestic Ultimate
DUNS

Yes

No

Match based on
Global ultimate

Set DUNS flag as ‘S’
(Strong) for the EA

Set DUNS flag as ‘W’
(Weak) for the EA

Return all unique EA’s
with the strength set to
the highest found.

VMware

CONFIDENTIAL

Page 35 of 69

5.4.4.2

Steps

FR Number

FR Description

FR-IB-ELA-41.2

DUNs Rule (Standard): If an Account ID is entered and rule is eligible to be executed,
fetch the DUNs number associated to the VMStar account
If a DUNS number is available, Search EDW (not EBS) party data to see which parties
have the same DUNS value and the parties have a related EA number available. Where
an EA is available fetch the EA #, Party DUNS, Domestic Ultimate DUNS and Global
Ultimate DUNS

BR Number
4.1.1

If the SFDC DUNs to the party match is based on Party DUNS or Domestic Ultimate
DUNS, then set the „DUNs Flag‟ strength to „S‟, else is the match is based on global
ultimate set the strength flag „W‟ for the EA.
From all the EA‟s collected for Duns rule, Return unique EA‟s with the „DUNs Flag‟

FR-IB-ELA-41.3

4.1.1

5.4.5 Cases
5.4.5.1

To-Be Flow

Start

Account ID /
EA Number
provided ?

EA #

Eligibility

For each user, Find cases that were
submitted by the user and have an
EA # associated. Do not consider
any cases that are related to the
‘Default Consumer Account’

Find all users

For each unique EA
found

Account ID
Find other accounts
that match
normalized account
name + Country

Eligibility

Remove contacts
with domains like
‘Gmail’ (Eloqua
rules).

For each Account
found, get all
associated contacts
in SFDC

For each
remaining
contact

Use the contacts email to
find other cases that were
logged with that email. Do
not consider any cases that
are related to the ‘Default
Consumer Account’

For each case that is
found and has an EA
that is associated

Eligibility

For each Account found, find all
associated cases in SFDC where
an EA is available. Do not
consider any cases that are
related to the ‘Default
Consumer Account’

Check if
Normalized EA
Name = Normalized
Account name

Set Case flag as ‘S’
(Strong)

Yes

Check if
Normalized EA
Name = Input EA’s
Normalized name

Yes

No

Domain of the
primary case contact
occurs more than once
on the VMStar account
contact list

No

VMware

CONFIDENTIAL

No

Yes

Return unique EA’s
with the highest
strength found.

Set Case flag as ‘W’
(Weak)

Yes

Domain of the
primary case contact
occurs more than
once on the input EA
user list

No

Page 36 of 69

5.4.5.2

Steps

FR Number

FR Description

FR-IB-ELA-41.4

EA Users to Cases Rule (Standard): If an EA Number is entered and rule is eligible to be
executed, fetch all users associated to the EA and for each user, Find cases that were
submitted by the user and have an EA # associated. Do not consider any cases that are
related to the „Default Consumer Account‟ (There are about 11 such default accounts,
exclude all)

FR-IB-ELA-41.5

If an EA number is available, check if the EA‟s UCM party normalized name is the same
as the input EA‟s UCM party normalized name. If yes, set the „Case Flag‟ strength to „S‟,
else, check if the domain of the cases primary contact occurs more than once on the
EA‟s user list. If yes, set the „Case Flag‟ strength to „S‟, else, set the flag to „W‟
VMStar account Contacts to Cases Rule (Deep): If an Account ID is entered and rule is
eligible to be executed, fetch all the SFDC accounts based that have the same
normalized name + country as the input account.

BR Number
4.4.3

4.4.2

For each account, find all the contacts and remove all contacts with domains like „Gmail‟.
For each remaining contact, Find other cases that were submitted by the contact email
and have an EA # associated. Do not consider any cases that are related to the „Default
Consumer Account‟ (There are about 11 such default accounts, exclude all)

FR-IB-ELA-41.6

as the input account normalized name. If yes, set the „Case Flag‟ strength to „S‟, else,
check if the domain of the cases primary contact occurs more than once on the
accountscontacts list. If yes, set the „Case Flag‟ strength to „S‟, else, set the flag to „W‟
VMStar account to Cases Rule (Standard): If an Account ID is entered and rule is eligible
to be executed, fetch all the SFDC accounts based that have the same normalized name
+ country as the input account.

4.4.1

For each account, find all the cases submitted for the account and an EA is available. Do
not consider any cases that are related to the „Default Consumer Account‟ (There are
about 11 such default accounts, exclude all)

FR-IB-ELA-41.7

VMware

as the input account normalized name. If yes, set the „Case Flag‟ strength to „S‟, else,
check if the domain of the cases primary contact occurs more than once on the accounts
contacts list. If yes, set the „Case Flag‟ strength to „S‟, else, set the flag to „W‟
From all the EA‟s collected thru allCase rules, Return unique EA‟s with the „Case Flag‟

CONFIDENTIAL

4.4.1, 4.4.2,
4.4.3

Page 37 of 69

5.4.6 Quotes
5.4.6.1

To-Be Flow

Start

For each EA #
entered

For each Account ID entered

Eligibility

Eligibility

Find other accounts that match
normalized account name + Country
Fetch all ELA header quotes
that have the account ID

Fetch all ELA header
quotes where the EA
# is available in the
‘Purchaser’s EA #’
column

Find
header
EA

Find all IB quotes
where the EA is
available in ‘EA #’
field in the quote
detail

For each header
quote found
Find the IB quote
related to header
ELA quote by using
the quote number in
‘IB Quote #’ field

Find IB
Quote

Retrieve all the EA
numbers from the
‘EA #’ field in the
quote detail

Find
Detail
EA

Gather any EA #
marked in the
‘Purchaser’s EA #’
column

For each
value found

For each
Header ELA
Quote found

Find IB
Quote
Find the related
header ELA quote by
using the quote
number in ‘IB Quote
#’ field

Check if it is
a valid EA
number

Yes

For each IB quote
found

Find
Detail
EA

Find
header
EA
Check if
Quote reached
the validation
stages

Set Quote flag as ‘S’
(Strong)

No

Set Quote flag as ‘W’
(Weak)

the highest found.

5.4.6.2

Steps

FR Number
FR-IB-ELA-41.8

VMware

FR Description
VMStar Account to Quotes Rule (Standard): If an Account ID is entered and rule is
eligible to be executed, fetch all the SFDC accounts based that have the same
normalized name + country as the input account.

CONFIDENTIAL

BR Number
4.5.1

Page 38 of 69

For each account, fetch all ELA header quotes that have the same account ID as the
input account ID. For each header quote found perform both the steps
Find any EA marked in the „Purchasers EA#‟ field and check if it is a valid EA
#. If it is a valid EA, check if the header quote has reached validation stages
and if yes set the „Quote Flag‟ to „S‟, else set the flag as „W”
2) Find the IB quote related to header ELA quote by using the quote number in
„IB Quote #‟ field. If found, retrieve all the EA numbers from „EA #‟ field in the
quote detail. For each value found, check if it is a valid EA #. If it is a valid EA,
check if the IB quote has reached validation stages and if yes set the „Quote
Flag‟ to „S‟, else set the flag as „W”
EA Number to Quotes Rule (Standard): If an EA Number is entered and rule is eligible
to be executed, perform all the steps for each EA entered as input.
1)

FR-IB-ELA-41.9

1)

FR-IB-ELA-41.10

VMware

For theEA, fetch all ELA header quotes where the EA is available in the
„Purchaser EA #‟ field. For each header quote found, perform both the steps
below
a. Check if the header quote has reached validation stages and if yes
set the „Quote Flag‟ to „S‟, else set the flag as „W”
b. Find the IB quote related to header ELA quote by using the quote
number in „IB Quote #‟ field. If found, retrieve all the EA numbers
from „EA #‟ field in the quote detail. For each value found, check if it
is a valid EA #. If it is a valid EA, check if the IB quote has reached
validation stages and if yes set the „Quote Flag‟ to „S‟, else set the
flag as „W”
2) Find all IB quotes where the input EA is available in the „EA#‟ field of the quote
detail.For each IB quote found perform both the steps
a. Retrieve all other EA numbers from „EA #‟ field in the quote detail.
For each value found, check if it is a valid EA #. If it is a valid EA,
check if the IB quote has reached validation stages and if yes set the
„Quote Flag‟ to „S‟, else set the flag as „W”
b. Find the related header ELA quote where the header quotes „IB
Quote #‟ field is the same IB quote found. If found, find any EA‟s
marked in the „Purchasers EA#‟ field and check if it is a valid EA #. If
it is a valid EA, check if the header quote has reached validation
stages and if yes set the „Quote Flag‟ to „S‟, else set the flag as „W”
From all the EA‟s collected thru all Quote rules, Return unique EA‟s with the „Quote
Flag‟ strength set to the highest gathered for the EA

4.5.1

CONFIDENTIAL

4.5.1

Page 39 of 69

5.4.7 Contacts
5.4.7.1

To-Be Flow

Start

Account ID /
EA Number
provided ?

EA #

Account ID

Eligibility

Find all users

For each user on the
EA provided as input

Find other EA’s which
this user has access to

For each EA
found

Is the
user SU / PC on
both the
EA’s

No

For each Account
found, get all
associated contacts
in SFDC

No

Yes

Yes

Find other accounts
that match
normalized account
name + Country

Are the first
8 characters
same on both
the EA’s

Return all unique
EA’s with the
highest strength
found.

Set Contacts flag as
‘S’ (Strong)

Is the email
domain
occurring more
than once on
both EA’s
Yes

No

‘W’ (Weak)

SU/PC
Remove contacts
with domains like
‘Gmail’ (Eloqua
rules).

For each remaining
contact

SU/PC or
Folder Admin

User role
on EA

Eligibility

SU/PC or
Folder Admin

Folder Admin

Yes

Check if
Normalized Account
Name = Normalized EA
name

No

Regular User

Find EA’s where the
contact is an user on the
account

Eligibility

Check if
Normalized Account
Name = Normalized EA
name

Yes

Yes

No

No

5.4.7.2

Any other
VMStar contact has
the same email
domain as this
contact

‘S’ (Strong)

‘W’ (Weak)

Steps

FR Number

FR Description

FR-IB-ELA-42


FR-IB-ELA-43

VMStar Contact to EA SU Rule (Standard): If an Account ID is entered and rule is
eligible to be executed, Find other accounts that match normalized account name +
Country.
For each remaining contact, find EA‟s in EMS where the contact is marked as a SU/PC
or Folder Administrator on the EA.
If the user is a SU / PC, set the „Contacts Flag‟ to „S‟ (strong), else if the user is a folder
administrator, check if the normalized name of the EA is the same as the normalized

VMware

Return all unique
EA’s with the
highest strength
found.

CONFIDENTIAL

BR Number
4.6.1, 4.6.2,
4.6.3
4.6.1

Page 40 of 69
name of the account. If matching then set the „Contacts Flag‟ to „S‟ (strong) else set the
„Contacts Flag‟ to „W‟ (weak).
FR-IB-ELA-43.1

VMStar Contact to EA User Rule (Deep): If an Account ID is entered and rule is eligible

4.6.2

For each remaining contact, find EA‟s in EMS where the contact is marked as a user on
the EA.
If the user is a regular user, check if the normalized name of the EA is the same as the
normalized name of the account. If matching, check if the any other VMStar contact has
the same email domain as this contact (repeated more than once). Else set the

FR-IB-ELA-44

If more than 1 vmstar contacts has the same email domain, then set the „Contacts Flag‟
to „S‟ (strong) else set the „Contacts Flag‟ to „W‟ (weak).
EA User to other EA Rule (Standard): If an EA Number is entered and rule is eligible to
be executed, Find all users that are associated to the EA in EMS.

4.6.3

For each of the users, find others EA‟s that this user is associated to and for each EA
found, check if the user is SU/PC on both the accounts. If yes, set the strength of the
„Contacts Flag‟ to „S‟ (strong).
Else, check if the first 8 characters are matching on both the EA‟s. If yes, set the strength
of the „Contacts Flag‟ to „S‟ (strong)

FR-IB-ELA-44.1

VMware

Else, check if an email domain is occurring more than onceon both the EA‟s. If yes, set
the strength of the „Contacts Flag‟ to „S‟ (strong). Else set the „Contacts Flag‟ to „W‟
(weak).
From all the EA‟s collected for Contact rules, Return unique EA‟s with the „Contacts Flag‟

CONFIDENTIAL

4.6.1, 4.6.2,
4.6.3

Page 41 of 69

5.4.8 Addresses
5.4.8.1

To-Be Flow
Start

For each EA
Provided as input

For each SFDC
Account ID Provided
as input

Eligibility
Eligibility

Find the parties and
their related sites in
EBS
Find the address line 1
+ city + country

Search in EBS for other
sites that have exactly
same address line 1 + city
+ country

For every match found,
find the related parties
and their related EA’s

For each EA found

For each site found,
Find other sites that
have the same
address line 1 + city
+ country

For every match found,
find the related parties
and their related EA’s

5.4.8.2

Set Address flag as
‘W’ (Weak)

with the highest
strength found.

Set Address flag as
‘S’ (Strong)

Steps

FR Number
FR-IB-ELA-44.2

FR-IB-ELA-44.3

FR-IB-ELA-44.4

VMware

For each EA found

FR Description
VMStarAccount to Address Rule (Deep): If an Account ID is entered and rule is eligible
to be executed, find its Address Line1, City & Country.
Search EBS for other sites that have the same address line 1, City & Country. If found,
find the related parties and their related EA‟s. For each EA found, set the „Address Flag‟
to „S‟ (strong).
EA Number to Address Rule (Deep): If an EA Number is entered and rule is eligible to be
executed, find its related parties and their related sites in EBS. For each site found, find
the related Address Line1, City & Country.
Search EBS for other sites that have the same address line 1, City & Country. If found,
find the related parties and their related EA‟s. For each EA found, set the „Address Flag‟
to „W‟ (weak).
From all the EA‟s collected for Address rules, Return unique EA‟s with the „Address Flag‟

CONFIDENTIAL

BR Number
4.9.1

4.9.2

4.9.1, 4.9.2

Page 42 of 69

5.4.9 Email Domain
5.4.9.1

To-Be Flow

Start

Account ID
entered

Yes

Eligibility

For each
Account ID
entered

Get all
associated
contacts in
SFDC

No

Remove contacts with
domains like ‘Gmail’
(Eloqua rules) and
contacts that do not share
their email domain with
atleast 1 other contact in
the list

For each
remaining
contact

Find EA’s whose
primary email
domain is the same
as this contacts
email domain

For each EA
gathered thru this
rule, check against
EA’s gathered thru
other rules

Set Email Domain
flag as ‘S’ (Strong)
For each EA found
based on all other
rules executed till
now and the input
parameters
provided

Yes

First
8 characters of this
EA’s normalized name =
First 8 characters of any
other EA’s normalized
name

Gather all EA’s with
appropriate flag.
No

Eligibility

Find other EA’s whose
primary email domain
is the same as this EA’s
primary email domain

For each
EA found

First
EA’s normalized name = First 8
characters of any other
EA’s(gathered so far)
normalized name

Set Email Domain
flag as ‘W’ (Weak)
Yes

No
Set Email Domain
flag as ‘W’ (Weak)

with the highest
strength found.

Set Email Domain

No

Eligibility

5.4.9.2

Find EBS parties where
the email domain of
any contact (party/
account/ site/ site use
level) is the same as
this EA’s primary email
domain

For each
party find
the related
EA

First
8 characters of EBS parties
normalized name = First 8
characters of any other
EA’s(gathered so far)
normalized name

Yes

Steps
FR Number

FR-IB-ELA-45

FR Description
VMstar Contact Email Domain to EA Rule (Standard): For each Account ID entered and
if the rule is eligible to be executed, get all the associated contacts from VMStar.
Remove all contacts with domains like „Gmail‟. Also remove any contacts where the
email domain is not occurring more than once.
For each remaining contact, find EA‟s in EMS where the contacts email domain is
matching the EA‟s primary user email domain. Once an EA is found match the first 8
characters of that EA‟sUCM party normalized name to first 8 characters of any EA‟sUCM
party normalized name found so far based on all the rules that have been executed so
far.
If a match is found, then set the „Contacts Flag‟ to „S‟ (strong) else set the „Contacts
Flag‟ to „W‟ (weak).

VMware

CONFIDENTIAL

BR Number
4.7.1

Page 43 of 69
FR-IB-ELA-45.1

The following Email Domain matching Rules will be applied wherever we need to find
target domains for a source domain
Strip out everything before the @ sign from the source and target list.
If the source domain does not has a „org‟, „edu‟, „net‟, ‟int‟, ‟gov‟ after the last „.‟ (dot) strip
out the last dot and any characters after that from the source
After all the required characters have been stripped from the source email, use that as
the input string.

FR-IB-ELA-46
FR-IB-ELA-47

Perform an exact match on the target domain/s after stripping out the last dot and any
characters after that as long as the characters after the last dot are not equal to „org‟,
„edu‟, „net‟, ‟int‟, ‟gov‟
Next set of rules should be performed for all the EA‟s that have been gathered so far
based on all the rules executed and any input EA‟s provided
EA Primary Email Domain Rule to other EA (Standard): For each EA found so far and if
the rule is eligible to be executed, find other EA‟s whose primary contacts email domain
is the same as this EA‟s primary contacts email domain but exclude EA‟s that have an

4.7.2, 4.7.3
4.7.2

EA_TYPE of „PERSON‟ from the target EA list
For each EA found, check if the first 8 characters of the EA‟s UCM party normalized
name matches with the first 8 characters of the EA‟s UCM party normalized name of any
of the EA‟s found so far (based on all rules)

FR-IB-ELA-48

If it matches, set the strength of the „Email Domain Flag‟ to „S‟ (strong). Else set the
EA Primary Email Domain Rule to EBS parties (Deep): For each EA found so far and if
the rule is eligible to be executed, find contacts (Party / Site / Site Uses Level) in EBS
that have the same email domain as this EA‟s primary contacts email domain. Based on
the contacts find the related EBS parties and their related EA‟s

4.7.3

For each EA found, check if the first 8 characters of the EA‟s UCM party normalized
name matches with the first 8 characters of the EA‟s UCM party normalized name of any
of the EA‟s found so far (based on all rules)

FR-IB-ELA-48.1

VMware

If it matches, set the strength of the „Email Domain Flag‟ to „S‟ (strong). Else set the
From all the EA‟s collected for Email Domain rules, Return unique EA‟s with the „Email
Domain Flag‟ strength set to the highest gathered for the EA

CONFIDENTIAL

4.7.1, 4.7.2,
4.7.3

Page 44 of 69

5.4.10

Company Master

5.4.10.1 To-Be Flow

Start

Account ID
/ EA #

Account ID

EA #

Eligibility

Eligibility

Provide the UUID
related to the
Account ID as input
to company master

Derive the UUID related
to the EA # and provide
the UUID’s as input to
company master

Yes

Is the company
master match found
based on business
approved hierarchy

No

Is the company
master match found
based on default
VMware hierarchy

Retrieve unique EA’s
for all the records in
the hierarchy
including the input
EA

No

End for this record/
begin search for
next record

Yes
Retrieve unique EA’s
for all the records in
the hierarchy including
the input EA

Set Company master

Set Saved EA flag as
‘W’ (Weak)

the highest found.

5.4.10.2 Steps
FR Number

FR Description

FR-IB-ELA-48.2

VMstar Account to Company Master Rule (Standard): For each Account ID entered and
if the rule is eligible to be executed, provide the related UUID of the account as the input
and check if a match is found based on the business approved VMware hierarchy.
If a match is found, retrieve EA‟s for all the records in the hierarchy including the input

VMware

CONFIDENTIAL

BR Number
4.01

Page 45 of 69
record. Set the „Company Master‟ flag to „S‟ for all of the EA‟s retrieved.
If a match is not found, check if a match is found based on the default VMware
hierarchy. If found, retrieve EA‟s for all the records in the hierarchy including the input
record. Set the „Company Master‟ flag to „W‟ for all of the EA‟s retrieved.

FR-IB-ELA-48.3
FR-IB-ELA-48.4

If no match is found, process the next record.
based on all the rules executed
EA Number to Company Master Rule (Standard): For each EA Number entered or
gathered based on standard rules and if the rule is eligible to be executed, provide the
UUID‟s of the all the sites that are attached to the EA‟s parties.

4.02
4.02

For each UUID, check if a match is found based on the business approved VMware
hierarchy.
If a match is found, retrieve EA‟s for all the records in the hierarchy including the input
record. Set the „Company Master‟ flag to „S‟ for all of the EA‟s retrieved.
If a match is not found, check if a match is found based on the default VMware
hierarchy. If found, retrieve EA‟s for all the records in the hierarchy including the input
record. Set the „Company Master‟ flag to „W‟ for all of the EA‟s retrieved.

FR-IB-ELA-48.5

VMware

From all the EA‟s collected for Company mater rules, Return unique EA‟s with the
„Company Master‟flag strength set to the highest gathered for the EA

CONFIDENTIAL

4.01, 4.02

Page 46 of 69

5.4.11

Normalized Name

5.4.11.1 To-Be Flow

Start

For each EA found
based on all other
rules executed till
now and the EA’s
Provided as input

For each Account ID
Provided as input

Eligibility
Eligibility

Find other EA’s that
have the same UCM
account normalized
name

Check if
any EA's UCM account
normalized names =
Normalized SFDC
Account name

Find the related
SFDC account
normalized name

No

First
EA’s UCM account normalized
name = First 8 characters of
SFDC account normalized
name

End

Yes
Check if
Exact match is found
based on normalized
names

No

Set Name flag as ‘S’
(Strong)

Yes

First
EA’s UCM account normalized
name = First 8 characters of
any other EA’s UCM account
normalized name

No

Yes
with the highest
strength found.

Set Name flag as ‘W’
(Weak)

Yes

No

End

5.4.11.2 Steps
FR Number

FR Description

FR-IB-ELA-48.6

VMstar Account to Normalized Name Rule (Standard): For each Account ID entered and
if the rule is eligible to be executed, find the accounts normalized name.
Check if account normalized names is equal to any EA‟s UCM party normalized name. If
a match is found add all the EA‟s that have the same UCM party normalized name to the
list and set the „Normalized Name‟ flag to „S‟ for all of the EA‟s.
If a match is not found, check first 8 characters of the account normalized name is equal
to first 8 characters of any other EA‟s UCM party normalized name. If a match is found
add all the EA‟s that have the same UCM party normalized name to the list and set the

VMware

CONFIDENTIAL

BR Number
4.8.1

Page 47 of 69
„Normalized Name‟ flag to „W‟ for all of the EA‟s.

FR-IB-ELA-48.7
FR-IB-ELA-48.8

based on all the rules executed
EA Number to Normalized Name Rule (Standard): For each EA Number entered or
gathered based on standard rules and if the rule is eligible to be executed, find other
EA‟s that have the same UCM party normalized name.

4.8.2
4.8.2

If found, add all the EA‟s that have the same UCM party normalized name to the list and
set the „Normalized Name‟ flag to „S‟ for all of the EA‟s.
If not found, check if the first 8 characters of the input EA‟s UCM party normalized name
is equal to first 8 characters of any other EA‟s UCM party normalized name. If the input
EA type is not equal to „PERSON‟ then do not considerEA‟s of the type „PERSON‟ in the
target list. However, if the input EA type is equal to „PERSON‟ then consider all EA‟s in
the target list.
If a match is found add all the EA‟s that have the same UCM party normalized name to
the list and set the „Normalized Name‟ flag to „W‟ for all of the EA‟s.

FR-IB-ELA-48.9

From all the EA‟s collected for Normalized Name rules, Return unique EA‟s with the
„Normalized name‟ flag strength set to the highest gathered for the EA

4.8.1, 4.8.2

5.5 Retrieve and Manage Saved EA Relationships

Wireframe-IB-ELA-14

FR Number

FR Description

FR-IB-ELA-49

Saved EA relationships can be accessed by all users that currently have access to the
EA research tool. This will be a second tab on the EA research portal

FR-IB-ELA-50

User should be able to select either the VMStar Account ID (default) or the EA Number.
Once selected they can enter the corresponding value. This can be analpha-numeric
value. They can also click on the lookup to search and select the respective values.

FR-IB-ELA-50.1

VMware

This is a mandatory value
If the user clicks on the „Lookup‟ button, a new overlay will be opened and will have the

CONFIDENTIAL

BR Number
7.02

7.02

7.02

Frd x el_arate_ea_researchtool

Frd x el_arate_ea_researchtool

Recommended

Recommended

More Related Content

What's hot

What's hot (19)

Similar to Frd x el_arate_ea_researchtool

Similar to Frd x el_arate_ea_researchtool (20)

Recently uploaded

Recently uploaded (20)

Frd x el_arate_ea_researchtool