Approval Record - Display Value

[GeoffreyOptumOp]

Hi, smart folks.  The Approval table, sysapproval_approver, has as it's only Display column, a document_id type field.

The document_id field references another table, sc_req_item.

But this has the effect of making the Approval records LOOK LIKE Request Item records.  See two examples below, from the Platform UI (regular form view) and from the ITSM Agent Workspace.

Is there a good way of making these show up a little differently, such as "Approval for Requested Item XXXXXXXX" instead of just "Requested Item XXXXXXXX"?  Thoughts?

[Allen Andreas · Accepted solution]

Hi,

This is because the sysapproval_approver table is using that field as the "display", so it's just showing whatever the display value is for that reference field.

What you could do, is create a string field (read-only) and then write a before business rule to concatenate "Approval for: " and then also add the display value of the document_id field to it, then, set that as your display column on the table dictionary record.

For current records, of course you'd need to create a fix script that would go through and populate this field the same as the business rule would for future records.

Please mark reply as Helpful/Correct, if applicable. Thanks!

[GeoffreyOptumOp]

Hi, @Allen Andreas 

Thanks.  I was thinking about something along those lines myself, so I decided to give it a shot.  But I am seeing some unexpected behavior.  Perhaps you (or someone) can get me across the finish line on this...

On the "sysapproval_approver" table, I created a column called "u_prefix", and I gave it a default value of simply "Approval".  And I set that column to be the Only display column:

Then for "sysapprover_approval" I created a Display Business Rule as follows:

This shows up on Forms like this:

And on ITSM Agent Workspace, like this:

Then I tried the following:

This gave me exactly what I wanted on the forms!

But, there seems to be no change inside of ITSM Agent Workspace:

Is the Display business rule somehow NOT RUN there?  What am I missing?  Thanks!!

[Allen Andreas]

Hi,

To clarify, are you saying this is a display business rule you're using?

Outside of that, there has been a change from your initial screenshot to what you've done now as previously it showed the display value for the document_id field and now it shows Approval.

Anyways, if the record you are looking at has a value for that new field you made...for example, if the back-end UI: 

Then it'll show on the workspace like so:

When that field doesn't have a value, but you've set that to be the table's display field...it'll default to just showing "Approval" and nothing else as you see in your screenshot. Here's me removing the value in the back-end UI from that new field so you can see what happens:

As I mentioned above, you'd want to use a before business rule on insert of a new record and then have your business rule populate that new field. It's not a display business rule.

Please mark reply as Helpful/Correct, if applicable. Thanks!

[GeoffreyOptumOp]

@Allen Andreas Thanks again.

I was able to get this working using the Before Update business rule as you suggested.

I did also have to make a modification to a value in the Agent Workspace called the "Primary Field", in table sys_aw_form_header, in order to get the change to show up in Agent Workspace.  Hopefully there are no side-effects from making that change also.