To delete an application from a process app even if it is referenced by a relational field in an existing application, you need to delete the primary table from the Tables tab in the SBM System Administrator. Be careful when doing this as it is permanent and will delete all parts of the application including existing items. You will then need to perform a Get From Application Engine for the process app in the Deployments tab of your environment in your Application Repository to pull the process app with only the remaining application back into the repository.
This article is to describe how to manually remove a Mashup Composer install from a Windows OS when the uninstall is failing to do so. After following the steps below the machine should be completely clean of Mashup Composer and should allow for a new install.
System DSNs that use the "Oracle for SBM" driver cannot be deleted after SBM is uninstalled. To work around this issue, delete all DSNs that use the “Oracle for SBM" driver before you uninstall SBM. If you have already uninstalled SBM and you still need to delete a DSN that uses this driver, you must delete the DSN from the registry. The Mashup 2009 DSN can be found here:
HKEY_CURRENT_USER\Software\Serena\Studio\Common\Launch The list of items that start with "RecentApplicationX" are the apps that have recently been opened. Delete the "RecentApplicationX" entries for the ones you don't want to show in the list anymore.
A disabled user is typically a temporary status, but may be expanded to be used where preservation of field selections is desired. A disabled user has TS_STATUS of 2 in the TS_USERS table. See the MicroFocus Community for a sample User Management process app .
(5) When (4) is published then the TKP_KP_PUBLISHED is updated and the associated attached duplicated and the original created in (3) is deleted (whether it has been changed or not).
Delete the temporary template file that was created in step 1G above. To update the template: REMEMBER: Templates cannot be deployed or published, but you can check in/out new versions.
From this point foward, you can continue developing this process app as you normally would. If you wish, you can go back to the repository and delete the particular version of the Process App that had problems so you don't end up opening it or accidentally redeploy it in the future.
1. Open Release Package process app in Composer (if not already open) 2. Import the new extensions from Serena Central and do the following in Composer: i. You will need to delete "Request Collection Widget" extension and add the new version