Here I will not go into details of creating Automation Library along with process data type.
This is described in Workflow 7.6 User Guide in section ‘Creating Automation Library’ on pages 245-248.
https://support.symantec.com/en_US/article.DOC8047.html
In my example I have created a sample consisting of Automation library called autolib2 and process data with fields request_name, request_owner, started_date, request_description, completed_date, process_id and sessionid.
I have built a simple Workflow type of project and imported my custom dll into it (CustomOrmType2.dll).
Automation library has been uploaded to the Process Manager, followed by IISreset and now I can set up automation rules for my process.
The first one we will try is a Process Event and we need to send our process to another Workflow.
Our other Workflow is called DoSomeThingProject and it is supposed to add a Process Message to our ticket.
In order to pass the ticket data to this workflow, we need to make sure our automation library and Symantec.Workflow.RulesEngine.dll are both added to this project.
Also we need to pass in the Input Data variable. It has to be precisely as indicated in the screenshot: RulesetArguments as a name and ArgumentsWithProfile type selected from the automation library dll.
Note that our 'Add Process Message' component will use the variables from the configured Input Data:
After that we will get our DoSomethingProject published to IIS.
I have a set up OnRequestCreated ruleset and an automation rule for my ticket to be sent to DoSomethingProject:
Now we need to add a Generated Run Ruleset Component in our ticket process. It will be placed right after the ‘Insert or Update Sym Request’ component. The component will be configured with my ruleset selected from the dropdown list.
Now we go ahead and publish our ticket workflow to IIS as well.
As this is a raw test and I’m not using any web forms to create a ticket I will invoke my ticket web service manually from the web service url http://localhost/SymRequestManagement/MyService.asmx> Execute > Invoke.
This generates a ticket and my rule is successfully executed along with it:
The next ruleset we will try is an EmailNotificationSent Data Event and we will send our ticket to another process called DoAnythingProject.
Again, this project requires both automation library and Symantec.Workflow.RulesEngine.dll to be added.
For Input Data it needs to use RulesetArguments and EmailNotificationSentArgumentsWithProfile as a type.
The project itself is very simple and only uses a log entry component.
It should write an error level entry to the logs “I am a DoAnythingProject and I have just been started.”
We will go ahead and publish this project to IIS and configure another automation rule.
Also I’ll set up a basic email template to use for this event:
In my existing ticket I will click Send Email link and send email from this template.
We see that our rule was executed successfully and the log entry appears in the logs as expected.
