Hide Request Price in service workspace

[tpeleg]

Hi,

Is it possible to hide price on service operations workspace without configure ui builder or changing requestInfo SNC script include?

Thanks,

Tomer

[TejasSN_LogicX]

try this

https://www.youtube.com/watch?v=52YuG5FrNhw

[tpeleg]

Thanks, I've tried this but it's effecting service portal and not WS

[Ravi Gaurav]

Hi @tpeleg 

Out-of-the-box, there is no property or toggle to hide the Request Price in Service Operations Workspace without either UI Builder config or a script change.

You have two practical options:

 

1. Duplicate and Adjust the Workspace Configuration

• In Service Operations Workspace → Configuration, duplicate the Record Information component (the card/record view that displays Request details).

• Remove the price field from that duplicated configuration.

• Assign your new configuration to the roles or users who should not see price.

This avoids touching the requestInfo SNC Script Include but does involve Workspace config changes.

 

2. Field-Level Security with ACLs

• Add a READ ACL on the price (and recurring_price, if used) fields on the sc_request / sc_req_item tables.

• Restrict visibility so only authorized roles (e.g. admin, finance) can see prices.

• For everyone else, the field will be blank in Workspace and anywhere else in the platform.

This is simpler to implement and doesn’t require UI Builder, but it applies system-wide.

[MortenPettersen]

Greetings tpeleg

I was able to hide the price field on the record form itself, by using Form Builder, and then editing the view name 'Service Operations Workspace' for the sc_request table. You can get to do this point by opening a sc_request record in classic/UI16 and rightclicking -> configure -> Form Builder. This approach means you are only making a config change for the form in the App scope 'Request Management for Service Operations Workspace' and the page variant is intact (per my understanding at least).

If the customer want's to get it removed from the banner on the top, I am not sure how to get that part done. Is that also in the requirement?

Screenshot: