Will you please share your requirement in detail.
Are you able to see adapter event in logs?
Are you able to successfully pass rule?
For run time execution of rule, you need to activate it on GRID. You cannot test working of rule only in Dev Studio.
Actually i wanted to mail all the details of every new Incident raised in remedy .
I have configured adapter , written a rule (screenshot attached) and linked it to process. Activated module in the CDP . Created new incident in Remedy , but nothing is coming up . I am suspecting , its the issue with rule configured.
No i couldnt see the event in logs ( checked grid and process logs)
I am guessing its the issue with the rule . But when I manually given the input in the process , it sent a mail when i executed.
Could you use the integrated AR filter plugin to call the desired workflow directly from the filter instead of using the Remedy Monitor Adapter?
or use the inbuilt Email Engine in AR? What version of AR are you using?
I haven't used it yet . Can we do it via AO.
1 of 1 people found this helpful
The inbuilt Email Engine enables you to send out email notifications and embed content in the email body/message - it is AR function not related to BAO.
Alternatively the filter plugin allows you to run a BAO workflow/process from a filter Set Fields action - you need to set the integration between the AR Server and the BAO Web Services up in the AR System Admin Console prior to be able to see your workflows in the drop-down of the Set Fields action but this is just completing a single form in AR and is straight forward. You can then pass any field(s) from the Incident form (in your case) over to the BAO workflow using the parameters set on the BAO workflow.
If you still want to use the Remedy Monitor Adapter then you will need to process the inputevent from the AR Notification/Alert queue and retrieve the Incident using the Remedy Actor Adapter assuming you pass across the Incident Number in the Alert msg.
If you need any further info on any of the above let me know and I will see what I can dig out.
Meanwhile will be trying out filter plugin which allows to run a BAO workflow/processes .
Can you please let me know if i have configured correctly in the rules (attached screenshot) . Wanted to do using Remedy Monitor Adapter , When i manually gave input in Start and tried executing manually its working fine .
Now I wanted to process the inputevent from the AR Notification/Alert queue and input it to further process...
Can I get all the Incident info if we use Remedy Monitor Adapter and then process what info we need .
Yes you can. But its better to write a filter on HPD:Help Desk form to pass all incident details and invoke BAO workflow.
Could you please point me to correct reference for configuring filters? Once the filters created , how do we invoke workflows from AO.
Hi Rohan ,
Can you confirm whether my configuration is correct in the rules to retrieve , adapter info and New..
1 of 1 people found this helpful
You need to define filters using the Remedy Developer Studio - when defining the filter select the form that will trigger it and the conditions etc. You will need to add a Set Fields action which will call the BAO workflow as per screen shots below:
In the above my BAO config is not conencted - when it is you need to add a Asynchronous workflow using the ADD button on the Process box - this will give u a list from which you select the workflow required. Once selected do the mapping for the BAO input and output parameters (start/stop in BAO terms) using the form fields and/or static text
The configuration for BAO is performed in the Remedy System Admin Console as per screen shots below:
Hope this helps.
the configuration that Adrian is referring to is can be done by performing the configuration in the following thread:
This configuration then becomes available in ARS (from the Set Fields Action) as the data source = BMC Atrium Orchestrator. You then build a Filter to call the exposed process in BAO passing in any Context Items as required.
ARS builds the associated Web Service call in the background so you do not need to do this yourself.
This is actually a more stable way of triggering BAO than using the Monitor Adapter (which is more complex to setup with Rules, etc).
If you are wanting to email details of every new Incident raised, as mentioned you can configure this in ARS as opposed to using BAO.
If you want to use the ARS Monitor adapter, you still need to build the Filter in ARS that pushes a record to the correct form to trigger the rule - so in fact you are doubling up on your work.
I suggest doing a search for information on both, there is a wealth of information available on both method available.
- Configure your Remedy monitor adapter with the server and user details.
- Confirm that the adapter starts up and logs in successfully.
- Add a filter onto the form (HPD:HelpDesk). This filter should send an alert to the user defined above (and subsequently the monitor adapter will generate a grid event).
- When a monitor adapter generates an event, the event XML is checked against all of the rules active on the grid. If you want to see the events, configure the logging as DEBUG of the adapter framework (and possibly adapter as well) for CDP; the events will then be shown in the grid.log.
- When a rule matches against the event, the associated process will be executed with the event passed as a parameter (inputevent).
- In your rule, you have used a condition //text/text() = New this means the alert action created in filter on HPD:HelpDesk should have value New in it's text field. (For a trial, just remove that condition from your rule and go with only first rule)
You can also call AO processes from a filter using SetFields action;
To use this mechanism you have to configure AO ar AR side, for this configuration, refer below doc:
Aryan , its working after i create a filter to alert in Remedy admin console .
Adrian / Carl .. I will be trying using the way you have suggested and update here..