2016-09-20 05:58 AM
I am trying to set up a new custom data source in WFA 4.0. I want the data for this to live in the Playground DB, so I set up my dictionary entry to reference that scheme. But when I move on to set up the aquisition script in Data Source Types, the Playground scheme is not offered in the drop down. I can create a custom scheme, and that will be available, but not Playground.
In 3.1, I could use Playground for custom data sources. Was this feature removed intentionally, or is this an oversight?
2016-09-20 09:43 PM - edited 2016-09-20 09:45 PM
Let me introduce this new feature to you.
WFA4.0 has introduced 'scheme management' which allows you to create a new scheme. WFA3.1 and earlier didn't allow you to create a scheme, but the new scheme only gets created via dictionary.
When you create a new scheme, you need to select a 'Type' for it
1. Data source Acquistion : The scheme will be used for Data Source Acuquistion. This means that only WFA can fill data in this scheme using WFA Data Source acquistion methods i.e. SQL or Script. The default WFA DB user 'wfa' will not be able to write data into this scheme. Only WFA can fill data via acquisition mechanisms.
2. Other : This scheme is for purpose other than Data Source acquistion. This sheme will NOT appear to you in the drop-down selection for a new Data Source type. The default DB user 'wfa' has full priviledges on this scheme. So I can fill data in this scheme using INSERT query statements.
The playground as in 3.1 was the only scheme where DB user 'wfa' could fill data directly. In WFA 4.0 definition, this fall for the 'Other' scheme. Hence you are not being shown the play ground scheme for creating a new Data Source Type.
I would want to know what is the purpose of choosing the 'playground' scheme for your data Source script?
What can you do if you still want to use playground itself?
I can provide you some ways and that may depend on the answer to the above question.
2016-09-22 06:27 AM
Thanks for offering to help. I created a playground table for a workflow that modifies login roles in a cluster, and found later that by creating a dictionary for that table I could use the objects in the planning phase instead of using invokeMySQLQuery all over my command steps. There are several workflows in the field using this now. How will I keep them from breaking when it comes time to upgrade to WFA 4.0?
2016-09-22 09:23 AM
The existing stuff on 'playground' will continue to work even after upgrade to 4.0. Modifying existing code will also work. You can even import Data Source types created on playground into 4.0 and it can then be modified.
Only new Datasource types can't be added on playground in wfa4.0.