Hi, I have a service definition with a few optional resources, when in de config mode it will always select an available resource but i want to have it selected by default the no resource. Is that possible and so how do i do that?
I believe that Diogo is mainly referring to the C# code on performing silent bookings, such as bookings automatically inserted into the system through DataMiner Jobs. The 'ShouldAutoSelectResource' property of the Function object can then indeed be used to toggle the automatic selection of resources.
However, if you are referring to having no resource selection done automatically into the booking wizard, this can be configured on a per node level into the service definition. This is done simply by adding a property 'Auto Select Resource' to the node, and setting value to true or false.
More information can also be found on DataMiner SRM 1.2.9 Release Notes - DataMiner Dojo
Below a screenshot of the property onto a node of the service definition.
As a result, the wizard will not select a resource by default and the selection will be left at 'No resource'. It will be up to the user to select the resource manually.
Thanks! I’ll give it a try, i don’t believe the DTR is going to ruin it cause i can finish with an no resource assigned for that node.
Hi Gerwin,
When you are bulding the node Function object you need to assign the value 'false' to its 'ShouldAutoSelectResource' property.
By default that value is set to 'true', hence a resource is selected by default.
Hope this helps.
Regards,
Alright let me try that thanks.
Is there any documentation available on the available options like these?
Note however that if any Data Transfer Rules (DTR) would be configured onto the service definition that have been coded to automatically select resource, the resource would of course get selected. So in case that you have configured the Property ‘Auto Select Resource’ with value ‘false’ and a resource would still be auto-selected, I would recommend to also check the configured DTR rules.
One last item, functionality available since SRM 1.2.9.