Home

Static Field Glossary

"Static" fields are collected record data standard across all Case IQ applications and essential to application function. While "Dynamic" fields are the text boxes, buttons, picklists, etc. added by a user with the Form Builder (see Use the Form Builder), users cannot edit or delete static fields on record forms. Static fields can be automatically populated by the system, such as the “Created Date” field, or record user input, for example the "Assign Reason" field.

Case Fields

Static Field	Field Data	Data Type	Field Name Tag
Assign Reason	The reason provided when a user is assigned as a case's owner.	Text	reassignReason
Assigned By	The user who assigned the case's owner. If the case was assigned as a result of a rule action, the "Assigned By" field will be "System".	User	The “Assigned By” field has multiple tags that pull in different data types: assignedBy: the user profile's ID. This is an ID data type. If you use “assignedBy” in an ISEL expression to compute a textbox, text area, or text editor field, the system will use the user profile's unformatted alphanumeric user ID (e.g. 9fef89d3-28fc-4520-9404-0f3435633c9d). Make sure the computed field is a user or user multiple field if you want the system to use the user profile's name. assignedBy__name: the user profile's name in text format. The “assignedBy__name” tag will use the user profile's name in an ISEL expression to compute a textbox, text area, or text editor field. However, this tag will not work for user or user multiple fields. assignedBy__active: whether the user profile is active in Boolean format. This means the data populated by the “assignedBy__active” tag will be either “Yes” or “No”. assignedBy__email: the user profile's email address. This means the data populated by the “assignedBy__email” tag will be an email address (e.g. jsmith@caseiq.com).
Case Cancel Date	The date and time a case was cancelled.	Date and Time	cancelDate
Case Cancel Reason	The reason provided by the user that cancelled the case.	Text	cancelReason
Case Owner	The user assigned responsibility of the case.	User	owner
Case State	Indicates if the case is open or closed depending on its workflows. If a case has more than 1 workflow, the case state will be closed when the last workflow is moved to a “closed” status.	Status ID	caseState
Case Type	The category of the case based on the kind of issue, concern, or incident described in the case record.	Picklist	caseType
Closed Calendar Month	The month in which the case was closed, presented as the month's numerical order on the calendar, e.g. 1 = January and 10 = October.	Number	closedCalendarMonth
Closed Calendar Quarter	The calendar quarter in which the case was closed as a number, e.g. 3 = the third quarter of the year.	Number	closedCalendarQuarter
Closed Calendar Week	The week in which the case was closed, presented as the week's numerical order on the calendar, e.g. the week of August 15, 2022, would be 34. A week begins on Sunday.	Number	closedCalendarWeek
Closed Calendar Year	The year in which the case was closed.	Number	closedCalendarYear
Closed Fiscal Month	The fiscal month in which the case was closed, presented as the month's numerical order on your organization's fiscal calendar. For example, if your company's fiscal year starts on April 1, October would be 7.	Number	closedFiscalMonth
Closed Fiscal Quarter	The fiscal quarter in which the case was closed, presented as the quarter's numerical order on your organization's fiscal calendar. For example, if your company's fiscal year starts on April 1, October would be in fiscal quarter 3.	Number	closedFiscalQuarter
Closed Fiscal Week	The fiscal week in which the case was closed, presented as the week's numerical order on your organization's fiscal calendar. For example, if your company's fiscal year starts on April 1, April 13, 2022, would be fiscal week 2. A week begins on Sunday.	Number	closedFiscalWeek
Closed Fiscal Year	The fiscal year in which the case was closed. For example, if your company's fiscal year starts on April 1, February 2023 would be "fiscal year 2022".	Number	closedFiscalYear
Confidential	Indicates whether a case has been set to "Confidential", meaning that it can only be viewed by users who have permissions to access confidential cases.	Boolean	confidential
Created By	The user that added the case to the Case IQ application. This means that they submitted the New Case form, sent an email that triggered a New Case Creation rule, or filed their concern via the online portal.	User	The “Created By” field has multiple tags that pull in different data types: createdBy: the user profile's ID. This is an ID data type. If you use “createdBy” in an ISEL expression to compute a textbox, text area, or text editor field, the system will use the user profile's unformatted alphanumeric user ID (e.g. 9fef89d3-28fc-4520-9404-0f3435633c9d). Make sure the computed field is a user or user multiple field if you want the system to use the user profile's name. createdBy__name: the user profile's name in text format. The “createdBy__name” tag will use the user profile's name in an ISEL expression to compute a textbox, text area, or text editor field. However, this tag will not work for user or user multiple fields. createdBy__active: whether the user profile is active in Boolean format. This means the data populated by the “createdBy__active” tag will be either “Yes” or “No”. createdBy__email: the user profile's email address. This means the data populated by the “createdBy__email” tag will be an email address (e.g. jsmith@caseiq.com).
Created Calendar Month	The month in which the case was created, presented as the month's numerical order on the calendar, e.g. 1 = January and 10 = October.	Number	createdCalendarMonth
Created Calendar Quarter	The calendar quarter in which the case was created as a number, e.g. 3 = the third quarter of the year.	Number	createdCalendarQuarter
Created Calendar Week	The week in which the case was created, presented as the week's numerical order on the calendar, e.g. the week of August 15, 2022, would be 34. A week begins on Sunday.	Number	createdCalendarWeek
Created Calendar Year	The year in which the case was created.	Number	createdCalendarYear
Created Date	The date and time a case draft was saved, which is functionally when the case was added to the application. The system will save a case draft when adding files or parties from the New Case form. The system will consider the date and time the user saves the New Case form as the case draft if the user does not add files or parties via the New Case form. In the latter scenario, the "Date Recorded" and "Created Date" fields will contain the same date and time.	Date and Time	createdDate
Created Fiscal Month	The fiscal month in which the case was created, presented as the month's numerical order on your organization's fiscal calendar. For example, if your company's fiscal year starts on April 1, October would be 7.	Number	createdFiscalMonth
Created Fiscal Quarter	The fiscal quarter in which the case was created, presented as the quarter's numerical order on your organization's fiscal calendar. For example, if your company's fiscal year starts on April 1, October would be in fiscal quarter 3.	Number	createdFiscalQuarter
Created Fiscal Week	The fiscal week in which the case was created, presented as the week's numerical order on your organization's fiscal calendar. For example, if your company's fiscal year starts on April 1, April 13, 2022, would be fiscal week 2. A week begins on Sunday.	Number	createdFiscalWeek
Created Fiscal Year	The fiscal year in which the case was created. For example, if your company's fiscal year starts on April 1, February 2023 would be "fiscal year 2022".	Number	createdFiscalYear
Date Assigned	The date and time the case's owner was assigned.	Date and Time	dateAssigned
Date Closed	The date and time a case was closed.	Date and Time	dateClosed
Date Purged	The date and time a case was purged.	Date and Time	datePurged
Date Recorded	The date and time a case was initially saved and the system assigned it a case number. This will always occur when the New Case form is saved. As a result, the "Date Recorded" and "Created Date" fields will contain the same date and time if the user does not add files or parties from the New Case form.	Date and Time	dateRecorded
Date Submitted	The date a case was created.	Date	dateSubmitted
Do not Purge	Indicates whether a case has been set to "Do not Purge", or if the case can be deleted in record purges.	Boolean	excludeFromPurge
External	Indicates whether a case was submitted via the application's portal.	Boolean	externalRecord
Investigative Team Members	The users on the case's Investigative Team.	User Multiple	investigativeTeamMembers
Last Flag Set	The name of the flag most recently set to the case.	flagName	lastFlagSet
Last Flag Set By	The user who set the most recent flag for the case.	User	The “Last Flag Set By” field has multiple tags that pull in different data types: lastFlagSetBy: the user profile's ID. This is an ID data type. If you use “lastFlagSetBy” in an ISEL expression to compute a textbox, text area, or text editor field, the system will use the user profile's unformatted alphanumeric user ID (e.g. 9fef89d3-28fc-4520-9404-0f3435633c9d). Make sure the computed field is a user or user multiple field if you want the system to use the user profile's name. lastFlagSetBy__name: the user profile's name in text format. The “lastFlagSetBy__name” tag will use the user profile's name in an ISEL expression to compute a textbox, text area, or text editor field. However, this tag will not work for user or user multiple fields. lastFlagSetBy__active: whether the user profile is active in Boolean format. This means the data populated by the “lastFlagSetBy__active” tag will be either “Yes” or “No”. lastFlagSetBy__email: the user profile's email address. This means the data populated by the “lastFlagSetBy__email” tag will be an email address (e.g. jsmith@caseiq.com).
Last Flag Set Date	The date and time the most recent flag was set for the case.	Date and Time	lastFlagSetDate
Last Flag Set Name	The name of the most recent flag set to the case.	Text	lastFlagSetName
Last Snapshot Generation Date	The date and time the system most recently took a snapshot of the case to generate suggested case links.	Date and Time	lastSnapshotGenerationDate
Last Updated By	The user who most recently updated the case.	User	The “Last Updated By” field has multiple tags that pull in different data types: lastUpdatedBy: the user profile's ID. This is an ID data type. If you use “lastUpdatedBy” in an ISEL expression to compute a textbox, text area, or text editor field, the system will use the user profile's unformatted alphanumeric user ID (e.g. 9fef89d3-28fc-4520-9404-0f3435633c9d). Make sure the computed field is a user or user multiple field if you want the system to use the user profile's name. lastUpdatedBy__name: the user profile's name in text format. The “lastUpdatedBy__name” tag will use the user profile's name in an ISEL expression to compute a textbox, text area, or text editor field. However, this tag will not work for user or user multiple fields. lastUpdatedBy__active: whether the user profile is active in Boolean format. This means the data populated by the “lastUpdatedBy__active” tag will be either “Yes” or “No”. lastUpdatedBy__email: the user profile's email address. This means the data populated by the “lastUpdatedBy__email” tag will be an email address (e.g. jsmith@caseiq.com).
Last Updated Date	The date and time the case was most recently updated.	Date and Time	lastUpdatedDate
Last Workflow	The workflow which most recently progressed for the case, i.e. the workflow that a user most recently moved to its next step.	Text	lastWorkflowId
Last Workflow Status	The status of the workflow that was most recently moved to its next step.	Status ID	lastWorkflowStateId
Last Workflow Step By	The user who progressed the most recent workflow to its next step.	User	The “Last Workflow Step By” field has multiple tags that pull in different data types: lastWorkflowTransitionBy: the user profile's ID. This is an ID data type. If you use “lastWorkflowTransitionBy” in an ISEL expression to compute a textbox, text area, or text editor field, the system will use the user profile's unformatted alphanumeric user ID (e.g. 9fef89d3-28fc-4520-9404-0f3435633c9d). Make sure the computed field is a user or user multiple field if you want the system to use the user profile's name. lastWorkflowTransitionBy__name: the user profile's name in text format. The “lastWorkflowTransitionBy__name” tag will use the user profile's name in an ISEL expression to compute a textbox, text area, or text editor field. However, this tag will not work for user or user multiple fields. lastWorkflowTransitionBy__active: whether the user profile is active in Boolean format. This means the data populated by the “lastWorkflowTransitionBy__active” tag will be either “Yes” or “No”. lastWorkflowTransitionBy__email: the user profile's email address. This means the data populated by the “lastWorkflowTransitionBy__email” tag will be an email address (e.g. jsmith@caseiq.com).
Last Workflow Step Date	The date and time the most recent workflow was progressed to its next step.	Date and Time	lastWorkflowTransitionDate
Last Workflow Step Reason	The reason provided when a user most recently moved a workflow to its next step.	Picklist	lastWorkflowTransitionReason
Open Business Days	The number of weekdays the case has been open, excluding holidays. The system will omit weekends and holidays and will only calculate it when the case is closed.	Number	openBusinessDays
Open Calendar Days	The total number of days a case has been open, including weekends and holidays. This will only be calculated when the case is closed.	Number	openCalendarDays
Pending Purge Date	The date and time the case has been scheduled to be purged.	Date and Time	pendingPurgeDate
Primary Party	The party set as primary for the case.	Party	primaryPartyId. This is an ID data type. If you use “primaryPartyId” in an ISEL expression to compute a textbox, text area, or text editor field, the system will use the primary party's unformatted alphanumeric user ID (e.g. b6a6cdf6-cfa5-4e8e-95eb-161cc61ab5a0). Make sure the computed field is a party selection field if you want the system to use the primary party's name.
Purge Reason	The reason provided when a case was scheduled to be purged.	Picklist	purgeReason
Record Source	The method by which the case was added to the system, i.e. web, external, or email.	Picklist	recordSource
Reported Anonymously	Indicates whether the case's reporter chose to remain anonymous when submitting the case via the application's portal.	Boolean	reportedAnonymously
Reported By	The name of the individual who reported the case.	Text	reportedBy
[Workflow]*	The current status of the workflow for the case.	Status ID	[workflowName]. E.g. for a workflow named "General Investigation", the tag would be "generalInvestigation".
[Workflow]* Date	The date and time the workflow entered the current status.	Date and Time	[workflowName]Date. E.g. for a workflow named "General Investigation", the tag would be "generalInvestigationDate".
[Workflow]* Reason	The reason provided when a user set the workflow to its current status.	Picklist	[workflowName]Reason. E.g. for a workflow named "General Investigation", the tag would be "generalInvestigationReason".
[Workflow]* Set By	The user who set the current status of the workflow for the case.	User	The “[Workflow]* Set By” field has multiple tags that pull in different data types. Include the workflow's name in place of [workflowName] in the following tags. [workflowName]SetBy: the user profile's ID. This is an ID data type. If you use “[workflowName]SetBy” in an ISEL expression to compute a textbox, text area, or text editor field, the system will use the user profile's unformatted alphanumeric user ID (e.g. 9fef89d3-28fc-4520-9404-0f3435633c9d). Make sure the computed field is a user or user multiple field if you want the system to use the user profile's name. [workflowName]SetBy__name: the user profile's name in text format. The “[workflowName]SetBy__name” tag will use the user profile's name in an ISEL expression to compute a textbox, text area, or text editor field. However, this tag will not work for user or user multiple fields. [workflowName]SetBy__active: whether the user profile is active in Boolean format. This means the data populated by the “[workflowName]SetBy__active” tag will be either “Yes” or “No”. [workflowName]SetBy__email: the user profile's email address. This means the data populated by the “[workflowName]SetBy__email” tag will be an email address (e.g. jsmith@caseiq.com).
Source Job	The name of the integration log that created the case.	Text	sourceJob
Terms and Conditions	Indicates whether the case's reporter accepted the portal's terms and conditions before submitting the case.	Boolean	acceptTermsAndConditions
Total Business Days	The total number of business days since a case was created, including days the case was closed but excluding holidays and weekends. This will only be calculated when the case is closed.	Number	totalBusinessDays
Total Calendar Days	The total number of days since a case was created, including weekends, holidays, and days the case was closed. This will only be calculated when the case is closed.	Number	totalCalendarDays
User Denied Access	The users on the case's Denied Access List.	User Multiple	userBlacklist
Workflow Statuses	The current status of all workflows applicable to the case, presented as a list.	Text	workflowStatuses

