Hi all!
Discovery 4.0.4 (O10) was last published back on 30 November 2018 and is the most recent version.
It now includes the extension module "CryptoAPI.xif" which is part of the application "CryptoAPI".
Previous Discovery 4.0.2 (O10), marked under development, was dependent on the application CryptoAPI because of that module extension.
When now I try to automatically update Discover 4.0.2 to 4.0.4 through Service Studio, it indicates that is not safe and I need to force the install.
I think that it would be better that Discovery would still depend on the CrytpoAPI instead of including itself the module extension "CryptoAPI,xif".
What does the development team of Discovery, the Architecture Team, thinks about this suggestion?
--Tiago Bernardo
Hi Rebecca,
I've come across this situation. This is what we did.
Deleted the Crypto extension. Installed the new Crypto Application available on the Forge and only then installed the new version of Discovery.
Hope this helps.
Hi,Same problem here now. CryptoAPI also have some changes so would be nice if that reference was set or that the CryptoAPI modules was cloned and got another name. But not as it is now.Kind regards,Evert
Hi!
I agree with the comments above.
This is "forcing"* us to move Discovery to environments that don't need it and discovery is very expensive on AOs.
* I do know that we can move it out by ourselves but next time we use the new OS 11 Dev. Studio upgrade option to upgrade Discovery it will put it back under this application. I do also know that we can use "Deploy Custom" to just deploy the extension part of the "Discovery" application but it will be simpler if we just leave it on its own application like it was before.
Regards,
Ricardo
This is solved in version 5.0.6 (OS11) and 4.0.6 (OS10)
I am upgrade to the latest version of 10 in preparation for our upgrade. In the notes it says that the reference to CrypoAPI was removed ... it doesn't seem to be the case. Which version of Crypto API is required?
Rebecca Hall wrote:
Hi Rebeca,
This was done on the latest version for OutSytems 10/11 (Version 4/.0.6 and 5.0.6).
The problematic version was 4.0.4, that brought both CryptoApi as SSUsers (taht is not needed anymore.
If you instaled version 4.0.4, what I recommend is that you first update the CryptoApi from forge and then update Discovery. This way you will have the modules (CryptoApi and Discovery) on the right applications.
Hope it helps
When installing a new version that does NOT include anymore the module "SSUsers" from a previous version where that module was included, the module does not get deleted.
See this my new post: https://www.outsystems.com/forums/discussion/57050/discovery-5-0-7-o11-does-not-include-ssusers-but-it-does-not-get-deleted/
David Pereira Cruz wrote: