...
Business Requirement
Please check this miro Miro page for detailed changes
AS IS | TO BE |
|---|---|
 |  |
| Miro macro resizing | ||
|---|---|---|
|
Re-layout the fields accordingly
The following fields are no longer in the layout :
Table 1.1
Field | Field Created By | Purpose | Comments | Reason |
|---|---|---|---|---|
Anonymous | Affinaquest | If checked, this Opportunity should be considered anonymous | 16 Opportunities have this flag ticked (18) | This data can be acquired in the anonymity level field. |
|
|
|
|
|
Private | Salesforce | A private Opportunity will only be visible to the owner and those with View/Modify all access on Opportunities | 0 Opportunities have this flag ticked | Field not used |
OMI | Affinaquest | The Opportunity Management Index (OMI) is a visual indicator of progress of the Opportunity toward funding, based on the number of stars. It is based on the Date, the Probability, the amount of time in the current Stage, and the last and next Activity | Does not populate as Advancement doesn’t use Activity | Remove as not used. |
Next Task | Affinaquest | The flag indicates status of the next Task for the Opportunity. Green - Task due date is at least 14 days away. Yellow - Task due date is within 14 days. Red - Task is overdue or no Activity is scheduled | Doesn’t populated as Advancement doesn’t use Activity | Tasks are currently set as private to mitigate risks associated with well-being data. As a result of the tasks being private DO’s cannot track tasks once they have been assigned. The task related fields should be removed from the opportunity page-layout, and we can consider adding them back in when we implement SF Activity. |
Next Task Date | Affinaquest | The date of the next Task that is scheduled for this Opportunity | 251 Opportunities have Next Task Date populated | Same as above. |
Credited Date | Advancement | There is no documentation in Salesforce or Jira to indicate the purpose of this field | 12 Opportunities have the Credited Date populated | GI advised that this was a GA field and GA have stated that they do not operate in the opportunity. As only 12 opportunities have this field populated, the field will be removed. |
Highlights Section will not be used anymore
Key (Important) fields per stage
Table 1.2
Stage | Identification | Qualification | Planning | Solicitation | Lost | Gift handover | Won |
|---|---|---|---|---|---|---|---|
KF1 | Amount | Amount | Acceptance from delegate | Verbal acceptance
| Closed date | Verbal acceptance | Amount |
KF2 | Lead source | Strategy | Ask made? | Gift date | Closed lost reason | Donor expectations apply | Funding complete |
KF2 | Primary campaign source | Next step | Ask amount | Gift Amount |
| Chart of accounts |
|
KF4 | Strategy |
| Strategy | Gift theme |
| Type |
|
KF5 | Next step | Next Step | Prospect pool | Sub-type |
Analysis on Persona
Why are we doing this?
...
USyd - AQ Lightning Outright Gift Admin
Upon further analysis, there is an opportunity to consolidate these two page layouts into one. Their difference is that the Admin one which is assigned to DRS profile gets access to Opportunity Split related list as in the screenshot below. Confirmed with Yeng Sembrano that Opportunity split is only used by DRS users and therefore, we can have a combined page layout which through dynamic form can conditionally show and hide this related list. There is also an opportunity to use the new opportunity split component. This idea is taken from this source https://www.salesforceben.com/how-to-use-opportunity-splits-in-salesforce/
...
Opportunity Validation Rules
...