Task
data type to perform PMQL search queries from any of the pages accessible from the Tasks top menu option. Selecting any PMQL search result displays the Task summary for that result.completed
: Datetime Task Completedcompleted
property represents when the Task completes. The completed
property applies to Form Task, Manual Task, and/or Script Task elements from the Request that created the sought Task(s).YYYY-MM-DD HH:MM:SS
using 24-hour time. Example: "2020-07-01 14:25:15"
.NOW
KeywordNOW
keyword to dynamically compare the current datetime with a specified number of chronological units. Use the Less Than operator (<
) followed by the number of chronological units to search for Requests of that age. Note that the interval unit of time is singular. PMQL supports the following units of time:task
property. The task
property value ("Student Registration"
) is not case-sensitive.request
property. The request
property value ("Student Enrollment Process"
) is not case-sensitive.NOW
keyword to represent the current datetime, and then uses the Less Than operator (<
) to determine the datetime four (4) days ago for completed Tasks that completed later than when they were due three (3) days ago. Note that the unit of chronological measurements (day
) is singular.LIKE
operator to find text in a specified JSON array within Request data. For example, PMQL finds the string JavaScript
in the key name CodingLanguages
regardless of what string precedes or follows the sought pattern because the %
wildcard before and after the sought pattern disregards all content in the JSON array preceding and following that pattern, respectively.data
object that represents Request data. The following Request variables store Request data that this PMQL search query references:CodingLanguages
Request variable stores one or more selections from a Select List control of programming languages in which the employment candidate has experience. The Request data stores the Select List control selection(s) in a JSON array that contains both the value and content for each option in the Select List control.JobTitle
Request variable stores the job title for each position the employment candidate held. A Loop control called Jobs
contains a set of controls to enter information about each position the candidate held, among them being a Line Input control called JobTitle
.created
: Task's Creation Datetimecreated
property represents when the Request creates the Task. The created
property applies to Form Task, Manual Task, and/or Script Task elements from the Request that created the sought Task(s).YYYY-MM-DD HH:MM:SS
using 24-hour time. Example: "2020-07-01 14:25:15"
.NOW
KeywordNOW
keyword to dynamically compare the current datetime with a specified number of chronological units. Use the Less Than operator (<
) followed by the number of chronological units to search for Requests of that age. Note that the interval unit of time is singular. PMQL supports the following units of time:task
property. The task
property value ("Package Purchased Items"
) is not case-sensitive.request
property. The request
property value ("Fulfill Purchase Delivery Process"
) is not case-sensitive.NOW
keyword to represent the current datetime, and then uses the Less Than operator (<
) to determine the datetime two (2) hours ago and 30 minutes ago that the applicable Task(s) was created and started, respectively. Note that the unit of chronological measurements (hour
and minute
) are singular.node_6
in Requests associated with Process ID 12 from two hours ago that have completed less than 30 minutes ago.element_id
property to reference the Node Identifier setting value (node_6
) from the Process model for the sought Task's element.process_id
property to reference the Process ID number (12
) associated with the sought Task(s).completed
property. The completed
property value compares the datetime that the Task completed.data
object: Search Request Data for Specific Request Informationdata
JSON object to search for Request data associated with the sought Task(s). The data
JSON object represents Request data: each Request's JSON data model contains the accumulation of all JSON objects and arrays for that Request. The data
JSON object also contains the record data for a Collection. The key names for each JSON object or array derive from the Variable Name setting values in the Screens used for Tasks in each Request or any data injected into that Request's JSON data model by Scripts run via Script Task elements or calls to the RESTful Application Program Interface (API).data
JSON object in PQML search queries helps answer the question "Which Request(s) have specific information in them for Tasks that I seek?" Use operators to compare the value for a particular Screen control to find Requests that only contain the value(s) you seek. For example:data.last_name = "Canera"
. Note that your user account or group membership must have the Requests: Edit Request Data permission. Ask your Administrator if you do not see the Data tab in completed Requests.data
JSON object precedes the Variable Name setting value, as noted above. Use JSON dot notation to reference sub-properties in the referenced Screen control if necessary. Major
stores the JSON object value for the option that each student selects as a major.TotalCredits
stores as an integer the sum of all credits that the student selected for enrollment.status
property. The status
property values (such as "in progress"
) are not case-sensitive.task
property. The task
property value ("Approve Semester Courses"
) is not case-sensitive.request
property. The request
property value ("Student Enrollment Process"
) is not case-sensitive.LeaveType
; the option that indicates the reason is for medical leave has an option value of Medical
. Therefore, to find those completed Tasks in which the reason for leave is illness, use the following in the PMQL search query: data.LeaveType = "Medical"
. The PMQL search query is case sensitive.completed
property. Each use of the completed
property compares the datetime that the Task completed.YYYY-MM-DD HH:MM:SS
as dates and can be used in comparative queries if that string is in quotation marks ("2020-03-15 00:00:00"
).due
: Datetime Task Is or Was Duedue
property represents when the Task is or was due. The due
property applies to Form Task, Manual Task, and/or Script Task elements from the Request that created the sought Task(s).YYYY-MM-DD HH:MM:SS
using 24-hour time. Example: "2020-07-01 14:25:15"
.NOW
KeywordNOW
keyword to dynamically compare the current datetime with a specified number of chronological units. Use the Less Than operator (<
) followed by the number of chronological units to search for Requests of that age. Note that the interval unit of time is singular. PMQL supports the following units of time:request
property. The request
property value ("Loan Approval Process"
) is not case-sensitive.NOW
keyword to represent the current datetime, and then uses the Greater Than operator (>
) to determine the datetime two (2) days from now for due Tasks. Note that the unit of chronological measurements (day
) is singular.completed
property. The completed
property compares the datetime that the Task completed. Since the PMQL search query finds completed Tasks past due, the due
property uses the Greater Than operator (>
) to find Tasks that were due later than 20 minutes ago. process_id
property with a value of 25
to find Requests associated with that Process.element_id
: Task Node Identifier from the Process Modelelement_id
property is the Node Identifier setting value from the Process model for the sought Task's element. The element_id
property applies to Form Task, Manual Task, and/or Script Task elements from the Process model that started the sought Task(s)."node_15"
.node_4
in Requests associated with Process ID 10.status
property. The status
property values (such as "in progress"
) are not case-sensitive.process_id
property with a value of 10
to find Requests associated with that Process.node_4
in Requests associated with Process ID 10 that started two days ago.NOW
keyword to represent the current datetime, and then uses the Less Than operator (<
) to determine the datetime two (2) days ago that the applicable Task(s) started. Note that the unit of chronological measurement (day
) is singular.id
: Task ID Numberid
property represents the Task ID number for the sought Task(s). The id
property applies to Form Task, Manual Task, and/or Script Task elements from the Request that started the sought Task(s).id
property for the Request
data type or for the id
property for the Collection
data type.modified
: Datetime Task Last Modifiedmodified
property represents when the Task was last modified. A Task modifies when the JSON object model to which that Task applies is changed from a Script, a user action, an application program interface (API) call, or any other means. The modified
property applies to Form Task, Manual Task, and/or Script Task elements from the Request that created the sought Task(s).YYYY-MM-DD HH:MM:SS
using 24-hour time. Example: "2020-07-01 14:25:15"
.NOW
KeywordNOW
keyword to dynamically compare the current datetime with a specified number of chronological units. Use the Less Than operator (<
) followed by the number of chronological units to search for Requests of that age. Note that the interval unit of time is singular. PMQL supports the following units of time:task
property. The task
property value ("Loan Information"
) is not case-sensitive.request
property. The request
property value ("Loan Application Process"
) is not case-sensitive.NOW
keyword to represent the current datetime, and then uses the Less Than operator (<
) to determine the datetime 20 minutes ago that the applicable Task(s) were modified. Note that the unit of chronological measurement (minute
) is singular.process_id
property to reference the Process ID number (25
) associated with the sought Task(s).LIKE
operator with the %
wildcard to search for any Task name that includes the characters approval
in its name.process_id
: Process ID Number Associated with the Taskprocess_ID
property represents the Process ID number associated with the sought Task(s). The process_ID
property applies to Form Task, Manual Task, and/or Script Task elements from the Process model associated with the Process ID that started the sought Task(s).modeler/
. This number is the Process ID to use with the process_id
property.!=
) to find all Tasks except those associated with Process ID 5.request
: Request Name Associated with the Taskrequest
represents the Request's name associated with the sought Task(s). The request
property applies to Form Task, Manual Task, and/or Script Task elements from the Process model that started the sought Task(s).request
property value in quotation marks. Example: "Request Name"
. The property value is not case-sensitive.OR
operator to search for any of multiple properties within an AND
operator to find Tasks for either the "Residential Loan Approval Process" or "Business Loan Approval Process" Requests.status
property. The status
property values (such as "completed"
) are not case-sensitive.NOW
keyword to represent the current datetime, and then uses the Less Than operator (<
) to determine the datetime one hour ago that the applicable Task(s) started. Note that the unit of chronological measurement (hour
) is singular, even if the sought Task(s) is more than one hour old.data
object that represents Request data. The following Request variables store Request data that this PMQL search query references:TotalPurchase
Request variable stores the total purchase request amount, including applicable taxes.Customer
Request variable stores the business name for which the purchase order fulfillment applies.started
: Datetime Task Startedstarted
property represents when the Task starts. The started
property applies to Form Task, Manual Task, and/or Script Task elements from the Request that started the sought Task(s).started
property is similar to the created
property, in that when a Task starts, it is created. The created
property applies to when our API creates a Task, while the started
property pertains to when a user uses the user interface to start a Task.YYYY-MM-DD HH:MM:SS
using 24-hour time. Example: "2020-07-01 14:25:15"
.NOW
KeywordNOW
keyword to dynamically compare the current datetime with a specified number of chronological units. Use the Less Than operator (<
) followed by the number of chronological units to search for Requests of that age. Note that the interval unit of time is singular. PMQL supports the following units of time:task
property. The task
property value ("Submit Purchase Request"
) is not case-sensitive.status
property. The status
property values (such as "in progress"
) are not case-sensitive.request
property. The request
property value ("Purchase Request Process"
) is not case-sensitive.NOW
keyword to represent the current datetime, and then uses the Less Than operator (<
) to determine the datetime three (3) days ago that the applicable Task(s) started. Note that the unit of chronological measurement (day
) is singular.data
object that represents Request data. The following Request variables store Request data that this PMQL search query references:Approve
Request variable stores whether a Checkbox control is selected in the Form Task that approves a submitted purchase request. Since this example requires only approved purchases, this PMQL search query includes only Approve
values of true
that a Checkbox control stores when it is selected upon Task submission. The property value is not case-sensitive.TotalPurchase
Request variable stores the total purchase request amount, including applicable taxes.status
: Task Statusstatus
property represents the Task status. The status
property applies to Form Task, Manual Task, and/or Script Task elements from the Request that started the sought Task(s).status
property value in quotation marks. Example: "in progress"
. The property value is not case-sensitive.request
property. The request
property value ("Travel Request Process"
) is not case-sensitive.NOW
keyword to represent the current datetime, and then uses the Greater Than operator (>
) to determine the datetime three days from now that the requested business travel is to occur as requested in the LeaveDate
Request variable. Note that the unit of chronological measurement (day
) is singular.data
object that represents Request data. The following Request variables store Request data that this PMQL search query references:DestinationMunicipality
Request variable stores to which municipality business travel is requested.DestinationState
Request variable stores to which state business travel is requested.LeaveDate
Request variable stores at which datetime business travel is requested.task
: Task Nametask
property represents the Task name. The task
property applies to Form Task, Manual Task, and/or Script Task elements from the Request that started the sought Task(s).task
property value in quotation marks. Example: "TaskName"
. The property value is not case-sensitive.status
property. The status
property values (such as "in progress"
) are not case-sensitive.LIKE
operator with the %
wildcard to search for any Task name that includes the characters review
in its name.process_id
property with a value of 12
to find Requests associated with that Process.