In this Article we will see how to get the WF/PM Connection String to use within the WebPart.
Articles
- - -
Currently the previous Articles have shown static data either hardcoded into the WebPart, Input by the User when the configured or information available from the current Session of the PM instance.
To make it more useful we would need to be able to talk to the Process Manager database to retrieve data to display.
Where is this? Open the Workflow Explorer exe.
SymQ Configuration
SymQ_Local_Defaults
Scroll down to 'local.orm'
Edit to see the 'Sql Connection String'
Data Source=SERVER;Initial Catalog=ProcessManager;Integrated Security=True;Pooling=True;Connect Timeout=30
There is also the 'local.workflowsqlexchange-'.
Replace with your Server name and Database Instance.
We could hardcode this in the code for the WebPart but this wouldn't be very useful as if it ever changed you'd have to update the rebuild/redeploy the DLL.
Another option would be to create another web.config just for our WebPart and reference that.
We could also decrypt the Process Manager web.config as shown in a custom Script component added to a sample Workflow Project.
We need a way to get this in code, thankfully "bcason" has already shown us how.
Workflow/ServiceDesk - How To Extract the (local.orm) Sql Connection String Code (Script) Component Sql Connection String Extractor https://www.symantec.com/connect/blogs/workflowservicedesk-how-extract-localorm-sql-connection-string
Amend this to use as a class in our Project.
This is the reason for adding 'Symantec.SymQ.dll' in a previous Article.
We can then call this method wherever we need a Connection String. This is shown in the SQL Article.
Related
local.orm SQL Connection String - Component