We want to change the default value from “Move to Inventory” to “Move to transit” on the transport task line. However I am not able to do this using page designer. I have also tried to use custom event without success:
Does anyone know how to do this?
Best answer by SimonTestard
@Abdul that’s not why, it’s because the Json item Destination is already prepopulated, and therefore you don’t need to Register it as a variable for it to be returned to the client handler :)
If you attempt to register it, it’ll try to register the same field twice which causes a serialization issue, see this thread.
If you test troubleshoot, you’ll see that the following variables are already registered by the time the workflow triggers, so any change to those doesnt require the variable be registered again.
Thanks @Abdul and @SimonTestard . I have tried to create this. See workflow:
However, I cant seem to find any fitting Call names on the projection action. Is it possible I have to use Data action type instead of Call action type?
TransportTask/Form (server error) Error while serializing contents.
This error happens when the server cannot serialize the data to be sent to the client. A common cause is that one attribute's length exceeds the defined maxlength in the projection. To find more info, open Log Window or Debug Console, refresh and then check Network Tab in DevTools. In the response there can be more detailed information about the exception. Error details: N/A
@henros, it seems like a general error to me. Discuss with technical support. Disable the workflow action, and then check whether the error has been resolved.
@Abdul that’s not why, it’s because the Json item Destination is already prepopulated, and therefore you don’t need to Register it as a variable for it to be returned to the client handler :)
If you attempt to register it, it’ll try to register the same field twice which causes a serialization issue, see this thread.
If you test troubleshoot, you’ll see that the following variables are already registered by the time the workflow triggers, so any change to those doesnt require the variable be registered again.
@Abdul that’s not why, it’s because the Json item Destination is already prepopulated, and therefore you don’t need to Register it as a variable for it to be returned to the client handler :)
If you attempt to register it, it’ll try to register the same field twice which causes a serialization issue, see this thread.
If you test troubleshoot, you’ll see that the following variables are already registered by the time the workflow triggers, so any change to those doesnt require the variable be registered again.
We use 3 different kinds of cookies. You can choose which cookies you want to accept. We need basic cookies to make this site work, therefore these are the minimum you can select. Learn more about our cookies.