Example: Updating a Record using the Go to Record Quick Action (GAD)

2 min

This example shows you how to provide input criteria for a Go to Record Quick Action so it redirects to another record for the same business object. The Update a Record Quick Action is then used to update that second record that the Go to Record action redirected to. A real-world use could be that of a customer using the CI business object and an external system which sends data about these CI records to ITSM. Using the Go to Record Quick Action, incoming CI data can be used to update existing records, but if the external system finds some new CI and sends that as part of the data, the Create Record if not Found option automatically creates a record in ITSM for the new item.

This example uses the Graphical Action Designer (GAD). Examples using the Classic Action Designer (CAD) are here: Examples of Using Actions (CAD).

Prerequisite

To use these Quick Actions, set the global constant EnableActionService to True.

This example assumes you have administrator-level access to the Configuration console and are familiar with creating business objects and Quick Actions. If you do not have administrator-level access, see Notes on roles and permissions and Open the Graphical Action Designer

Steps:

Identify two Incidents you can use for this exercise where the Summary field can be usefully changed in the second record. Let's call these Incidents 10928 and 10413. At the end of this example, we will run the action from 10928 and it will change the Summary field of 10413.

Image 1 of example showing 2 selected record to use with Go to Record and Update Record Actions

Find the Record Id from 10413 (for later use) as follows:

a. Log in to the Service Desk console.

b. Go to the Service Request workspace > Incidents list view.

c. Open the Developer tool by pressing F12 and go to Network tab.

d. Double click on the incident 10413.

e. In the Network tab, find GetContentForList item & go to its Payload tab.

f. ParentRecId is the RecId of the selected record. It will look something like this in length, for example, AB1AC111A1CD111B1B1CB1111111AAA.

Image 2 for Go To Record and Update record example showing how to find the RecId of an Incident record using Developer Tools

Go back to the Configuration Console > Build >Business Objects > Incident > Quick Actions > Graphical Action Designer.

Under Record Actions, find the Go to Record action block and then drag it on to the Editor.

In the Common Settings tab for the Go to Record block, enter a name in the Name field, for example, GTR-Action1.

In the Block Settings tab, enter the RecID you previously saved for record 10413.

Image 3 of Go to Record and Update Record example showing RecId from first incident being entered into Block Settings for Go to Record block

Under Record Actions, find the Update a Record action block and then drag it on to the Editor.

Link it to the Go to Record block so that it is second in line to be run in the composite action.

Image 4 of Go to Record and Update Record example showing order of 2 blocks in composite action

In the Block Settings tab, enter values for the Update a Record block. For example, Field Name = Subject (Summary) and Field Value = Printer Error 14 - Toner Cartridge needs changing. The field value was previously Printer error 10.

Click Save.

Go to Service Desk Analyst workspace > Incidents list view.

Go to the Incident record 10928. Select the created action GTR-Action1 and execute it.

Check the summary of the other incident record 10413.

The summary should have changed to Printer Error 14 - Toner Cartridge needs changing as specified.