I'm looking at including and excluding configuration parameters from passing through to the profile load script, which when I check it the parameter is passed through to the PLS, with whatever is defined in the instance, even when the value is not defined, and only passed to the PLS when unchecked and the value is set.
This feels very backwards/a bug.
We do want to be able to send through the parameter to the PLS if it's not initialized, as we want to combine it with data from DOM, but define the parameters wanted to be set via the instance.
Hi Jorge,
That is correct.
I have been looking at having a placeholder value to signify the value needs to be retrieved from DOM as well; though as the data types are different it’s not consistent.
The bookings will be created through a script, but also we’ll be using the PLS ad-hoc with resource automation as well, when we need to re-apply a config.
I see that this question has been inactive for some time. Do you still need more information for this? If not, could you select Jorge’s answer to indicate that the question is resolved?
The requirement for our case aren't currently a possibility, so a new feature has been requested.
SRM: Allow all profile instance parameters to be returned to a profile load script, even when null.
Hi Philip, am I assuming correct that your use case is: you have a Profile Instance with some parameter values and other parameters without values, then for the parameters without values you want to set values from a DOM Instance?
If not, could you please elaborate on your use case? Maybe with some screenshots.
Can you also describe how the bookings are created? Through a script or the wizard?