Invalid condition in htpml

Products

• CA Service Desk Manager
• CA Service Management - Service Desk Manager

Issue/Introduction

Custom Analyst role created to allow access to specific ticket types and request areas.

Seeing this error message in the stdlog

ERROR  parse.c  8968 Unable to evaluate PDM_IF at xx_wf_tab.htmpl[108] due to invalid condition:  "FIELD1" != "" && (("FIELD1" != "VALUE1") || ("FIELD1" != "VALUE2"))

Environment

Release: 12.6 or higher
Component:  CA Service Desk Manager

Cause

Invalid syntax was used in customisations

Resolution

Forms will need to be examined for any recent changes made to the customisations introduced.

In this example, the affected form was xx_wf_tab.htmpl

Error received when evaluating statement

</PDM_IF>
<PDM_IF "$args.category" != "" && "$args.category" != "VALUE1" && "$args.category" != "VALUE2">
<PDM_IF "$prop.form_name_3" != "edit"  && $args.status == "OP">
<PDM_MACRO name=button Caption="Insert Tasks[I]" Func="do_insert_tasks()" hotkey_name="Insert Tasks[I]" ID=btn909 Width=120>
<PDM_ELSE>
<PDM_MACRO name=button Caption="Insert Tasks[I]" Disabled=yes Func="do_insert_tasks()" hotkey_name="Insert Tasks[I]" ID=btn909 Width=120>
</PDM_IF>
<PDM_ELSE>
<PDM_MACRO name=button Caption="Insert Tasks[I]" Func="do_insert_tasks()" hotkey_name="Insert Tasks[I]" ID=btn909 Width=120>
</PDM_IF>
<PDM_MACRO name=btnEndRow>

Corrected by separating the IF statements like the example below:

<PDM_IF "$prop.form_name_2" == "iss" || "$prop.form_name_2" == "chg" || "$prop.form_name_2" == "cr" || "$prop.form_name_2" == "in" || "$prop.form_name_2" == "pr" || "$prop.form_name_2" == "approval_console">
 <PDM_IF "$args.category" != "" && "$args.category" != "VALUE1" && "$args.category" != "VALUE2">
  <PDM_MACRO name=tabBanner title="Classic Workflow Tasks - not ootb" add_btns=true>
 <PDM_ELSE>
  <PDM_MACRO name=tabBanner title="Classic Workflow Tasks" add_btns=true>
 </PDM_IF>
<PDM_ELSE>
  <PDM_MACRO NAME=tabBanner title="Workflow Tasks">
</PDM_IF>

Additional Information

Broadcom is not permitted to debug or troubleshoot custom changes that have been introduced.  

Additional information on modifying forms via WSP is available through our documentation