Cockpit Objects
Cockpit Objects
Some of the most important Gainsight objects used in the Cockpit and Success Plans modules are described here.
Call To Action
This object is used in Cockpit and Call to Action (CTA). For example; Rules/Reports on CTAs and Success Plans (complete or incomplete, overdue, etc).
The following table lists the data fields available in this object:
Field Name | Description |
---|---|
Company | The name of the Company. |
Age | For how long a CTA is open (Closed Date - Created Date) or (Today - Created Date). |
Assignee | The assignee of the CTA. User information from the Gainsight object User is fetched here. This field is under the Owner (Lookup) object as Name field. |
Call To Action Parent Id | This is used to store the parent CTA Id from which the current CTA is generated. This field is applicable to Recurring Lifecycle CTAs. |
Closed Date | CTA Closed Date. |
Closed Overdue | Flag that indicates whether a task is closed after the Due Date. |
Closed Task Count | The number of CS Tasks that are closed in a CTA. |
Close Source | This indicates how a CTA was closed. For example; Manually, By Rules, etc. |
Created Date | Created date of a CTA. |
CTA Group | This field helps fetch fields from the CTA Group object that has Success Plans information. |
Days Due | The number of days due to close a CTA (Original Due Date - Created Date). |
Days Past Due Date | The number of days past the due date of a CTA. |
Days Until Close | Number of days due to close a CTA from today (Due date - Today). |
Dependency Meta |
This is used to store the Gantt Chart dependencies and is used internally only. |
Due Date | Due date of a CTA. |
Due Date Variance | Number of days that a CTA due date is changed by (New Due Date - Old Due Date). |
Entity Type | Company/Relationship. |
Event Properties |
This is used to store recurring CTA information. |
Final Milestone | It stores the Closed Milestone information (Name, etc.) associated with a CTA (If it is associated). |
Flagged | It indicates whether a CTA is flagged. |
GS Recommended | Flag that Indicates whether a CTA is recommended by Gainsight, prioritized according to ARR, customer health, renewal date, NPS® score, CTA due date and priority. |
GS Score | Score assigned to a CTA for Gainsight recommendation based on the above parameters. |
GS Score Updated on | The date on which a CTA score is updated. |
Is a Draft | Flag that indicates whether an objective which is linked to a success plan is in Draft state. |
Is Closed | It indicates whether a CTA is closed. |
Is Recurring | Flag that indicates whether a CTA is part of Recurring CTAs (True/False). |
Milestone | It stores the Open Milestone Information (Name, etc.) associated with a CTA. |
Milestone Enabled | Flag that indicates whether a Milestone is associated with a CTA (True/False). |
Open Task Count | The number of Tasks currently in an ‘Open’ state in a CTA. |
Original Due Date | The original due date of a CTA. |
Overdue | Status of a CTA whether it is past the due date (True/False). |
Overdue Type | Overdue/Due in Next 7 Days/Open (Due in more than 7 days). |
Percent Complete | The Percentage of the Tasks closed in a CTA (Closed Task Count/Total Task Count). |
Playbook | Name of a Playbook. |
Priority | The priority status of a CTA. |
Reason | The reason of a CTA. |
Relationship | Name of Relationship to which the CTA belongs. |
Relationship Type | Name of a Relationship Type to which a CTA type belongs. |
Rule Action Id | Rules Action from which a CTA is generated. Note: When a Rule or Action setup is updated, corresponding Rule ID and Action ID are not updated. Value in this field is not changed for a specific CTA record. |
Snoozed | Flag that indicates whether a CTA is snoozed (True/False). |
Snoozed on | Date on which a CTA is snoozed. |
Snoozed until | Date & Time until which a CTA is snoozed. |
Snooze Reason | The reason of snooze for a CTA |
Source | Source from which a CTA is generated (Manual/Rules/Survey/Activity/Advanced Outreach (Program)/Zendesk).
|
Status | The status of a CTA. |
Task Count | The number of Tasks in a CTA. |
Type Name | The CTA type name. |
CS Task
This object is used in Calls to Action and CS Tasks. For example; Reports on the CS Tasks (complete or incomplete, overdue, etc).
The following table lists the data fields available in this object:
Field Name | Description |
---|---|
Company | Company Name in Gainsight (GSID). |
Assigned | To whom a CS Task is assigned (GSID). This field helps fetch the user information from the Gainsight object User. |
Auto sync | Flag that indicates whether a task is auto synced to Gainisght or not. |
Call to Action | It contains parent CTA to which this task belongs. |
CTA Status | It indicates status of parent CTA. |
Closed Date | Closed date of a CS Task. |
Closed Overdue | Flag that indicates whether a task is closed after the Due Date. |
Created Date | Created date of a CTA Task. |
Days Due | The number of days assigned to close a CS Task from created date (Original Due Date - Created Date). |
Days Past Due Date | The number of days that a CTA Task passed the due date. |
Days to Close | The number of days that a CS Task is open from the created date. (Closed Date - Created Date). |
Days Until Close | The number of days due to close from today (Due date - Today). |
Delta days | The number of days that a Task is open between the Due date and created date. (Due Date - Created Date). |
Due Date | The due date of a CTA Task. |
Due Date Variance | The number of days that a Task due date is changed by (New Due Date - Old Due Date). |
Is Closed | Status of a Task whether it is Closed or not. |
Is Email Sent | Indicates whether email is sent from Cockpit for this task (Email Assist Tasks). |
Original Due Date | The original due date of the CTA Task. |
Overdue | The status of a Task whether it is past the due date. |
Parent | Dependent Task name to which current task has a dependency. (For example: If a task due date is scheduled in dependence with another task closed date). |
Playbook | The name of the Playbook that the Task is retrieved from. |
Priority | Priority of a Task (Low/Medium/High/etc). |
Source | The source from which the CS task is created. Manual = created by a user, Activity = created from a timeline entry, from Rules, Survey, etc. |
Status | Indicates the status of a Task (Open/Closed/etc.). |
Subject | The subject of the task name. |
Timeline Activity Id | This field helps fetch information of an email activity in Timeline that the current CS Task is generated from. |
To Email Type | The type (Contact/User/Manual) of To email address used to send email. |
Type | The type of a CTA Task. |
Type Name | Indicates, if this is a standard task or an email assist task. |
Unique Identifier with in playbook | The Unique identifier of a Playbook. |
Next Action Due Date | This object stores information about the upcoming actions and their corresponding due dates. |
Playbook
This object is used in Playbooks.
The following table lists the data fields available in this object:
Field Name | Description |
---|---|
Created By | The user who created the Playbook. |
Created Date | The date on which the Playbook was created. |
CTA Type | The CTA type name. |
Deleted | Flag that indicates whether the Playbook is deleted. |
Description | The information related to the Playbook. |
Entity Type | Account/Relationship. |
Id | This is used to store the parent CTA Id from which the current playbook is generated. |
Is Active | It is of datatype Boolean (True/False). It indicates whether a user is active or not. |
Is Auto Sync Enable | Flag that indicates whether a playbook is auto synced to SFDC or not. |
Modified By | User who last modified the Playbook. |
Modified Date | The date on which the Playbook was last modified. |
Name | The name of the Playbook. |
Relationship Type | Name of a Relationship Type to which Playbook belongs. |
Sync Status | The sync status of a Playbook. |
Task Count | The total number of CS Tasks in which this Playbook is used. |
Used Count | The total number of CTA in which this Playbook is used. |
Cockpit Associated Records
This object is used to get data on SP templates and linked objects. For example; how to build report on SP templates and Linked Objects.
The following table lists the data fields available in this object:
Field Name | Description |
---|---|
Created By | The user who created this record. |
Created Date | The date on which this record was created. |
CTA | The name of the CTA associated with this record. |
External Object | The object that is used to store external IDs associated with this record. |
Id | This is used to store the parent CTA Id from which the current playbook is generated. |
Modified By | User who last modified the record. |
Modified Date | The date on which the record was last modified. |
Success Plan | The name of the success plan template that is associated with this record. |
Task | The name of the task that is associated with this record. |
Reporting Category
The following table lists the data fields available in this object:
Field Name | Description |
---|---|
Display Order | Display order of the library questions while configuring a reporting category. |
Id | This is used to store the parent CTA Id from which the current playbook is generated. |
Name | The name of the category. |
Type | The type of reporting category. |