*The name of a workflow in your application will be in place of "[workflowName]" for each field. Each workflow will have its own status, date, reason and set by fields.

Profile Fields

Static Field	Field Data	Data Type	Field Name Tag
Address	The address of the profile provided by a user.	Text	address
City	The city of the profile provided by a user.	Text	city
Country	The country of the profile provided by a user.	Picklist	country
Created By	The user that added the profile to the Case IQ application by submitting the New Profile form.	User	createdBy
Created Date	The date and time a profile was created.	Date and Time	createdDate
Date of Birth	The date of birth of the profile provided by a user.	Date	dateOfBirth
Date Purged	The date and time a profile was purged.	Date and Time	datePurged
Date Submitted	The date a profile was submitted.	Date	dateSubmitted
Do not Purge	Indicates whether a profile has been set to "Do not Purge", or if the profile can be deleted in record purges.	Boolean	excludeFromPurge
Email address	The email address of the profile provided by a user.	Email	emailAddress
Exclude From Suggest Links	Indicates if your application will search the profilerecord for similar values when suggesting related cases.	Boolean	excludeFromSuggestedLinks
First Name	The first name of the profile provided by a user.	Text	firstName
Home Phone #	The home phone number of the profile provided by a user.	Phone Number	homePhone
Last Name	The last name of the profile provided by a user.	Text	lastName
Last Snapshot Generation Date	The date and time the system most recently took a snapshot of the profile to generate suggested case links.	Date and Time	lastSnapshotGenerationDate
Last Updated By	The user who most recently updated the profile.	User	lastUpdatedBy
Middle Initial	The middle initial of the profile provided by a user.	Text	middleInitial
Name	The first and last name of the profile. The system automatically concatenates the text in the profile's “First Name” and “Last Name” fields.	Text	personName
Pending Purge Date	The date and time the profile has been scheduled to be purged.	Date and Time	pendingPurgeDate
Profile Picture	The image file uploaded to the profile by a user.	Image	picture
Purge Reason	The reason provided when a profile was scheduled to be purged.	Picklist	purgeReason
Record Source	The method by which the profile was added to the system, i.e. web, external, or email.	Picklist	recordSource
Source Job	The name of integration log that created the profile.	Text	sourceJob
State / Province	The state or province of the profile provided by a user.	Picklist	stateProvince
System Processing	Indicates if the profilerecord is currently being used in a process.	Boolean	sysProcessing
Work Phone #	The work phone number of the profile provided by a user.	Phone Number	workPhone
Zip Code / Postal Code	The zip or postal code of the profile provided by a user.	Postal Code	zipCodePostalCode

