SWF_WORKFLOW_CONDITION_DEF - Workflow parameter input field disappears when property is assigned

[ragunath_1996]

HI Team,

Thank you for your suggestion. I implemented the solution exactly as recommended using both extension points:

• SWF_WORKFLOW_CONDITION_DEF
• SWF_WORKFLOW_CONDITION_EVAL

The custom workflow condition is successfully displayed in Manage Workflows for Purchase Requisitions.

However, I am facing an issue while trying to provide F4 Value Help for the custom parameter.

What I have tested

1. Without OData configuration

Parameter contains only:

• id
• name
• shorttext
• xsd_type
• mandatory
• ddic_type

Result

• Input field is displayed.
• No F4 help is available

2. Using a Custom CDS View (Scenario = Value Help)

I created a custom CDS View based on I_PurchaseRequisitionType and published it successfully.

Configured in SWF_WORKFLOW_CONDITION_DEF:

service_path
entity
property

Result

• The parameter input field disappears completely.

3. Using SAP Standard Workflow Value Help

Instead of the custom CDS, I used the standard workflow service:

• Service: S_MMPURWORKFLOWVH_CDS
• EntitySet: C_PurReqnTypeForWorkflow
• Property: PurchasingDocumentType

I verified from the $metadata that:

• Service exists
• EntitySet exists
• Property exists

However, after assigning the property in the parameter definition, the workflow UI no longer displays the input field.

Summary of my observations

Configuration Result

id + name + mandatory	Input field displayed
+ ddic_type	Input field displayed
+ service_path	Input field displayed
+ entity	Input field displayed
+ property	Input field disappears completely

It appears that the Workflow framework rejects the parameter once the property is specified.

My Question

Has anyone successfully implemented an F4 Value Help for a custom workflow condition parameter in SWF_WORKFLOW_CONDITION_DEF?

If yes, could you please share:

1. Whether a standard or custom OData service was used?
2. Does the property require additional ValueList/Common.ValueList annotations?
3. Is F4 Help currently supported for custom workflow condition parameters in SAP S/4HANA Cloud Public Edition, or is this a framework limitation?

Any guidance would be greatly appreciated.

Thank you!