Variable formatter

LucileC
Tera Expert

Hello, 

I have created a record producer with A LOT of variables and a lot of catalog ui policies.

This record producer creates a facilities request, I displayed theses variables on the facilities request form but they are unreadable.

When I submit the form from the back-end it works perfectly.

[EDIT] The first screenshot is the variables with the request submitted from the portal and the second one is the request submitted by the back-end.

find_real_file.png

find_real_file.png

We have a modify sc_cat_item widget if it's of any help for you to know.

Does any one has an idea or has already seen this type of bug ?

[EDIT] The variables are not displayed in the same order as the one on the portal form on the first screenshot.

Thanks you

6 REPLIES 6

Pranesh072
Mega Sage
Mega Sage

OOB variable editor is writable.You must added something to it.

You can check catlog client script and ui policy.

You can check permission section of variables.

 

Thanks for your reply.

The fact that the variable editor is read only isn't an issue for now. 
I tried to check the "Applies on the Target Record" option on catalog ui policies hoping that less variables will show on the variable editor, but it doesn't work neither.

have you checked the permission tab of variable?

Allen Andreas
Administrator
Administrator

Hi,

So...just to clarify, you are saying when a user utilizes the Service Portal to submit this record producer, the end-result in the back-end UI is your top screenshot?

And then when a user uses the back-end UI to submit the record producer, the end-result in the back-end UI is your bottom screenshot?

If so, without seeing or knowing what you've done with the sc_cat_item widget or variable editor, we may not be able to assist.

I personally have not seen this issue before.

I'm also not sure why screenshot one the fields are editable, etc. whereas screenshot two they're read-only, etc.

It may be that you included screenshots of different sections, but please keep consistency for troubleshooting so we can assist else it just causes more questions.

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


Please consider marking my reply as Helpful and/or Accept Solution, if applicable. Thanks!