To-Do Fields

Static Field	Field Data	Data Type	Field Name Tag
Assigned By	The user who assigned the to-do's owner.	User	The “Assigned By” field has multiple tags that pull in different data types: assignedBy: the user profile's ID. This is an ID data type. If you use “assignedBy” in an ISEL expression to compute a textbox, text area, or text editor field, the system will use the user profile's unformatted alphanumeric user ID (e.g. 9fef89d3-28fc-4520-9404-0f3435633c9d). Make sure the computed field is a user or user multiple field if you want the system to use the user profile's name. assignedBy__active: whether the user profile is active in Boolean format. This means the data populated by the “assignedBy__active” tag will be either “Yes” or “No”. assignedBy__email: the user profile's email address. This means the data populated by the “assignedBy__email” tag will be an email address (e.g. jsmith@caseiq.com). assignedBy__name: the user profile's name in text format. The “assignedBy__name” tag will use the user profile's name in an ISEL expression to compute a textbox, text area, or text editor field. However, this tag will not work for user or user multiple fields.
Item Number	The full identification number of the to-do, which includes the to-do's case number followed by its own number, e.g. "2024-005 / 2"	ID	childNumber
Closed by	The user who marked the to-do as complete.	User	The “Closed By” field has multiple tags that pull in different data types: closedBy: the user profile's ID. This is an ID data type. If you use “closedBy” in an ISEL expression to compute a textbox, text area, or text editor field, the system will use the user profile's unformatted alphanumeric user ID (e.g. 9fef89d3-28fc-4520-9404-0f3435633c9d). Make sure the computed field is a user or user multiple field if you want the system to use the user profile's name. closedBy__active: whether the user profile is active in Boolean format. This means the data populated by the “closedBy__active” tag will be either “Yes” or “No”. closedBy__email: the user profile's email address. This means the data populated by the “closedBy__email” tag will be an email address (e.g. jsmith@caseiq.com). closedBy__name: the user profile's name in text format. The “closedBy__name” tag will use the user profile's name in an ISEL expression to compute a textbox, text area, or text editor field. However, this tag will not work for user or user multiple fields.
Created By	The user that added the to-do to the Case IQ application by submitting the New To-Do form.	User	The “Created By” field has multiple tags that pull in different data types: createdBy: the user profile's ID. This is an ID data type. If you use “createdBy” in an ISEL expression to compute a textbox, text area, or text editor field, the system will use the user profile's unformatted alphanumeric user ID (e.g. 9fef89d3-28fc-4520-9404-0f3435633c9d). Make sure the computed field is a user or user multiple field if you want the system to use the user profile's name. createdBy__active: whether the user profile is active in Boolean format. This means the data populated by the “createdBy__active” tag will be either “Yes” or “No”. createdBy__email: the user profile's email address. This means the data populated by the “createdBy__email” tag will be an email address (e.g. jsmith@caseiq.com). createdBy__name: the user profile's name in text format. The “createdBy__name” tag will use the user profile's name in an ISEL expression to compute a textbox, text area, or text editor field. However, this tag will not work for user or user multiple fields.
Created Date	The date and time a to-do was created.	Date and Time	createdDate
Date Completed	The date and time a user marked a to-do as complete.	Date and Time	dateCompleted
Date Purged	The date and time a to-do was purged.	Date and Time	datePurged
Date Submitted	The date a to-do was submitted.	Date	dateSubmitted
Deleted By	The user that deleted the to-do in Case IQ.	User	The “Deleted By” field has multiple tags that pull in different data types: deletedBy: the user profile's ID. This is an ID data type. If you use “deletedBy” in an ISEL expression to compute a textbox, text area, or text editor field, the system will use the user profile's unformatted alphanumeric user ID (e.g. 9fef89d3-28fc-4520-9404-0f3435633c9d). Make sure the computed field is a user or user multiple field if you want the system to use the user profile's name. deletedBy__active: whether the user profile is active in Boolean format. This means the data populated by the “deletedBy__active” tag will be either “Yes” or “No”. deletedBy__email: the user profile's email address. This means the data populated by the “deletedBy__email” tag will be an email address (e.g. jsmith@caseiq.com). deletedBy__name: the user profile's name in text format. The “deletedBy__name” tag will use the user profile's name in an ISEL expression to compute a textbox, text area, or text editor field. However, this tag will not work for user or user multiple fields.
Deleted Date	The date and time a to-do was deleted.	Date and Time	deletedDate
Details	The description of the to-do provided by a user.	Text	details
Due Date	The date provided by a user that the to-do task should be completed.	Date	due
Email Reminder	Indicates the number of days before the due date provided by a user that a to-do's responsible user should receive an email reminder from Case IQ to complete the to-do.	Picklist	emailReminder
Do not Purge	Indicates whether a to-do's case has been set to “Do not Purge” or if the case can be deleted in record purges.	Boolean	excludeFromPurge
Exclude From Suggest Links	Indicates if your application will search the to-do record for similar values when suggesting related cases.	Boolean	excludeFromSuggestedLinks
Last Updated By	The user who most recently updated the to-do.	User	The “Last Updated By” field has multiple tags that pull in different data types: lastUpdatedBy: the user profile's ID. This is an ID data type. If you use “lastUpdatedBy” in an ISEL expression to compute a textbox, text area, or text editor field, the system will use the user profile's unformatted alphanumeric user ID (e.g. 9fef89d3-28fc-4520-9404-0f3435633c9d). Make sure the computed field is a user or user multiple field if you want the system to use the user profile's name. lastUpdatedBy__active: whether the user profile is active in Boolean format. This means the data populated by the “lastUpdatedBy__active” tag will be either “Yes” or “No”. lastUpdatedBy__email: the user profile's email address. This means the data populated by the “lastUpdatedBy__email” tag will be an email address (e.g. jsmith@caseiq.com). lastUpdatedBy__name: the user profile's name in text format. The “lastUpdatedBy__name” tag will use the user profile's name in an ISEL expression to compute a textbox, text area, or text editor field. However, this tag will not work for user or user multiple fields.
Last Updated Date	The date and time the to-do was most recently updated.	Date and Time	lastUpdatedDate
#	The number generated to identify the to-do for the case.	ID	number
Pending Purge Date	The date and time a to-do has been scheduled to be purged.	Date and Time	pendingPurgeDate
Purge Reason	The reason provided when a profile was scheduled to be purged.	Picklist	purgeReason
Record Source	The method by which the to-do was added to the system, i.e. web, external, or email.	Picklist	recordSource
Responsible	The user assigned responsibility of the to-do.	User	The “Responsible” field has multiple tags that pull in different data types: responsible: the user profile's ID. This is an ID data type. If you use “responsible” in an ISEL expression to compute a textbox, text area, or text editor field, the system will use the user profile's unformatted alphanumeric user ID (e.g. 9fef89d3-28fc-4520-9404-0f3435633c9d). Make sure the computed field is a user or user multiple field if you want the system to use the user profile's name. responsible__active: whether the user profile is active in Boolean format. This means the data populated by the “responsible__active” tag will be either “Yes” or “No”. responsible__email: the user profile's email address. This means the data populated by the “responsible__email” tag will be an email address (e.g. jsmith@caseiq.com). responsible__name: the user profile's name in text format. The “responsible__name” tag will use the user profile's name in an ISEL expression to compute a textbox, text area, or text editor field. However, this tag will not work for user or user multiple fields.
Status	A flag indicating the status value or stage in the task process of the to-do.	Flag	status
Source Job	The name of the integration log that created the to-do.	Text	sourceJob
System Processing	Indicates if the to-do record is currently being used in a process.	Boolean	sysProcessing
To-Do Type	The kind of task the to-do involves provided by a user.	Picklist	todoType

Appointment Fields

Static Field	Field Data	Data Type	Field Name Tag
All Day	Indicates if the event will last the entire day, as provided by a user.	Boolean	allDayEvent
Cancelled By	The user who cancelled the appointment.	User	The “Cancelled By” field has multiple tags that pull in different data types: cancelledBy: the user profile's ID. This is an ID data type. If you use “cancelledBy” in an ISEL expression to compute a textbox, text area, or text editor field, the system will use the user profile's unformatted alphanumeric user ID (e.g. 9fef89d3-28fc-4520-9404-0f3435633c9d). Make sure the computed field is a user or user multiple field if you want the system to use the user profile's name. cancelledBy__active: whether the user profile is active in Boolean format. This means the data populated by the “cancelledBy__active” tag will be either “Yes” or “No”. cancelledBy__email: the user profile's email address. This means the data populated by the “cancelledBy__email” tag will be an email address (e.g. jsmith@caseiq.com). cancelledBy__name: the user profile's name in text format. The “cancelledBy__name” tag will use the user profile's name in an ISEL expression to compute a textbox, text area, or text editor field. However, this tag will not work for user or user multiple fields.
Cancelled Date	The date and time an appointment was cancelled.	Date and Time	cancelledDate
Item Number	The full identification number of the appointment, which includes the appointment's case number followed by its own number, e.g. "2024-005 / 2"	ID	childNumber
Created By	The user that added the appointment to the Case IQ application by submitting the New Appointment form.	User	The “Created By” field has multiple tags that pull in different data types: createdBy: the user profile's ID. This is an ID data type. If you use “createdBy” in an ISEL expression to compute a textbox, text area, or text editor field, the system will use the user profile's unformatted alphanumeric user ID (e.g. 9fef89d3-28fc-4520-9404-0f3435633c9d). Make sure the computed field is a user or user multiple field if you want the system to use the user profile's name. createdBy__active: whether the user profile is active in Boolean format. This means the data populated by the “createdBy__active” tag will be either “Yes” or “No”. createdBy__email: the user profile's email address. This means the data populated by the “createdBy__email” tag will be an email address (e.g. jsmith@caseiq.com). createdBy__name: the user profile's name in text format. The “createdBy__name” tag will use the user profile's name in an ISEL expression to compute a textbox, text area, or text editor field. However, this tag will not work for user or user multiple fields.
Created Date	The date and time an appointment was created.	Date and Time	createdDate
Date Purged	The date and time a to-do was purged.	Date and Time	datePurged
Date Sent	The date and time the last update of the appointment was sent to recipients.	Date and Time	dateSent
Date Submitted	The date a to-do was submitted.	Date	dateSubmitted
Deleted By	The user that deleted the appointment in Case IQ.	User	The “Deleted By” field has multiple tags that pull in different data types: deletedBy: the user profile's ID. This is an ID data type. If you use “deletedBy” in an ISEL expression to compute a textbox, text area, or text editor field, the system will use the user profile's unformatted alphanumeric user ID (e.g. 9fef89d3-28fc-4520-9404-0f3435633c9d). Make sure the computed field is a user or user multiple field if you want the system to use the user profile's name. deletedBy__active: whether the user profile is active in Boolean format. This means the data populated by the “deletedBy__active” tag will be either “Yes” or “No”. deletedBy__email: the user profile's email address. This means the data populated by the “deletedBy__email” tag will be an email address (e.g. jsmith@caseiq.com). deletedBy__name: the user profile's name in text format. The “deletedBy__name” tag will use the user profile's name in an ISEL expression to compute a textbox, text area, or text editor field. However, this tag will not work for user or user multiple fields.
Deleted Date	The date and time an appointment was deleted.	Date and Time	deletedDate
Description	The description of the appointment provided by a user.	Text	description
Do not Purge	Indicates whether an appointment's case has been set to “Do not Purge” or if the case can be deleted in record purges.	Boolean	excludeFromPurge
Duration	The length of time between the appointment's “Start Date” and “End Date”.	Time	duration
End Date	The date and time the appointment will end provided by a user.	Date and Time	endDate
Exclude From Suggested Links	Indicates if your application will search the appointment record for similar values when suggesting related cases.	Boolean	excludeFromSuggestedLinks
Failed Invitees	The invitees to which the system was not able to deliver the appointment email.	Email	failedInvitees
Invitees	The email address(es) provided by a user to which the system sent the appointment email.	Email Multiple	invitees invitees__name
Last Updated By	The user who most recently updated the appointment.	User	The “Last Updated By” field has multiple tags that pull in different data types: lastUpdatedBy: the user profile's ID. This is an ID data type. If you use “lastUpdatedBy” in an ISEL expression to compute a textbox, text area, or text editor field, the system will use the user profile's unformatted alphanumeric user ID (e.g. 9fef89d3-28fc-4520-9404-0f3435633c9d). Make sure the computed field is a user or user multiple field if you want the system to use the user profile's name. lastUpdatedBy__active: whether the user profile is active in Boolean format. This means the data populated by the “lastUpdatedBy__active” tag will be either “Yes” or “No”. lastUpdatedBy__email: the user profile's email address. This means the data populated by the “lastUpdatedBy__email” tag will be an email address (e.g. jsmith@caseiq.com). lastUpdatedBy__name: the user profile's name in text format. The “lastUpdatedBy__name” tag will use the user profile's name in an ISEL expression to compute a textbox, text area, or text editor field. However, this tag will not work for user or user multiple fields.
Last Updated Date	The date and time the appointment was most recently updated.	Date and Time	lastUpdatedDate
Location	The location of the appointment provided by a user.	Text	location
#	The number generated to identify the appointment for the case.	ID	number
Organizer	The user that organized the appointment.	User	The “Organizer” field has multiple tags that pull in different data types: organizer: the user profile's ID. This is an ID data type. If you use “organizer” in an ISEL expression to compute a textbox, text area, or text editor field, the system will use the user profile's unformatted alphanumeric user ID (e.g. 9fef89d3-28fc-4520-9404-0f3435633c9d). Make sure the computed field is a user or user multiple field if you want the system to use the user profile's name. organizer__active: whether the user profile is active in Boolean format. This means the data populated by the “organizer__active” tag will be either “Yes” or “No”. organizer__email: the user profile's email address. This means the data populated by the “organizer__email” tag will be an email address (e.g. jsmith@caseiq.com). organizer__name: the user profile's name in text format. The “organizer__name” tag will use the user profile's name in an ISEL expression to compute a textbox, text area, or text editor field. However, this tag will not work for user or user multiple fields.
Pending Purge Date	The date and time the appointment has been scheduled to be purged.	Date and Time	pendingPurgeDate
Purge Reason	The reason provided when an appointment was scheduled to be purged.	Picklist	purgeReason
Record Source	The method by which the appointment was added to the system, i.e. web, external, or email.	Picklist	recordSource
Source Job	The name of the integration log that created the appointment.	Text	sourceJob
Start Date	The date and time the appointment will begin provided by a user.	Date and Time	startDate
Status	A flag indicating if the latest version of the appointment invitation has been sent to the invitees or if the appointment has been cancelled.	Status	status
Subject	The text provided by a user that the system will use in the appointment email invitation's subject line.	Text	subject
System Processing	Indicates if the appointment record is currently being used in a process.	Boolean	sysProcessing

