You’re offline. This is a read only version of the page.
2,100
Hi,
I have upgraded PSA in my organisation. But due to that I am facing an issue in Project Contract entity.
> The earlier PSA version was PSA V2.4. With this version the "Contract Status Reason" field (optionset field) on Project Contract entity had limited options.
> After upgrading to PSA V3.10, this field has more or in fact all required options.
> As per the client's needs we filter the options of the field using custom JavaScript code. Now, it doesn't have "Lost", "Abandoned" and "Confirmed" options as we've made them hidden via script. But, due to this, the out-of-the-box "Close as Lost" and "Confirm" functionalities have been stopped.
> When we click "Close as Lost" button, the popup ask for the reason either "Lost" or "Abandoned". And after confirming the functionality, it will set that value in "Contract Status Reason" field. But as we mentioned above, we have filter out these options; the "Close as Lost" functionality breaks and set blank in "Contract Status Reason" field.
Could anyone please help me with this?
Thank you.
Hi,
From your above explanation, I understand you are using custom JS code to achieve clients need to filter the options of the field. Below are the options available for the field.
Why did you hide the option "Lost", "Abondoned", "Confirmed" ? What I see is system is behaving as expected and asking for right value, its just because we have hide the value it is no longer available and thus leading to blank value.
If you dont want to use value "Lost" or "Abondoned", you do see an option to add your custom value in it. Accordingly, you can then set those values via JS when you "Close as Lost"
Share
Report
All responses (
Answers (
