Yes, cifs_share.name is getting cached after one cycle of data acquisition.
But my question is about the period from the time workflow is executed till the next execution cycle.
Is there any way to have cifs_share.name in "Reservations" ?
I'm developing a workflow where I choose an SVM where cifs share will be created.
One of my filters is to pick an SVM where this share doesn't exists (customer may request to create multiple shares (one share request per workflow) with same name and they should go on different SVM's).
This filter doesn't work untill after one cycle of data acquisition.
The reservations have to be written for the custom commands based on what the command does. These are SQL scripts and one needs to understand the database schema to do this. This cannot be done for custom commands currently.
As Adai mentioned, the upcoming release of WFA will allow you to associate a SQL script with your custom command which will handle the reservations. Hope this helps.