Note Fields

Static Field	Field Data	Data Type	Field Name Tag
Item Number	The full identification number of the note, which includes the note's case number followed by its own number, e.g. "2024-005 / 2"	ID	childNumber
Created By	The user that added the note to the Case IQ application by submitting the New Note form.	User	The “Created By” field has multiple tags that pull in different data types: createdBy: the user profile's ID. This is an ID data type. If you use “createdBy” in an ISEL expression to compute a textbox, text area, or text editor field, the system will use the user profile's unformatted alphanumeric user ID (e.g. 9fef89d3-28fc-4520-9404-0f3435633c9d). Make sure the computed field is a user or user multiple field if you want the system to use the user profile's name. createdBy__active: whether the user profile is active in Boolean format. This means the data populated by the “createdBy__active” tag will be either “Yes” or “No”. createdBy__email: the user profile's email address. This means the data populated by the “createdBy__email” tag will be an email address (e.g. jsmith@caseiq.com). createdBy__name: the user profile's name in text format. The “createdBy__name” tag will use the user profile's name in an ISEL expression to compute a textbox, text area, or text editor field. However, this tag will not work for user or user multiple fields.
Created Date	The date and time a note was created.	Date and Time	createdDate
Date Purged	The date and time a note was purged.	Date and Time	datePurged
Date Submitted	The date a note was submitted.	Date	dateSubmitted
Deleted By	The user that deleted the note in Case IQ.	User	The “Deleted By” field has multiple tags that pull in different data types: deletedBy: the user profile's ID. This is an ID data type. If you use “deletedBy” in an ISEL expression to compute a textbox, text area, or text editor field, the system will use the user profile's unformatted alphanumeric user ID (e.g. 9fef89d3-28fc-4520-9404-0f3435633c9d). Make sure the computed field is a user or user multiple field if you want the system to use the user profile's name. deletedBy__active: whether the user profile is active in Boolean format. This means the data populated by the “deletedBy__active” tag will be either “Yes” or “No”. deletedBy__email: the user profile's email address. This means the data populated by the “deletedBy__email” tag will be an email address (e.g. jsmith@caseiq.com). deletedBy__name: the user profile's name in text format. The “deletedBy__name” tag will use the user profile's name in an ISEL expression to compute a textbox, text area, or text editor field. However, this tag will not work for user or user multiple fields.
Deleted Date	The date and time a note was deleted.	Date and Time	deletedDate
Details	The details of a note provided by a user.	Text	details
Do not Purge	Indicates whether a note's case has been set to “Do not Purge” or if the case can be deleted in record purges.	Boolean	excludeFromPurge
Exclude From Suggested Links	Indicates if your application will search the note record for similar values when suggesting related cases.	Boolean	excludeFromSuggestedLinks
Last Updated By	The user who most recently updated the note.	User	The “Last Updated By” field has multiple tags that pull in different data types: lastUpdatedBy: the user profile's ID. This is an ID data type. If you use “lastUpdatedBy” in an ISEL expression to compute a textbox, text area, or text editor field, the system will use the user profile's unformatted alphanumeric user ID (e.g. 9fef89d3-28fc-4520-9404-0f3435633c9d). Make sure the computed field is a user or user multiple field if you want the system to use the user profile's name. lastUpdatedBy__active: whether the user profile is active in Boolean format. This means the data populated by the “lastUpdatedBy__active” tag will be either “Yes” or “No”. lastUpdatedBy__email: the user profile's email address. This means the data populated by the “lastUpdatedBy__email” tag will be an email address (e.g. jsmith@caseiq.com). lastUpdatedBy__name: the user profile's name in text format. The “lastUpdatedBy__name” tag will use the user profile's name in an ISEL expression to compute a textbox, text area, or text editor field. However, this tag will not work for user or user multiple fields.
Last Updated Date	The date and time the note was most recently updated.	Date and Time	lastUpdatedDate
Note Type	The kind of information a note stores as set by a user.	Picklist	noteType
#	The number generated to identify the note for the case.	ID	number
Pending Purge Date	The date and time the note has been scheduled to be purged.	Date and Time	pendingPurgeDate
Purge Reason	The reason provided when a note was scheduled to be purged.	Picklist	purgeReason
Record Source	The method by which the note was added to the system, i.e. web, external, or email.	Picklist	recordSource
Source Job	The name of the integration log that created the note.	Text	sourceJob
System Processing	Indicates if the note record is currently being used in a process.	Boolean	sysProcessing

