Skip to main content
Solved

Workflow to Create Document Text for a Shipment – Not Working as Expected

  • November 17, 2025
  • 1 reply
  • 34 views

Forum|alt.badge.img+8

Hello,

I'm trying to create a workflow to add a Document Text to a shipment. The process works in Postman but fails to have the desired effect when used in the workflow, despite no errors occurring during debugging.

Workflow Steps

  1. Get shipment data
    Retrieve ShipmentId and NoteId.

  2. Create a NoteText
    POST to:
    XXX.de/main/ifsapplications/projection/v1/ShipmentHandling.svc/NoteTexts
    → This returns an objkey.

  3. Create DetailNote using objkey
    POST to:
    XXX.de/main/ifsapplications/projection/v1/ShipmentHandling.svc/NoteTexts(Objkey='43C5E76DC0AF433FE0632A81A8C0B66A')/DetailNotes
    Payload:

    { "OutputType": "FUSS", "NoteId": 33593601, "NoteText": "It is a Text" }

Problem

The workflow runs without any error, but no document text appears in the shipment.
Interestingly, if I manually create a document text with the same OutputType, I get a message in the debugger that a document text already exists. This suggests the request is targeting the right resource, but the document text isn’t being created as expected in the workflow.

Here are the steps from the workflow.

 

Question:
What might be missing or wrong in this process? Is there a step or dependency that needs to be handled differently within the workflow?

Thanks,
Golo

Best answer by Achala

When the Workflow runs in Troubleshoot mode (Debug mode), please note that any data changes made by the IFS API task within the Workflow are not persisted. As a result, you will not see the data updates reflected during this mode.

To verify the data changes in Troubleshoot mode, you can add a READ task immediately after the CreateDetailNotes task to read the created record and run the Workflow again in Troubleshoot Mode.

1 reply

Forum|alt.badge.img+3
  • Do Gooder (Employee)
  • 14 replies
  • Answer
  • November 18, 2025

When the Workflow runs in Troubleshoot mode (Debug mode), please note that any data changes made by the IFS API task within the Workflow are not persisted. As a result, you will not see the data updates reflected during this mode.

To verify the data changes in Troubleshoot mode, you can add a READ task immediately after the CreateDetailNotes task to read the created record and run the Workflow again in Troubleshoot Mode.