This file provides sub functions for BRPM - BSA communication. Since our implementation relied on NSH Script Jobs, to provide more flexibility and avoid restrictions, we decided to enhance this file with e.g.:
return "SystemObject/Static Group/Job Group"
return "SystemObject/Static Group/Abstract Depot Group/Depot Group"
return "SystemObject/Depot Object/NSH Script"
We also use sub functions to:
- create an nsh job via SOAP call
- add nshscriptparametervalues to a job
Adding those would be nice. Right now on every release of a new patch these changes have to be applied again. Or is there a strict design decision against the use of NSH Script Jobs?