File Fields

Static Field	Field Data	Data Type	Field Name Tag
Include Files attached to Case	Indicates if the user who created the packet chose to include the case's other file records in the packet.	Radio	caseFilesInclusionKind
Item Number	The full identification number of the file, which includes the file's case number followed by its own number, e.g. "2024-005 / 2"	ID	childNumber
Content Searchable	Indicates if Case IQ can search for text in attached file.	Boolean	contentSearchable
Created By	The user that added the file to the Case IQ application by submitting the New File form.	User	The “Created By” field has multiple tags that pull in different data types: createdBy: the user profile's ID. This is an ID data type. If you use “createdBy” in an ISEL expression to compute a textbox, text area, or text editor field, the system will use the user profile's unformatted alphanumeric user ID (e.g. 9fef89d3-28fc-4520-9404-0f3435633c9d). Make sure the computed field is a user or user multiple field if you want the system to use the user profile's name. createdBy__active: whether the user profile is active in Boolean format. This means the data populated by the “createdBy__active” tag will be either “Yes” or “No”. createdBy__email: the user profile's email address. This means the data populated by the “createdBy__email” tag will be an email address (e.g. jsmith@caseiq.com). createdBy__name: the user profile's name in text format. The “createdBy__name” tag will use the user profile's name in an ISEL expression to compute a textbox, text area, or text editor field. However, this tag will not work for user or user multiple fields.
Created Date	The date and time a file was created.	Date and Time	createdDate
Date Purged	The date and time a file was purged.	Date and Time	datePurged
Date Submitted	The date a file was submitted.	Date	dateSubmitted
Deleted By	The user that deleted the file in Case IQ.	User	The “Deleted By” field has multiple tags that pull in different data types: deletedBy: the user profile's ID. This is an ID data type. If you use “deletedBy” in an ISEL expression to compute a textbox, text area, or text editor field, the system will use the user profile's unformatted alphanumeric user ID (e.g. 9fef89d3-28fc-4520-9404-0f3435633c9d). Make sure the computed field is a user or user multiple field if you want the system to use the user profile's name. deletedBy__active: whether the user profile is active in Boolean format. This means the data populated by the “deletedBy__active” tag will be either “Yes” or “No”. deletedBy__email: the user profile's email address. This means the data populated by the “deletedBy__email” tag will be an email address (e.g. jsmith@caseiq.com). deletedBy__name: the user profile's name in text format. The “deletedBy__name” tag will use the user profile's name in an ISEL expression to compute a textbox, text area, or text editor field. However, this tag will not work for user or user multiple fields.
Deleted Date	The date and time a file was deleted.	Date and Time	deletedDate
Description	The description of the attached file provided by a user.	Text	descriptions
Document generation method	The method the system used to merge case data in the packet template chosen by the user.	Picklist	documentGenerationMethod
Do not Purge	Indicates whether a file's case has been set to “Do not Purge” or if the case can be deleted in record purges.	Boolean	excludeFromPurge
Exclude From Suggested Links	Indicates if your application will search the file record for similar values when suggesting related cases.	Boolean	excludeFromSuggestedLinks
File Shared	Indicates if a user has shared the file.	Boolean	fileShared
Attachments	The name of the attached file to the record.	Text	files
File Type	The format of the file generated from a template or packet chosen by the user who created the file.	Picklist	generatedFileType
Is there an Active Shared Link against this File record?	Indicates if a file's shared link is activate, meaning that recipients can currently view and download a file using the shared link.	Boolean	hasActiveShare
Kind	The type of file record.	Picklist	kind
Last Updated By	The user who most recently updated the file.	User	The “Last Updated By” field has multiple tags that pull in different data types: lastUpdatedBy: the user profile's ID. This is an ID data type. If you use “lastUpdatedBy” in an ISEL expression to compute a textbox, text area, or text editor field, the system will use the user profile's unformatted alphanumeric user ID (e.g. 9fef89d3-28fc-4520-9404-0f3435633c9d). Make sure the computed field is a user or user multiple field if you want the system to use the user profile's name. lastUpdatedBy__active: whether the user profile is active in Boolean format. This means the data populated by the “lastUpdatedBy__active” tag will be either “Yes” or “No”. lastUpdatedBy__email: the user profile's email address. This means the data populated by the “lastUpdatedBy__email” tag will be an email address (e.g. jsmith@caseiq.com). lastUpdatedBy__name: the user profile's name in text format. The “lastUpdatedBy__name” tag will use the user profile's name in an ISEL expression to compute a textbox, text area, or text editor field. However, this tag will not work for user or user multiple fields.
Last Updated Date	The date and time the file was most recently updated.	Date and Time	lastUpdatedDate
#	The number generated to identify the file for the case.	ID	number
Pending Purge Date	The date and time the file has been scheduled to be purged.	Date and Time	pendingPurgeDate
Purge Reason	The reason provided when a file was scheduled to be purged.	Picklist	purgeReason
Record Source	The method by which the file was added to the system, i.e. web, external, or email.	Picklist	recordSource
Apply page numbering	Indicates if the user who created the packet has chosen to include page numbers.	Boolean	shouldAddPageNumbers
Generate a Table of Contents (ToC)	Indicates if the user who created the packet has chosen to include a Table of Contents.	Boolean	shouldAddTableOfContents
Source Job	The name of the integration log that created the file.	Text	sourceJob
System Processing	Indicates if the file record is currently being used in a process.	Boolean	sysProcessing
Template Name	The template file chosen to generate the file record's document.	Picklist	templateId
Locale	The language used in the template file.	Picklist	templateLocale
URL	The file link text entered by a user.	Text	url

