| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 2214.1 | Same experience with other customers | BERN01::GMUER | | Wed Jan 29 1992 04:18 | 8 |
| The points 4), 6), 7), 8) of Dominique's note .0 are DECmcc "evergreens"
which are claimed by nearly every (potential) customer here in Switzerland.
Solving this little but nice things would make the selling of DECmcc easier.
The improvement of the functions and the user interface in T1.2.4 is great !!
Please keep this way and we will have happy customers.
Edgar
|
| 2214.2 | thanks | TOOK::MATTHEWS | | Fri Jan 31 1992 09:55 | 26 |
| Yes, the comments/suggestions are well received by us. In most cases
we were aware of the limitations in the implementations but due
to resource limitations they had to be made. Yes, there will
be future improvements for many of your suggestions. I can't
commit to when but we understand the points you are making.
You will find several improvements in V1.2 which are not documented.
These were things we did not originally commit to, but we felt
very concerned about. We experimented and found ways to make them
work. Unfortunately, there was not time to change the documentation.
I have been in the field myself and have been frustrated about
how long it takes to get changes made and into the field when
I knew I could make changes in a few days. I am now in engineering
and understand the other side of the issues. Getting a new manual
through the production phase is no trivial matter. Changing a source
file takes hours. Checking it against delivered code takes a few
days. Getting a thousand manuals printed takes 2 months. The
printers insist on planning their production runs.
Please be patient with us, we hear your comments and are trying
to respond. Check the ability to launch a new application from the
new iconic map. We heard and responded to a need. It may not be
totally correct yet.
|
| 2214.3 | some notif functions not in 1.2 EFT kit | TOOK::CALLANDER | MCC = My Constant Companion | Fri Jan 31 1992 10:46 | 29 |
| just some updates on the status of some of these requests.
The "beep" on a rule firing has been such a hot button, we have
added it in. This will be user controllable to the extent that
they can turn it on and off. they will not (in V1.2) be able
to change the volume level.
The user will have the ability to bring up the notification graph, or
notification window and keep them active (individually or in tandem)
so as to be notified of new occurrences regardless of weather the map
is centered on the entity in question (the 1.2 EFT kit allows this
one now).
We also noted a major limitation in notification logging. This one has
always been planned, but we ran out of time before field test. This
function is now operational in our internal baselevel kit (not yet
available to the general DEC public). This will allow you to log in
either brief or "detail"ed format all events you have requested from
the PM with the NOTIFY command. You will also be able to put limits
on how much data in each file before a new version is started (like
start a new version every 1000 events), as well as how many versions
should be kept (auto purging of old files) so you don't run out of
memory.
Hope these help. I know they aren't everything that you are looking for
but they were the ones my team could do.
jill
|
| 2214.4 | More details on what actually ended up going into V1.2 | TOOK::DMCLURE | Just Say Notification Services | Tue Feb 04 1992 10:25 | 49 |
| re: New Notification Logging and/or Customization Features...
> We also noted a major limitation in notification logging. This one has
> always been planned, but we ran out of time before field test. This
> function is now operational in our internal baselevel kit (not yet
> available to the general DEC public). This will allow you to log in
> either brief or "detail"ed format all events you have requested from
> the PM with the NOTIFY command...
Actually, we added three different log formats (as opposed to two).
The three logging formats are "Full", "Brief", and "Brief Plus Alarm Data."
The default logging format is "Brief Plus Alarm Data." The various logging
controls can be customized via a new Notification Logging Customization
window (not to be confused with the General Notification Customization
window). The two new Notification customization windows (along with the
save and restore menu options) will control the following things:
1. General Notification Customization:
* _<y/n>_ Open Notification Window on Startup
* Maximum Notifications _<#>_
* Notify Requests Startup File __<filename>__
* _<y/n>_ Bottom Row Buttons
* _<y/n>_ Notifications Bell
* Ok, Apply, Cancel.
2. Notification Logging Customization:
* Default Log File __<filename>__
* _<y/n>_ Logging enabled at Startup
* _<y/n>_ Create New Versions When Logfiles are Opened
* _<y/n>_ New Version of Logfile Every _<#>_ Hours
* _<y/n>_ Purge Old Logfiles When Creating New Versions
* Keep last _<#>_ Versions When Purging
* Logging Format: {"Brief Plus Alarm Data", "Brief", "Full"}
* [move to] Logging Status and Controls [window]
* Ok, Apply, Cancel.
3. Use Last Saved Settings
* Reads resources from a file named MCC_NOTIFICATION_RESOURCE.DAT in
the current directory (if it exists) and combines with both default
system, as well as display resource data.
4. Use System Defaults
* Resets using only default system and display resource data.
5. Save Current Settings
* Write new version of MCC_NOTIFICATION_RESOURCE.DAT file using
currently applied resource data.
-davo
|