There are also two files that apparently assemble these variables, but even using one of them as an example of creating a new value could not succeed.
The files are catalogrequestserach.xsl and requestcommontempaltes.xsl, as shown:
searchSortInfo = { "id":"r.request_id",
"name":"r.name",
"status":"r.status",
"createdDate":"r.created_date",
"modifiedDate":"r.modified_date",
"completionDate":"r.completion_date",
"desiredDate":"r.desired_date",
"priority":"r.priority",
"requestForUser":"requestForUserLastName, requestForUserFirstName, r.req_for_user_id",
"requestByUser":"requestByUserLastName, requestByUserFirstName, r.req_by_user_id",
"requestedForAccount.name,requestedForAccount.id":"requestForAccountName, r.req_for_account_id",
"requestedByAccount.name,requestedByAccount.id":"requestByAccountName, r.req_by_account_id",
"form.costCenter":"formCostCenter",
"form.project":"formProject",
"form.glCode":"formGLCode",
"form.authorizationNumber":"formAuthNo",
"form.comments":"formComments",
"domain.id":"r.domain",
"domain.name":"ute.tenant_name"};
- requestcommontempaltes.xsl
,searchSortInfo :{ <xsl:if test="$pageType='catalogrequestsearchpre'">
"id":"r.request_id",
"name":"r.name",
"status":"r.status",
"createdDate":"r.created_date",
"modifiedDate":"r.modified_date",
"completionDate":"r.completion_date",
"desiredDate":"r.desired_date",
"priority":"r.priority",
"requestForUser":"requestForUserLastName, requestForUserFirstName, r.req_for_user_id",
"requestByUser":"requestByUserLastName, requestByUserFirstName, r.req_by_user_id",
"requestedForAccount.name":"requestForAccountName",
"requestedForAccount.id": "r.req_for_account_id",
"requestedByAccount.name":"requestByAccountName",
"requestedByAccount.id":"r.req_by_account_id",
"form.costCenter":"formCostCenter",
"form.project":"formProject",
"form.glCode":"formGLCode",
"form.authorizationNumber":"formAuthNo",
"form.comments":"formComments",
"domain.id":"r.domain",
"domain.name":"ute.tenant_name"
</xsl:if>}
Original Message:
Sent: 08-23-2019 03:28 PM
From: Diego Lima
Subject: Display SDM Ticket Number in Catalog Request List
Hi Guys,
I need to display the ticket number generated in sdm instead of the service catalog request number in the catalog ticket list in USS.
I am studying the structures of these variables to understand how to assemble or call the ticket variable created in SDM to replace in the "req-id" line.
I have identified the file where I should make this change and the variable that is bringing the request ID generated in the Catalog.
The file to change is request-list.widget and the variables that are visible to replacing the {{id}} variable in the value of requests, such as:
- id
- name
- status
- createdDate
- modifiedDate
- completionDate
- desiredDate
- priority
- requestForUser
- requestByUser
- requestedForAccount.name, requestedForAccount.id
- requestedByAccount.name, requestedByAccount.id
- form.costCenter
- form.project
- form.glCode
- form.authorizationNumber
- form.comments
- domain.id
- domain.name
However, I could not understand at this time how I could put together a request ID in Catalog and SDM ticket to create this variable (if it does not exist) and replace it in the ticket list.
I also noticed that the usm_link_ticket_request_item table holds all the relationship I need in case there is a need to create something related to the solution database.
Have any of you ever needed to do something like this?