Email Fields

Static Field	Field Data	Data Type	Field Name Tag
Attachments	The name of the attached file to the email.	Text	attachments
Bcc	The email address(es) provided by a user to which the system sent the email via BCC.	Email Multiple	bccRecipients bccRecipients__name
Body	The main text of the email provided by a user.	Text	body
Cc	The email address(es) provided by a user to which the system sent the email via CC.	Email Multiple	ccRecipients ccRecipients__name
Count	The number of emails in a conversation thread.	Integer	threadCount
Created By	The user that sent the email from the Case IQ application by submitting the New Email form.	User	The “Created By” field has multiple tags that pull in different data types: createdBy: the user profile's ID. This is an ID data type. If you use “createdBy” in an ISEL expression to compute a textbox, text area, or text editor field, the system will use the user profile's unformatted alphanumeric user ID (e.g. 9fef89d3-28fc-4520-9404-0f3435633c9d). Make sure the computed field is a user or user multiple field if you want the system to use the user profile's name. createdBy__active: whether the user profile is active in Boolean format. This means the data populated by the “createdBy__active” tag will be either “Yes” or “No”. createdBy__email: the user profile's email address. This means the data populated by the “createdBy__email” tag will be an email address (e.g. jsmith@caseiq.com). createdBy__name: the user profile's name in text format. The “createdBy__name” tag will use the user profile's name in an ISEL expression to compute a textbox, text area, or text editor field. However, this tag will not work for user or user multiple fields.
Created Date	The date and time an email was sent.	Date and Time	createdDate
Date Purged	The date and time an email was purged.	Date and Time	datePurged
Date Submitted	The date an email was submitted.	Date	dateSubmitted
Deleted By	The user that deleted the email in Case IQ.	User	The “Deleted By” field has multiple tags that pull in different data types: deletedBy: the user profile's ID. This is an ID data type. If you use “deletedBy” in an ISEL expression to compute a textbox, text area, or text editor field, the system will use the user profile's unformatted alphanumeric user ID (e.g. 9fef89d3-28fc-4520-9404-0f3435633c9d). Make sure the computed field is a user or user multiple field if you want the system to use the user profile's name. deletedBy__active: whether the user profile is active in Boolean format. This means the data populated by the “deletedBy__active” tag will be either “Yes” or “No”. deletedBy__email: the user profile's email address. This means the data populated by the “deletedBy__email” tag will be an email address (e.g. jsmith@caseiq.com). deletedBy__name: the user profile's name in text format. The “deletedBy__name” tag will use the user profile's name in an ISEL expression to compute a textbox, text area, or text editor field. However, this tag will not work for user or user multiple fields.
Deleted Date	The date and time an email was deleted.	Date and Time	deletedDate
Direction	Indicates if the system sent the email or received the email.	Picklist	direction
Email Sources	Indicates if the email was sent to share a file from Case IQ.	Picklist	emailSources
Do not Purge	Indicates whether an email's case has been set to “Do not Purge” or if the case can be deleted in record purges.	Boolean	excludeFromPurge
Exclude From Suggested Links	Indicates if your application will search the email record for similar values when suggesting related cases.	Boolean	excludeFromSuggestedLinks
Failed Recipients	The recipients to which the system was not able to deliver the appointment email.	Email	failedRecipients
High Priority	Indicates if the email was sent as high priority.	Boolean	highPriority
Last Updated By	The user who sent the email.	User	The “Last Updated By” field has multiple tags that pull in different data types: lastUpdatedBy: the user profile's ID. This is an ID data type. If you use “lastUpdatedBy” in an ISEL expression to compute a textbox, text area, or text editor field, the system will use the user profile's unformatted alphanumeric user ID (e.g. 9fef89d3-28fc-4520-9404-0f3435633c9d). Make sure the computed field is a user or user multiple field if you want the system to use the user profile's name. lastUpdatedBy__active: whether the user profile is active in Boolean format. This means the data populated by the “lastUpdatedBy__active” tag will be either “Yes” or “No”. lastUpdatedBy__email: the user profile's email address. This means the data populated by the “lastUpdatedBy__email” tag will be an email address (e.g. jsmith@caseiq.com). lastUpdatedBy__name: the user profile's name in text format. The “lastUpdatedBy__name” tag will use the user profile's name in an ISEL expression to compute a textbox, text area, or text editor field. However, this tag will not work for user or user multiple fields.
Last Updated Date	The date and time the email was sent.	Date and Time	lastUpdatedDate
Parent Email Sender	The email address of the original email in the conversation thread.	Email	parentEmailSender
Pending Purge Date	The date and time the email has been scheduled to be purged.	Date and Time	pendingPurgeDate
Purge Reason	The reason provided when an email was scheduled to be purged.	Picklist	purgeReason
Recipients	The email address(es) provided by a user to which the system sent the email.	Email Multiple	recipients
Record Source	The method by which the email was added to the system, i.e. web, external, or email.	Picklist	recordSource
Sender	The name of the individual who sent the email.	Text	senderName
Sender Email	The email address of the individual who sent the email.	Email	senderEmail
Source Job	The name of the integration log that created the email.	Text	sourceJob
Subject Line	The text provided by a user that the system will use in the email's subject line.	Text	subject
System Processing	Indicates if the email record is currently being used in a process.	Boolean	sysProcessing

