This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

DVD issues in web client. SM 9.51

Dear All,

In our SM 9.51, visibility conditions applied to fields in format is working properly in windows client, but not in web client. Is this a known problem & do we have any solution? ..Pls help

Parents
  • Suggested Answer

    0  

    Not sure if this is your issue but there is an old DVD issue where OR operand works in windows client but not in web client. If you are using OR operand, please change it to |.

    | will work in both windows and web clients.

    Best Regards,

    Jason

    Although I am an OpenText employee, I am speaking for myself and not for OpenText.
    If you found this post useful, give it a “Like” or click on "Verify Answer" under the "More" button

  • 0 in reply to   

    Thanks for your reply Jason, But this is already verified, we are using operand '|' and not 'OR' !!

  • 0 in reply to 

    One more thing I want to add here is... Initially, everything was fine from last 4 years. The issue started coming recently. The old formats where we have similar visibility conditions are working fine. Only new developments are giving this type of issues..

  • Suggested Answer

    0   in reply to 

    Something must be different. Strange that old formats works but not new formats. To confirm, paste exact old visibility condition from old format into new format and see if it works. That will confirm if it's specific to the condition or not.
    Also, try debugging the condition. e.g condition = ($A && $B) || $C. Remove each variable onet by one and retest to confirm which variable is the root cause. test condition = ($A && $B), test condition = $A, test condition = $B, test condition = $C. 

    I also encountered 2 similar issues with a customer. See https://kmviewer.saas.microfocus.com/#/OCTCR19X1117220 and https://kmviewer.saas.microfocus.com/#/OCTCR19X1936439.

    My customer was using multiselect.selection function to create a variable in a condition. This variable resulted in a NULL value. Windows client is smarter, if the variable is NULL, it does not perform the condition. Web client will try to perform the condition even if the variable is NULL which results in error condition. So, check if any of your variables are returning NULL value. You can add the variable into the format to check on it's value. Web client do not handle NULL value properly and this defect will most likely be fixed in versions newer than 9.72

    Best Regards,

    Jason

    Although I am an OpenText employee, I am speaking for myself and not for OpenText.
    If you found this post useful, give it a “Like” or click on "Verify Answer" under the "More" button

Reply
  • Suggested Answer

    0   in reply to 

    Something must be different. Strange that old formats works but not new formats. To confirm, paste exact old visibility condition from old format into new format and see if it works. That will confirm if it's specific to the condition or not.
    Also, try debugging the condition. e.g condition = ($A && $B) || $C. Remove each variable onet by one and retest to confirm which variable is the root cause. test condition = ($A && $B), test condition = $A, test condition = $B, test condition = $C. 

    I also encountered 2 similar issues with a customer. See https://kmviewer.saas.microfocus.com/#/OCTCR19X1117220 and https://kmviewer.saas.microfocus.com/#/OCTCR19X1936439.

    My customer was using multiselect.selection function to create a variable in a condition. This variable resulted in a NULL value. Windows client is smarter, if the variable is NULL, it does not perform the condition. Web client will try to perform the condition even if the variable is NULL which results in error condition. So, check if any of your variables are returning NULL value. You can add the variable into the format to check on it's value. Web client do not handle NULL value properly and this defect will most likely be fixed in versions newer than 9.72

    Best Regards,

    Jason

    Although I am an OpenText employee, I am speaking for myself and not for OpenText.
    If you found this post useful, give it a “Like” or click on "Verify Answer" under the "More" button

Children