The Inherent ALE and Residual ALE value is different in native UI and Workspace

[jigyasaarora23]

In case of a quantitative type inherent assessment, the Inherent ALE (calculated based on a script ), it's value is different in native UI than the one in the Workspace. The one in Native UI is the correct one, according to the calculation in the script.

In a Risk assessment methodology, we have a factor which is choice drop down type , it is used to calculate the inherent ALE along with a currency type question. 

PFB the details of the factors and calculation as per the requirement:

Inherent Assessment - Below factor will be choice type question. Also, this will be mandatory question
i) What is the worst-case scenario number of injuries (requiring first aid, medical treatment and/or hospitalisations) we expect due to our business activities and operations?
Options:
0-49 (Backend value should be 25)
50-99 (Backend value should be 75)
>100(Backend value should be 100)
ii) What is the worst case financial loss you expect for the risk? (currency type question)

Inherent ALE should be calculated as per below formula
Inherent ALE = WORST-CASE OUTPUT(backend value of the choice selected in question 1) x ADJUSTMENT VALUE
Where adjustment value is $500000

PFA the details of the assessment for your reference.

[jaikishan1]

Hi @jigyasaarora23 ,

The inherent ALE in native UI shows the calculated amount based on the reference currency which is determined by the system locale.
This value displayed in the workspace is the inherent ALE amount from native UI converted to the session currency defined by the user.
The difference observed could be due to this conversion. If the session and reference currency are sam and still difference is being observed, can you please check if there is any customisation on the fields or maybe provide an instance with a sample setup to review it further.

Please mark this answer as helpful if it serves your purpose.

Regards,
Jai

[jaikishan1]

Hi @jigyasaarora23 ,

We have also observed this discrepancy across native UI and workspace view and this has been fixed made consistent from the current release.

Regards,
Jai