Party Fields

Static Field	Field Data	Data Type	Field Name Tag
Address	The address of the party provided by a user.	Text	address
Item Number	The full identification number of the party, which includes the party's case number followed by its own number, e.g. "2024-005 / 2"	ID	childNumber
City	The city of the party provided by a user.	Text	city
Country	The country of the party provided by a user.	Picklist	country
Created By	The user that added the party to the Case IQ application by submitting the New Party form.	User	The “Created By” field has multiple tags that pull in different data types: createdBy: the user profile's ID. This is an ID data type. If you use “createdBy” in an ISEL expression to compute a textbox, text area, or text editor field, the system will use the user profile's unformatted alphanumeric user ID (e.g. 9fef89d3-28fc-4520-9404-0f3435633c9d). Make sure the computed field is a user or user multiple field if you want the system to use the user profile's name. createdBy__active: whether the user profile is active in Boolean format. This means the data populated by the “createdBy__active” tag will be either “Yes” or “No”. createdBy__email: the user profile's email address. This means the data populated by the “createdBy__email” tag will be an email address (e.g. jsmith@caseiq.com). createdBy__name: the user profile's name in text format. The “createdBy__name” tag will use the user profile's name in an ISEL expression to compute a textbox, text area, or text editor field. However, this tag will not work for user or user multiple fields.
Created Date	The date and time a party was created.	Date and Time	createdDate
Date of Birth	The date of birth of the party provided by a user.	Date	dateOfBirth
Date Purged	The date and time a party was purged.	Date and Time	datePurged
Date Submitted	The date a party was submitted.	Date	dateSubmitted
Deleted By	The user that deleted the party in Case IQ.	User	The “Deleted By” field has multiple tags that pull in different data types: deletedBy: the user profile's ID. This is an ID data type. If you use “deletedBy” in an ISEL expression to compute a textbox, text area, or text editor field, the system will use the user profile's unformatted alphanumeric user ID (e.g. 9fef89d3-28fc-4520-9404-0f3435633c9d). Make sure the computed field is a user or user multiple field if you want the system to use the user profile's name. deletedBy__active: whether the user profile is active in Boolean format. This means the data populated by the “deletedBy__active” tag will be either “Yes” or “No”. deletedBy__email: the user profile's email address. This means the data populated by the “deletedBy__email” tag will be an email address (e.g. jsmith@caseiq.com). deletedBy__name: the user profile's name in text format. The “deletedBy__name” tag will use the user profile's name in an ISEL expression to compute a textbox, text area, or text editor field. However, this tag will not work for user or user multiple fields.
Deleted Date	The date and time a party was deleted.	Date and Time	deletedDate
Email address	The email address of the party provided by a user.	Email	emailAddress
Do not Purge	Indicates whether a party's case has been set to “Do not Purge” or if the case can be deleted in record purges.	Boolean	excludeFromPurge
Exclude From Suggested Links	Indicates if your application will search the partyrecord for similar values when suggesting related cases.	Boolean	excludeFromSuggestedLinks
			externalRecord
First Name	The first name of the party provided by a user.	Text	firstName
Home Phone #	The home phone number of the party provided by a user.	Phone Number	homePhone
Last Name	The last name of the party provided by a user.	Text	lastName
Last Updated By	The user who most recently updated the party.	User	The “Last Updated By” field has multiple tags that pull in different data types: lastUpdatedBy: the user profile's ID. This is an ID data type. If you use “lastUpdatedBy” in an ISEL expression to compute a textbox, text area, or text editor field, the system will use the user profile's unformatted alphanumeric user ID (e.g. 9fef89d3-28fc-4520-9404-0f3435633c9d). Make sure the computed field is a user or user multiple field if you want the system to use the user profile's name. lastUpdatedBy__active: whether the user profile is active in Boolean format. This means the data populated by the “lastUpdatedBy__active” tag will be either “Yes” or “No”. lastUpdatedBy__email: the user profile's email address. This means the data populated by the “lastUpdatedBy__email” tag will be an email address (e.g. jsmith@caseiq.com). lastUpdatedBy__name: the user profile's name in text format. The “lastUpdatedBy__name” tag will use the user profile's name in an ISEL expression to compute a textbox, text area, or text editor field. However, this tag will not work for user or user multiple fields.
Last Updated Date	The date and time the party was most recently updated.	Date and Time	lastUpdatedDate
Middle Initial	The middle initial of the party provided by a user.	Text	middleInitial
#	The number generated to identify the party for the case.	ID	number
Party Name	The first and last name of the party. The system automatically concatenates the text in the party's “First Name” and “Last Name” fields.	Text	partyName
Party Type	The kind of party chosen by a user.	Picklist	partyType
Pending Purge Date	The date and time the party has been scheduled to be purged.	Date and Time	pendingPurgeDate
Primary	Indicates if the party is the primary one for the case.	Boolean	primaryEntity
Purge Reason	The reason provided when a party was scheduled to be purged.	Picklist	purgeReason
Record Source	The method by which the party was added to the system, i.e. web, external, or email.	Picklist	recordSource
Source Job	The name of the integration log that created the party.	Text	sourceJob
State/Province	The state or province of the party provided by a user.	Picklist	stateProvince
System Processing	Indicates if the party record is currently being used in a process.	Boolean	sysProcessing
Work Phone #	The work phone number of the party provided by a user.	Phone Number	workPhone
Zip Code/Postal Code	The zip or postal code of the party provided by a user.	Postal Code	zipCodePostalCode

Contact Us

Case IQ Knowledge Base