Page tree

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

NEW / Next release

R-2314 / Change about massa risus, vestibulum in nunc vitae, sagittis dignissim est.


 

1. Functional Process

Process Overview

A Competitive Insight summarizes the market intelligence gathered from business interactions with the accounts. It helps building the business context in order to better define value propositions to the market.

A Competitor object record summarizes basic information about a Solvay’s competitor such as its name, its city, its country, etc. Additional market information that involves a competitor can be found in the competitive insights records related to it.

Flow


2. Data Model & security

Main objects

 

 

Related Objects



Competitor Visibility and Rights

Who can create?

All the users (see section 3.9.5.1 Competitor Creation Process) can create a competitor

Who can see?

All the users can see all the competitor

Who can update?

Only the GBU Data Steward and the System Administrator

Who can delete?

Only the System Administrator can delete a Competitor

 

3. Specific rules & automation

Competitor Creation Process 

 

Competitor creation can be done by any user. De-duplication rules are set on the name and on the city, and will notify the users in case of any duplicates found but do not block the competitor creation. 

Once the competitor is created, it is sent for approval to the Data Steward of the GBU for which the competitor is created:

A picklist “Status” is available on the Competitor page in order to define the status of the Competitor. Following values are available:

  • Requested for approval
  • Approved
  • Rejected

Only competitor with status “validated” can be used during the creation of a competitive insight; it means if the competitor is not validated by the GBU Data Steward, it can’t be used in the CRM.

 

Competitor Email trigger

Saving a new Competitor record after creation triggers a validation workflow and a request email sent to the GBU Data Steward (Queue defined based on the field “GBU”). The email will contain the following text, and will be sent in the formal Solvay template:

4. History

Product information section on Opportunity product used to be a custom object because the visibility of the section was different of the visibility of the rest of the opportunity. Today visibility is the same so all fields have been re-created in opportunity product and all features plugged on the previous custom object are/will be plugged on opportunity product directly.


 

 

Last modifications :

UserLast Update
Julien Andreoli-ext 2677 days ago
Laura THEOLIER-EXT 2725 days ago
BRAHIM, Walid
KANJA-ext, Zakaria
NWANGWU, Daniel

 

The best way to get IT support is to use the new Service One Platform.