We are going to set up the following environment:
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
#!/bin/bash | |
usage="usage: $(basename "$0") [-h | --help] --saga=<name> --event=<name> --source=<name> --target=<name> | |
where: | |
-h, --help show this help text | |
-saga Saga name, e.g. 'Onboarding' (creates a platform event Onboarding__e) | |
-event Event type name, e.g. 'NewLead' | |
-source The Apex type to convert from, e.g. LeadService.NewLeadResult | |
-target The Apex type to convert to, e.g. RestCalloutService.RestCallout" |
Recently I was tasked with figuring out how many opportunities changed the stage from, say, Stage1
to Stage2
during the last month. First, let's walk through OpportunityHistory and retrieve all the changes that we are interested in:
$ sfdx force:data:soql:query -u pro -r csv -q \
"select Id, OpportunityId, CreatedDate, StageName
from OpportunityHistory
http://plantuml.com/use-case-diagram
@startuml
left to right direction
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
<apex:page> | |
<h1>First Step</h1> | |
<apex:pageBlock> | |
<apex:outputLink value="#" onclick="nextStep();">Next Step</apex:outputLink> | |
</apex:pageBlock> | |
<apex:includeScript value="/support/console/45.0/integration.js"/> | |
<script type="text/javascript"> | |
function nextStep(){ | |
if(sforce.console.isInConsole()){ |
NewerOlder