Question
MKB Brandstof
NL
Last activity: 25 Aug 2025 10:43 EDT
Bulding a custom DMS task that asks user for dynamic parameters
I am trying to implement a Custom DMS Task that requests the value of the dynamic parameters.
I've been trying to follow the following instructions:
However I have the feeling it misses some key information:
- Below "Add callback for user inputs" in the screen shot under 2. it shows that the JSON request is copied from Param.jsonData however it doesn't say how to populate this property. What is the specific .pxObjClass I need to use to fill this parameter as JSON?
- Next "Capturing user inputs" shows how the user should enter the dynamic properties, but it does not say how the custom task handles the users response. I assume that DMS calls the environment again and is handled by the DMTaskProcessor queue. Is the RunTask activity run again or is another activity required?
Could you help me fill in the blanks?
Updated: 25 Aug 2025 10:43 EDT
HCA Healthcare
US
in your RunTask activity, when you detect you need values, build the UI schema as JSON and put it in Param.jsonData; it’s just a string, so no special pxObjClass is required either hand-craft the JSON or create a temp Data/Embed page of your own class and pxConvertPageToString. Deployment Manager will pause the task and show that form to the user at run time. When the user clicks Submit, the orchestrator calls the same RunTask again and the entered values appear on your parameter page under .taskInfo.inputParameters(n).value read them there and proceed. After you finish, call ResolveTaskSuccess (TaskID, OrchestratorURL, LogContent) to complete the step; if you want the pipeline to stop for operator action, call ResolveTaskWithError. You do not need a second “callback” activity the DMTaskProcessor on the orchestrator manages the wait/resume and simply re-invokes your RunTask with the user inputs. Practical tips: keep your JSON schema minimal (name, label, type, required, options), match the input names to what you read from .taskInfo.inputParameters(), and log Param.jsonData and the inputs on first runs to confirm mapping.