This article will go over GenRocket Terminology and how it applies to generating test data for Salesforce. Examples are also given to show analogies between GenRocket Terminology to Salesforce Terminology.
These terms define the core components and key GenRocket functionality:
- Domain - A GenRocket Domain defines real world objects. Think of a Domain as a noun (person, place, or thing). A GenRocket Domain is analogous to a Salesforce Object (account, contact, opportunity, etc.).
- Attribute - A GenRocket Attribute defines a characteristic of a GenRocket Domain. A GenRocket Attribute is analogous to a Salesforce Object field (name, date, price, etc.).
- Generator - A GenRocket Generator generates a specific type of data. An Attribute must be assigned a Generator in order to generate data. Generators will allow you to create the type of synthetic data you require to populate your Salesforce Objects.
Example: A firstName Attribute uses the NameGen Generator to provide a first name for each record (Mary, Sam, Jill, etc.).
- Receiver - A GenRocket Receiver receives data generated from the Attributes of a Domain and morphs the data into a usable format. GenRocket uses the SFObjectInsertReceiver to insert generated data into a Salesforce Object via REST web services.
- Scenario - A GenRocket Scenario defines the instructions for generating data. Scenarios that use Salesforce specific Generators and Receivers can be executed from the GenRocket web platform to generate and insert data into Salesforce Objects in real time.
- Parent/Child vs Master-Detail - In GenRocket, the Parent-Child relationships between Domains is analogous to Master-Detail relationships in Salesforce.
- Sibling vs Lookup - In GenRocket, the Sibling relationship between Domains is analogous to Lookup Object relationships in Salesforce.
The following video goes over the GenRocket Terminology discussed above: