Isn't this what "Reservation" in a command essentially does? Updating WFA cache tables instantly without the need for wait for discovery and DataSource acquistion. WFA3.0 allows users to create Reservation code for custom commands as well. But I will agree that they are complex to write unless you are an expert. If you can , its the best.
WFA cache tables can only be updated by WFA Datasource acquistion or Reservation except on playground schema. So you can't have user commands update WFA cache tables using SQL insert. So as a possible way and as a simpler alternative to writing Reservation code, you can add 2 commands in your workflow.
1. A command that will refresh Data On OCUM.
2. A command to run the DataSource acquistion immediately.
Now when your workflow completes, your WFA Data will always be up to date. Its not as instant as a reservation will get you, but it works.
You can take see an example here in my reply. http://community.netapp.com/t5/OnCommand-Storage-Management-Software-Discussions/Is-WFA-truly-open-source/m-p/61199#M12754
I've given a code to refresh monitoring on OCUM6.X then a command to run DataSource acquistion on the OCUM. It was mainly provided when custom commands couldn't have resevation code and waiting for discover and acquistion cycle was to be minimized.
If this post resolved your issue, help others by selecting ACCEPT AS SOLUTION or adding a KUDO.