Deprecation Analysis of
Dear SAP Cloud Application Studio Developer,
you might got recently an email titled “Deprecation analysis of” <your add-on>.
The deprecation check behind the email was executed for all productive tenants. With this check the syntax check of the SAP Cloud Applications Studio in regards to deprecation messages was made visible – also for add-ons which havn´t been touched for a while.
As you might know the deprecation mechanism of the public solution model is in place to enable SAP to continue with new -potentially incompatible- developments and to set the old entities to deprecated – indicating that they should not be used anymore and if possible their usage should get replaced.
New features might be only supported for the new objects created. So whenever possible a replacement of the usage of deprecated objects makes sense.
However the analysis of the productive tenants has shown that not all issues indicated by the syntax check are really places requiring a replacement. In most cases the old functionality continues to run – because the Developers have built everything in a compatible way, supporting also the old entities. For example datatypes cannot be replaced in a add-on – they will be always supported in the future.
(In the email was Mewritten: “It is recommended to replace this usages with the suggested alternative.” – not immediate action required.)
In most cases you find more information about the deprecation in the online help.
It is intended to provide here some more information about frequently asked questions.
The email was send out on the 25th May it will be send out again three weeks later (should be 15th of June). After this it will be sent out only once per release. The email text will be in the future more like “For your Information”.
Update as of 06.07.2016
As more requests come in I see that three things cause confusion:
1. The report had a small bug with big effect in: if in a tenant are multiple addons – the deprecations of addon 1 were also listed in addon 2 … and so on.
Programmers know what the cause is: forgot to clear a variable in the next iteration. However for every entry the full path is listed – so it is easy to identify to which addon the line belongs to and ignore the others.
2. My assumption was wrong that the Studio syntax check shows the same messages – so that they can be displayed again by every AddOn responsible in the studio. It turned out that this assumption was wrong. I don´t know what mode I was in when I got the messages in the Studio – but I was not able to see the messages in the Studio in my recent tries.
3. Some Messages address situations which cannot be resolved. Exchange of a Datatype for example or to remove something which is not possible because the solution is assembled.
Considering all this at the moment the email can only be rated as a hint. For some situations it might be useful to replace some usage of a standard object by a newer one. Generally it cannot be expected from Cloud Studio developers that these places are changed – unless the studio does not throw this as error messages too.
So I am a bit sorry having caused confusion with this service. However from SAP side we have now visibilty on the various deprecation cases what we did not have before. So we will try to improve the email in order to point out only real valuable information in the future.
As already mentioned above there is no urgent action required.