This is an action that users can use to get helpful diagnostic information for support people such as database title & server & file path & replica ID, user name & access level & roles, and current view and/or form and/or field. We find it extremely helpful in cases where the user might not know the programatic name of the current view/form/field, and it also saves the time of going database-properties and scanning the various tabs for useful information.
Code
First you need a form, I called it UserInfo. It will be used in a dialog box. Here are the fields you need - all of them computed when composed (I set these up in a table):
UserName
@Name( [Abreviate]; @UserName );
AccessLevel
AccessLevel := @Subset( @UserAccess( @DbName ); 1 );
@If( AccessLevel = "1"; "Depositor";
AccessLevel = "2"; "Reader";
AccessLevel = "3"; "Author";
AccessLevel = "4"; "Editor";
AccessLevel = "5"; "Designer";
AccessLevel = "6"; "Manager";
"" )
Roles
@UserRoles
DatabaseTitle
@DbTitle
Server
@Name( [Abbreviate]; @Subset( @DbName; 1 ) )
FilePath
To continue reading for free, register below or login
To read more you must become a member of SearchDomino.com
@Subset( @DbName; -1 )
Then 4 computed for display fields (values set in calling action described below):
Have hide-whens on the current <element> fields to hide them if empty.
Also have a hidden SaveOptions field with a value of 0 to stop the form from being saved.
Here is the agent that composes this document:
Now try it out in different areas of a database. If you have a view open, it tells you the name of the view. If you have a document open, it tells you the form, and if the document is in edit mode, it tells you which field you are on. An interesting one to try is a view with a preview pane - it tells you the view name and the form of the currently selected document! Have fun.
If I win the CD Player, next month I'll post how to add a problem description section to the form and link it to a discussion database with a post button ;-) Wish me luck!
Whoops, one thing I almost forgot. The form needs a 'Close' button on it with this formula:
@Command( [FileCloseWindow] )
I have the dialog window called so that it doesn't have an OK or Cancel button, so you might be stuck if you tried it without this button to replace them.
