Saving a Function’s Visual Interface |
DEVELOPER |
There are three ways to save a function’s UI after it has been designed or edited:
File | Function | Save menu sequence,
clicking on the toolbar diskette icon, or
exiting a function via the File | Exit menu sequence which asks whether to save or not.
The Save operation within the Forms Designer behaves differently depending on whether you are connected to a host dictionary or working off-line.
When connected to a host dictionary, the function user interface is returned to the currently connected repository. In the second case, the user interface is saved to the drive and directory designated by you in the save dialog window. In the first case the Forms Designer creates a temporary BPSL stream, which is submitted to the Host Services, which updates the currently connected repository.
When working off-line, the Forms Designer saves a BPSL stream, which contains all the objects necessary to describe the user interface and its linkage to the PROIV runtime application framework. BPSL streams saved locally have an extension of *.BPS.
The Forms Designer allows you to retrieve PROIV functions from an application repository, logoff (disconnect) and then work on each function’s user interface off-line.
Since the Form’s Designer doesn't need a repository in this situation, you are free to work on a user interface outside the normal development environment. This feature is extremely valuable for language translation personnel whose primary job is to convert from one language to another and adjust visual screens accordingly without access to function source code. It also permits developers to easily work off-site.
After all cosmetic changes have been made, you may reconnect to the original application repository and save (upload) each function.
Error |
Cause |
Action |
Function: <function name> is not found and can't be saved. |
The function name does not exist in the PROIV environment where the Forms Designer is currently connected. |
Connect the Forms Designer to the PROIV environment where the function exists. |
Function: <function name> is marked as 'production' and can’t be saved. |
The production flag for the function is set. |
Remove the 'production' flag in the Function Security screen. |
Topic ID: 530037