As you shrink the size of the screen the page eventually begins to deform, in particular the tab navigation.

Its not a big issuenbut it would be nice if it all scaled down more cleanly. While I havent tested it on a mobile browser, it wouldnt surprise me if the scaling issues I'm seeing on a desktop browser would make the site unusable on a mobile device. It might not be in scope, but if the top menu scaled ok the rest of the site might actually work pretty well on a standard mobile device which could be useful for remote administration.

Seems to be an issue when you drop bellow about 640px, which means its not an issue for desktops. As noted I havent actually tested on any mobile devices.

Commit operations serve no purpose when there is no check/listen operation of the corresponding type.

As such, the available operations in the tree should at least be filtered to match the selected check or listen operations.

This raises questions about the viability of the commit operation as an operation altogether, namely:

An operation consists of a name (not particular useful for a commit), retry wait (it'll never fail), retry count (it'll never fail), and child/next operations for which the use thereof for commit operations is dubious.

It may be worth considering giving an operation list something along the lines of exit conditions, where it could:

DoNothing
CommitChanges

based on whether it Suceeded.

Alternatively, it could just automatically do that behind the scenes.

Either way, this wouldn't break the role of a check operation with regards to the operation list, namely because the operation list already knows about and works with it's check operation directly.

A useful feature as suggested by Bob would be for the Powershell script to not only register the workflow, but also to add some default MPRs for data and rule changes. These MPRs could then have the configured workflow added, without needing to modify any existing MPRs.

Currently the time it takes to search through the logs for a recent event feels a little sluggish - with more operation lists / events happening at once it may end up being very difficult to find the details of a particular event.

This could be alleviated by the introduction of search parameters:

e.g. OR / AND / TO-FROM etc.

Additionally, the Logs action should facilitate the search filters in its parameters, such that external pages can redirect to it. This would allow for the following:

e.g. An operation list has run, a little yellow arrow comes up next to the last-run details and it redirects to the log action with the a filter similar to:

<opListGuid> AND <opListName> AND time TO-FROM endtime

Which would adequetly describe the logged details of the run.

I have been running a PowerShell script (attached) without a problem for some time, but now that I have added parameters for the first time I am unable to pass values for these parameters to the script without getting the above error.

The script is attached, and the plug-in parameters are being specified as follows:

Module Path: \\EDMGT051\D$\Scripts\FIM.ScriptBox\FIM Object Visualizer\Reports\DEEWR.Requests.Today.ps1
Script Parameters: -pdb EDMGT053 -pdbinstance FIMSQL

I am following the mouse-over instructions, and have tried all combinations I can think of (including renaming to lower case params, including quotes, using local file path) - all without success.

Assuming others are able to use this OK, can I please have some assistance with this as it will remove the need for the DEEWR admin to edit the scripts when deploying to other environments?

Attempted to add a group via the UI results in the current error. However, following this error, the group is successfully added and appears in the list of current groups:

System.ArgumentException: The parameters dictionary contains a null entry for parameter 'id' of non-nullable type 'System.Guid' for method 'System.Web.Mvc.ActionResult Group(System.Guid)' in 'Unify.EventBroker.Web.GroupController'. An optional parameter must be a reference type, a nullable type, or be declared as an optional parameter.
Parameter name: parameters
at System.Web.Mvc.ActionDescriptor.ExtractParameterFromDictionary(ParameterInfo parameterInfo, IDictionary`2 parameters, MethodInfo methodInfo)
at System.Linq.Enumerable.WhereSelectArrayIterator`2.MoveNext()
at System.Linq.Buffer`1..ctor(IEnumerable`1 source)
at System.Linq.Enumerable.ToArrayTSource(IEnumerable`1 source)
at System.Web.Mvc.ReflectedActionDescriptor.Execute(ControllerContext controllerContext, IDictionary`2 parameters)
at System.Web.Mvc.ControllerActionInvoker.InvokeActionMethod(ControllerContext controllerContext, ActionDescriptor actionDescriptor, IDictionary`2 parameters)
at System.Web.Mvc.ControllerActionInvoker.<>c_DisplayClass15.b_12()
at System.Web.Mvc.ControllerActionInvoker.InvokeActionMethodFilter(IActionFilter filter, ActionExecutingContext preContext, Func`1 continuation)
at System.Web.Mvc.ControllerActionInvoker.InvokeActionMethodWithFilters(ControllerContext controllerContext, IList`1 filters, ActionDescriptor actionDescriptor, IDictionary`2 parameters)
at System.Web.Mvc.ControllerActionInvoker.InvokeAction(ControllerContext controllerContext, String actionName)

• Version number missing.
• 'Event Broker' displayed in Bold should be FIM Event Broker or not there at all (the product name essentially appears twice over two consecutive lines).
• The text 'MVC <templates/>' looks wrong, although it does match the logo on the project page. The project seems to refer to the project as 'MvcTemplates' in its description.
• Shane has mentioned that there are a few other places where branding has been missed, as well as parts of the workflow.

A SQL Server Changes operation is still operating an hour after it has been deleted. To do this,

• I added a SQL Server Changes operation, and set it to retry
• Have the operation fail
• Once the operation has failed, stop the operation list, delete the check operation, add a new check operation, and restart the operation list

The operation continues to operate in the background as if it is still there.

There are some issues configuring the OIM Changes operation:

• The operation displays with the name Unify.EventBroker.PlugIn.OimChanges rather than a display name on the Check Operation
• Validation is not present for the Data Object Type field, and throws a null exception if it is saved with an empty value
• Password is not validated

OIM Commit is fine.

I used the following script to delete rolling log files generated by both a SSIS package as well as the FIM Operations History files ... thereby making sure disk space usage was kept within limits. This would be a useful script to post on the Event Broker wiki as an example usage of the "Execute PowerShell Script" plug-in ... just copy this code:

# Delete all *.log Files in target folder older than 21 day(s)
$Path = "\\MyServerFileShare\Logs\MyApplication"
$Daysback = "-21"
$Extension = "*.log"
 
$CurrentDate = Get-Date
$DatetoDelete = $CurrentDate.AddDays($Daysback)
Get-ChildItem $Path -Include $Extension -Recurse | Where-Object { $_.LastWriteTime -lt $DatetoDelete } | Remove-Item