Dialogue Boxes: Difference between revisions
Developer Hints: Display a dialogue box from a SEM script |
No edit summary |
||
| (11 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
Sysgem Enterprise Manager (SEM) | 'Tips for developers working within the Sysgem Enterprise Manager (SEM) environment'. | ||
---- | |||
''How to display a dialogue box from a SEM script:'' | |||
'''Dialogue Boxes''' | |||
e.g. in a Windows Script (in Perl) | |||
print "\@{{B Banner - Title\n"; | print "\@{{B Banner - Title\n"; | ||
| Line 13: | Line 16: | ||
print "\@{{DI\n"; | print "\@{{DI\n"; | ||
The script above produces the following dialogue box: | |||
[[FILE:DialogueBox.jpg]] | |||
''Information Box:'' | |||
The "\@{{DI\n" in the last line of the script (above) causes the dialogue box to be an information Box. | |||
''Error Box:'' | |||
To display an error box, use the following instead of the last line in the example: | |||
print "\@{{DE\n"; | |||
''Warning Box:'' | |||
To display an warning box, use: | |||
print "\@{{DW\n"; | |||
''Enquiry Box:'' | |||
To display an enquiry box (requesting that the user repliies with a "Yes" or "No"), use: | |||
print "\@{{DQ\n"; | |||
''Note: Special use of the "Enquiry" box:'' | |||
Note that an enquiry box is only really effective if executed from the "(M) Post Processing" script in a Menu option, and then only if there is some other action pending after the post processing script has run. The entire post processing script is run to completion without the script being aware of the reply to the enquiry. If the reply is "No", then any remaining scripts to be run - such as 'Integration Class' scripts will NOT be run, whereas if the reply is "Yes" then all remaining scripts will be actioned. An example for the use of the enquiry box would be a question of whether a user account that has just been created should also be added to the subscriber database (via an 'Integration Class' script). If the answer given is "No" then the Integration Class script to add the subscriber pointer will NOT be run. | |||
'''Other Platforms''' | |||
''On UNIX/Linux:'' | |||
echo "@{{B Banner - Title" | |||
echo "@{{T 1st Line of information for display inside the box" | |||
echo "@{{T " | |||
echo "@{{T Last line of information" | |||
echo "@{{DI" | |||
''On OpenVMS:'' | |||
$ write sys$output "@{{B Banner - Title" | |||
$ write sys$output "@{{T 1st Line of information for display inside the box" | |||
$ write sys$output "@{{T " | |||
$ write sys$output "@{{T Last line of information" | |||
$ write sys$output "@{{DI" | |||
Latest revision as of 09:46, 24 February 2011
'Tips for developers working within the Sysgem Enterprise Manager (SEM) environment'.
How to display a dialogue box from a SEM script:
Dialogue Boxes
e.g. in a Windows Script (in Perl)
print "\@{{B Banner - Title\n";
print "\@{{T 1st Line of information for display inside the box\n";
print "\@{{T \n";
print "\@{{T Last line of information\n";
print "\@{{DI\n";
The script above produces the following dialogue box:
Information Box:
The "\@{{DI\n" in the last line of the script (above) causes the dialogue box to be an information Box.
Error Box:
To display an error box, use the following instead of the last line in the example:
print "\@{{DE\n";
Warning Box:
To display an warning box, use:
print "\@{{DW\n";
Enquiry Box:
To display an enquiry box (requesting that the user repliies with a "Yes" or "No"), use:
print "\@{{DQ\n";
Note: Special use of the "Enquiry" box:
Note that an enquiry box is only really effective if executed from the "(M) Post Processing" script in a Menu option, and then only if there is some other action pending after the post processing script has run. The entire post processing script is run to completion without the script being aware of the reply to the enquiry. If the reply is "No", then any remaining scripts to be run - such as 'Integration Class' scripts will NOT be run, whereas if the reply is "Yes" then all remaining scripts will be actioned. An example for the use of the enquiry box would be a question of whether a user account that has just been created should also be added to the subscriber database (via an 'Integration Class' script). If the answer given is "No" then the Integration Class script to add the subscriber pointer will NOT be run.
Other Platforms
On UNIX/Linux:
echo "@{{B Banner - Title"
echo "@{{T 1st Line of information for display inside the box"
echo "@{{T "
echo "@{{T Last line of information"
echo "@{{DI"
On OpenVMS:
$ write sys$output "@{{B Banner - Title"
$ write sys$output "@{{T 1st Line of information for display inside the box"
$ write sys$output "@{{T "
$ write sys$output "@{{T Last line of information"
$ write sys$output "@{{DI"
