0
Completed

Suggested Features for EvB 3

Daniel Walters 7 years ago • updated by anonymous 4 years ago 13

After using EvB 3 at DET a little bit I have a few suggestions.

The Operation Lists page can get really messy. It would be great if we could sort the operations and/or group them by Management Agent. Or even being able to re-order the list differently to the order they were entered.

When configuring operation lists it would be good if there was a label that showed where you are. For example something up the top that says Operation Lists > AD_Incoming > schedule. It might just be me but copying config from a list in another doc I kept getting lost.

The Exclusion Groups being defined with operation lists make it impossible to run delta import checks on everything all the time with no exclusion then if something is imported to run a delta sync as a trigger (because for the delta sync to be a trigger it has to be in an operation list by itself and then there's no check operation to kick it off.) So it would be good to either have individual operations within in an operation list to have their own exclusion status or alternatively a check operation for Pending Imports similar to the check operation for pending exports would also work.


SQL Server Execute.bmp

Hey Daniel,

Thanks for these. Regarding the first suggestion, you should be able to currently use Groups for only displaying specific operation lists. The autoconfiguration wizard adds each management agent as a group when it creates its operations. Or are you talking about grouping within the larger list also?

Yeah, I'm talking about displaying within the larger list. I just realised it makes no sense to sort by management agent because an operation list can have operations for many MAs. Maybe if we could sort it alphabetically or order them manually.

Craig's just showed me how to use groups properly so my first suggestion is redundant.

Something that would make it even better (let me be lazier) would be an export readable config or quickview page where you can see all the operation lists and everything they're doing in one page. It would make it easier for me to double-check what's in there.

Another thing I've found, it would be nice if there was some further description of operations like SQL Server Execute. I uploaded an example of where there are two and the order is significant. I don't know which is which unless I click into them.

It would be cool if as well as the current schedule functionality to have an option to save schedules so that if you have a bunch of operation lists that run on the same schedule you could just select a saved schedule and maybe change the start time to offset them so they don't all run at the same time.

This is only very minor, when I'm double-checking config I use crtl-f in Event Broker using IE to make sure I haven't added anything extra etc. For some reason the highlighting from ctrl-f quickly disappears. I don't know if this is something to do with Event Broker or IE settings or what it is but it would be easier if the highlighting didn't disappear.

This unclosed issue has no priority. Please specify a priority.

I can't edit this issue anymore. Happy for it to be set as trivial or minor.

Several of these have been catered for in the latest release, but can you break them down and list the ones that are still relevent

The Operation Lists page can get really messy. It would be great if we could sort the operations and/or group them by Management Agent. Or even being able to re-order the list differently to the order they were entered.

The auto-configuration page groups Operation Lists, but doesn't display them. There is an issue (EB-544) to get this functionality.

When configuring operation lists it would be good if there was a label that showed where you are. For example something up the top that says Operation Lists > AD_Incoming > schedule. It might just be me but copying config from a list in another doc I kept getting lost.

The sitemap achieves this now.

The Exclusion Groups being defined with operation lists make it impossible to run delta import checks on everything all the time with no exclusion then if something is imported to run a delta sync as a trigger (because for the delta sync to be a trigger it has to be in an operation list by itself and then there's no check operation to kick it off.) So it would be good to either have individual operations within in an operation list to have their own exclusion status or alternatively a check operation for Pending Imports similar to the check operation for pending exports would also work.

Interesting and worth looking at, created issue EB-634.

Something that would make it even better (let me be lazier) would be an export readable config or quickview page where you can see all the operation lists and everything they're doing in one page. It would make it easier for me to double-check what's in there.

Another thing I've found, it would be nice if there was some further description of operations like SQL Server Execute. I uploaded an example of where there are two and the order is significant. I don't know which is which unless I click into them.

Operations have display names now, so it will be possible to customize the tree to describe the series of operations.

It would be cool if as well as the current schedule functionality to have an option to save schedules so that if you have a bunch of operation lists that run on the same schedule you could just select a saved schedule and maybe change the start time to offset them so they don't all run at the same time.

This will be handled with the introduction of a shared schedule engine in UFCORE-60.

This is only very minor, when I'm double-checking config I use crtl-f in Event Broker using IE to make sure I haven't added anything extra etc. For some reason the highlighting from ctrl-f quickly disappears. I don't know if this is something to do with Event Broker or IE settings or what it is but it would be easier if the highlighting didn't disappear.

This is to do with our refresh script which may be updated at a later date, won't fix at this particular issue until that's updated.

See comments for specific details, issues broken up where necessary (EB-634) and others duplicated/won't fix or already fixed.

Thanks.