Technology Blogs by Members
Explore a vibrant mix of technical expertise, industry insights, and tech buzz in member blogs covering SAP products, technology, and events. Get in the mix!
Showing results for 
Search instead for 
Did you mean: 
Active Contributor

If you have upgraded to Lumira Designer 2.0, please go here


Now that Design Studio 1.6 is available, karol.kalisz and I have taken strides to port over our existing SCN Design Studio SDK Development Community components to the new 1.6 SDK patterns that reiner.hille-doering has mentioned here: What's New in Design Studio 1.6 SDK

I previously mentioned some changes in a blog post here (Sneak Peak - SCN Design Studio 1.6 SDK Components), however I am creating an SCN Document this time so that others can modify this document going forward to keep everything up to date.


Why 3.0?  At certain points along the way, we've had to make the decision to commit future development to a newer version of Design Studio that means no further support for older versions.  With Design Studio 1.6, many new features along with SDK changes to support the new sap.m mode mean that we must make a clean break.  This means that Design Studio 1.6 is a pre-requisite for anything related to our 3.0 components, just like for our 2.0 components, 1.4 was required.  You can still download the older 1.0 and 2.0 components from GitHub.


Download Links


Version Required Design Studio Version
Download Link
1.0 Design Studio 1.2 or higher Download
2.0 Design Studio 1.4 or higher Download
3.0 Design Studio 1.6 (Works mostly in Lumira Designer 2.0) Stable | Preview
[NEW] Lumira Designer 2.0 SP2 READ HERE

Source Code

Source Code can be found on GitHub here:


GitHub - org-scn-design-studio-community/sdkpackage: SDK Package of SCN Design Studio Community


Community Components Blog List/Timeline


From most recent to oldest, here is a collection of all blogs by the SCN Design Studio SDK Community team in reverse-chronological order, with certain milestones called out.  You should note that the further back in time you delve, the more primitive, and in same case, irrelevant, some of the older components may be, hence calling out the dates.  Nevertheless, those wishing to see what is possible, or to get source code examples, need look no further than these blog posts written by the SCN SDK Community.





Component Library & Documentation


We can offer the overview of all components and documentation on functions.

     You can find it here Component List 3.0 - SCN Design Studio Community

Besides the list of components, you can find also "Download" link and instructions how to install. It is better for you to use the ZIP installation (direct links provided above) as this allows you to store the installed ZIP locally. But, github is also having versionized ZIPs - in case your copy is lost.

What Has Changed?

We've made all attempts to not disrupt any existing components or properties so your transition to 3.0 shouldn't be too bumpy.


Simplified Categories


In order to try to save a little space and keep things tidy, we now have only 4 categories:


  • SCN Community BasicsThese are meant for simple interactive/selector-type components.

  • SCN Community VisualizationsThese are meant for components that visualize data, either with a graphic or tabular output.

  • SCN Community PrototypesThis is a catch-all category for either proof-of-concept or ideas that are not fully baked, as well as deprecated components that we aren't ready to discard quite yet.  Basically this is the 'wild west', proceed with more caution here.

  • SCN Community UtilsThis category is for components that at their time, had no need to be on the canvas, however due to SDK limitations technically had to exist there when really their purpose was more for scripting and debug utility.  In today's world with 1.6, these ideally would become 'Technical Components' but in short-term, we've preserved them where they are today, perhaps some day we can remove this category and refactor them to true 'Technical Components' and free up even more space.


M Mode Support


With 1.6, SAP has offered up a more official support for UI5 sap.m components.  As a result, existing SCN Community components that are based on sap.m will be supported first in 'M' mode, and for a time being in 'Classic' mode.  As we see M mode mature hopefully in future versions, people will make the switch to 'M' mode for their apps.  You will also see new SCN Community components that we not possible in 'Classic' mode before (without ugly hacks) become available now only in 'M' mode (such as Switch and Slider and more.)


Streamlined Additional Properties Sheet (APS)

Nearly all components, no matter what category or original author, now support an easy to use APS that generates itself.  This means consistent UI for designers, and less time spent by developers in the community to implement, as the APS generation code really takes care of it all for you.  A separate technical document for community developers (old and new) will be posted with the details.

Component Quality


We have made many important internal code re-factorings using the RequireJS module pattern which has been an opportunity for us to make a few bug fixes along the way, as well as streamline some old code.  There may be some initial bumps in the road early on with 3.0, but a goal is to re-visit existing components and FIX either bugs or incomplete features in order to make this a more reliable and appealing package for the community.




In the past, SCN comments have provided one channel to report bugs or ask for features or provides general feedback and ask questions.  For general feedback and questions, please provide them here on SCN as always, but we'd encourage you to post actual feature requests and bugs on GitHub as an issue so that they can be tracked and not lost in the sea of comments.  This helps you and the SCN developer community.  The place to do this is here:


Issues · org-scn-design-studio-community/sdkpackage · GitHub


Going forward look for additional new components and more reliable existing components!

Labels in this area