brother_of_karamazov
Legendary Poster
Found this nifty little tip out recently:
You can turn a web version into a windows version.
This can be useful in two ways.
1- If you have both web users and fat client users you can convert a version that a web user created into a windows version and allow your fat client users to run it.
2- If you have spec troubles with a web version you can 'repair' it. If you go into Batch Versions you can select the web version, click Advanced and then Check Out. You can then execute a Check In if you wish to make the version available to fat client users. If your wish is to regenerate and 'repair' the web version you would execute the Check Out on your egen machine and regenerate the version.
We have had several instances where troubleshooting led us to believe that the spec for a web version were corrupted. This conversion method allowed us to regenerate a web version instead of deleting and recreating the version in question.
From Solution ID 200783616:
Versions added on a web client will be deemed web-only versions and these versions will not display and cannot be run on a windows client. Before a version created on the web client can be run on a windows workstation, the version must be converted to a windows version. The following steps must be done to convert a Web only version to a full windows client version
Check-out the version in Object Management Workbench on a fat windows client workstation.
Check-in the version from Object Management Workbench on a fat windows client workstation.
Regenerate that version to run on the HTML client again.
Deploy the version to the server and workstations as needed.
Once a web-only version is converted to a windows version, the version is no longer a web-only version and will be able to be executed from a windows client. However, you will no longer be able to make changes to the data selection and data sequencing from the row exits or delete the version on the HTML client.
You can turn a web version into a windows version.
This can be useful in two ways.
1- If you have both web users and fat client users you can convert a version that a web user created into a windows version and allow your fat client users to run it.
2- If you have spec troubles with a web version you can 'repair' it. If you go into Batch Versions you can select the web version, click Advanced and then Check Out. You can then execute a Check In if you wish to make the version available to fat client users. If your wish is to regenerate and 'repair' the web version you would execute the Check Out on your egen machine and regenerate the version.
We have had several instances where troubleshooting led us to believe that the spec for a web version were corrupted. This conversion method allowed us to regenerate a web version instead of deleting and recreating the version in question.
From Solution ID 200783616:
Versions added on a web client will be deemed web-only versions and these versions will not display and cannot be run on a windows client. Before a version created on the web client can be run on a windows workstation, the version must be converted to a windows version. The following steps must be done to convert a Web only version to a full windows client version
Check-out the version in Object Management Workbench on a fat windows client workstation.
Check-in the version from Object Management Workbench on a fat windows client workstation.
Regenerate that version to run on the HTML client again.
Deploy the version to the server and workstations as needed.
Once a web-only version is converted to a windows version, the version is no longer a web-only version and will be able to be executed from a windows client. However, you will no longer be able to make changes to the data selection and data sequencing from the row exits or delete the version on the HTML client.