SWF_WORKFLOW_CONDITION_DEF - Workflow parameter input field disappears when property is assigned

[#1]

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!

[ElenaPuica]

Hello!

F4 value help for custom workflow condition parameters is supported in Public Cloud. This is not a framework limitation. Multiple working implementations exist, including SAP KBA 3754591, which provides a complete, working template using the same six parameter fields.

Resolution steps:

• Correct the entity value. Open the $metadata of S_MMPURWORKFLOWVH_CDS, locate the <EntityContainer> section, and use the exact EntitySet name listed there (not the EntityType). This is the primary fix for the disappearing field. Confirm the chosen property (e.g. the PR document type field) exists on that EntitySet.
• Prefer the standard value-help service. Use the standard S_MMPURWORKFLOWVH_CDS service rather than a custom CDS view. For standard services, the value help is already attached to the property in the OData model and requires no additional ValueList/Common.ValueList annotation. A custom CDS only works if it is exposed as an OData service and built with proper value-help annotations; an extra failure surface that the standard service avoids.
• Keep all parameter fields populated together. Include xsd_type (string) alongside service_path, entity, and property, matching the working structure:

service_path = '/sap/opu/odata/sap/S_MMPURWORKFLOWVH_CDS'

entity       = '<EntitySet name from $metadata>'

property     = '<property from that EntitySet>'

xsd_type     = if_swf_flex_ifs_condition_def=>cs_xstype-string

mandatory    = abap_true

• Align the parameter name across both BAdIs. The technical name set in SWF_WORKFLOW_CONDITION_DEF must be read with the identical key in SWF_WORKFLOW_CONDITION_EVAL (READ TABLE it_parameter_value ... WITH KEY name = '<same name>'). A mismatch causes the evaluation to fail silently even after the field displays correctly.
• Verify prerequisites. Ensure there is an active workflow scenario, and keep the Automatic Release feature active in the workflow configuration for consistent processing once conditions are met.

Answers to the questions:

• Standard or custom OData service? Both work; the standard S_MMPURWORKFLOWVH_CDS is the reliable choice and is what the reference implementations use.
• ValueList/Common.ValueList annotations required? Not for a standard service, the value help is already in the standard model. Required only if using a custom CDS built as a value-help provider.
• Is F4 supported or a framework limitation? Supported. The disappearing field is a configuration/metadata-resolution issue (wrong entity value).

[ragunath_1996]

Thank you for your detailed response. I followed your suggestions and verified the implementation again. Current implementation Service Path: /sap/opu/odata/sap/S_MMPURWORKFLOWVH_CDS EntitySet: C_PurReqnTypeForWorkflow (verified from the $metadata EntityContainer) Property: PurchasingDocumentType xsd_type: if_swf_flex_ifs_condition_def=>cs_xstype-string mandatory: abap_true Current behavior The custom workflow condition is displayed successfully in Manage Workflows for Purchase Requisitions. The input field is now displayed correctly. However, the F4 Value Help is still not displayed. The field only allows manual entry of the document type (e.g., NB, ZNB). I also verified the metadata of S_MMPURWORKFLOWVH_CDS. The property PurchasingDocumentType exists and is associated with PurchasingDocumentTypeName using sap:text. However, I could not identify any additional ValueList-related annotations for this property. Could you please clarify the following? Is PurchasingDocumentType supported as a value help property for SWF_WORKFLOW_CONDITION_DEF? Is there another standard EntitySet/Property that should be used for Purchase Requisition Document Type instead of C_PurReqnTypeForWorkflow/PurchasingDocumentType? If this scenario is supported, could you please share a working example specifically for Purchase Requisition Document Type, similar to the example in KBA 3754591? - If possible, could you also share a sample implementation for Purchase Requisition Document Type, as the KBA primarily demonstrates the implementation pattern but does not explicitly cover this property. Thank you for your support.