For an orchestration project, we need to create bookings based on requests from a third-party application. During the processing, I would like to define a Profile Instance with the specific values received from the other system so that the assigned resource will have the designated configuration.
While I can dynamically create new profile instances, I wonder how I can "clone in memory" an existing one and attach it to the selected resource so that I don't need to worry about cleaning them later.
In the SRM documentation, it seems that I need to use a Profile Instance by Value. Still, it is not clear how to create it programmatically and if there is any consideration for its definition and usage.
Hi Gelber,
I don't think that you need a Profile Instance in this case. The way I did it was by defining all needed Profile Parameters during booking creation instead of providing a Profile Instance.
You can indeed create some Profile Instances for testing purposes during development of your PLS. The PLS should behave exactly the same when the Profile Parameter data comes from a Profile Instance or provided during creation of the booking.
Thanks Jens. I’ll try it, although I wonder how we can use our Profile Tester functionality to quickly validate the PLS. Perhaps it’s not a big deal because I can always use a Profile Instance to develop the PLS and then add the code assign parameters to the resources during the booking creation. Will that work?