short description for each approval in workflow

[Gemma4]

Hi Everyone,

I have a new hire workflow that I’m having trouble understanding how to configure the approval task short descriptions to display a unique short description. I’m not the best with scripts and workflows and would appreciate any insight you all have. Below is a copy of the workflow we are using and the approvers that are currently getting generated. As you can see, all the approver short descriptions look the same. Instead, it would be great if the short description pulled the information from the SD for 0365 run script and SD for laptop approval run script. So, for example, the short description should read New Hire Checklist Request first name last name and task details. I’ve tried so many variations in the run script and adding a new set values without any luck. This would allow the approver to understand if they approving a O365 of Laptop request. 

Thanks in advance for any feedback you have! 

Gemma

[Gemma4]

correct I commented them out because they were not working correctly. In the O365, it was causing all the approval  tasks to have "O365 Distribution Lists Approval for" and the short description of the ritm

[Kristen Ankeny]

What is the configuration is the "Approval - Group" after the O365 run script?

[Gemma4]

Attached is approval group and it is also commented out

[Kristen Ankeny]

Right, that code won't work because it's for setting the approver(s) for the task with code instead of a person or group reference.

Looking further in a personal dev, I think the short description you are seeing on that list view is one of two things:

- A custom field on the sysapproval_approver table, in which case the backend name will most likely start with u_ or x_

- Displaying the short description from the requested item they are approving, in which case you won't be able to have it be different for each approval record.

If the former, you're better off adding a business rule on create of approval records to populate the custom short description with the right value. In this case, you're going to want to come up with a pattern that works across all forms.

If the latter, what you're trying to achieve will not work. As a note, in the workflow, current references the sc_req_item. So, when you set short description for current, you're updating the short description on the requested item.

[Gemma4]

Thank you, I'll see what I can figure out with a business rule.