Community collaboration: We need your help! Creating a How-To Compilation :)

[Jens-Limbach]

Hi all,

I created just today a new document where I would love to gather all how-to knowledge that we have in this awesome community! The community is getting bigger and we have already so much know-how here!

Many people make the effort in composing how-to's and posting them here, those can be found via the search but how to find them when you don't know what to search?

First I thought, that I would browse myself through all of them and compose them in one thread. But this would be very hard to maintain and a lot of effort... Then I had a better idea: Let's do it together! :smile:

I defined a few standardized tags, if everyone uses those in his future how-to's and add them to his previous how-to's we can easiely compile a great collection of topic related how-to's!

Here is the document with the How-To's: How-To Collection for SAP Cloud Applications Studio

What can you do?

Please add a tag from my list to every of your how-to's! If you want a new category that I have missed please post a comment to the how-to collection!

Current List of Tags:

cloudstudio_howto_usecase

cloudstudio_howto_extensibility

cloudstudio_howto_ui

cloudstudio_howto_integration

cloudstudio_howto_coding

cloudstudio_howto_analytics

cloudstudio_howto_other

How can I change my tags most efficiently?

There is no need to edit your complete content, it is much easier to just "edit" the tags only at the bottom of each of your posts:

How will it look like?

Your content will appear in the collection automatically by adding this tag. So if people go to the compilation and click the link or click the link in any of the available tag clouds, they will also see your content.

Currently there is only mine, but I hope that will change very soon...

Example for UI Topic: http://scn.sap.com/community/business-bydesign/studio/blog/tags#/?tags=cloudstudio_howto_ui

Let's go! :smile:

I hope that a few of our experts start with that so that we can reach a critical mass and hopefully in the future everybody will follow :smile:

alessandro.iannacci, thomas.schneider judson.wickham3 marianne.macgregor srivatsava.janaswamy2 vinodkumar.kommineni horst.schaudestefankrauth rei.kasai ralf.baumann tim.chang sunilkumar.maurya andreas.eissmann2 sven.feurer chris.bai, ginger.gatling , sathianarayanan.hari

I am sure I forgot people to mention please forgive me :smile:

Probably we will add the How-To collection to the sticky posts soon.

Cheers,
Jens

[Former Member]

Good initiative.

[Former Member]

Yes very good idea!

[Jens-Limbach]

I corrected the usecase tag ("-" was not supported...) and also the link of to the UI tutorial in the main article :smile:

[vinodkumar_kommineni]

As you said in the blog we could see an exponential growth in this forum from past few months.This would be really helpful for everyone getting into the Cloud world :smile:

[vinodkumar_kommineni]

Hi Jens,

I just saw that I can add tags to any blog document. Which means one does not needs to be the owner of the blog document to really do the tagging. So its more easy :smile:

I meant even if owner is not able to do this for any reason we can do this!!

Regards

Vinod

[Ticg]

Great idea, Jens ! 

[Former Member]

Hi Vinod,

Please suggest how can we add left pane and right pane(Multiple Panes/Multiple Views) in single FACET , Do we need to create mutiple custom BO's or single custom BO is enough.    Is it feasible requirement to place mutilple panes/views in a single FACET. Is it possible with Node concept. Please suggest.

Thanks in advance.

Tim

[dhruv_mehta]

Any one have an Idea regarding Exception Handling in ABSL?

[HorstSchaude]

Not possible as of today :sad:

[Former Member]

Yes. The UI and BO configuration is extremely flexible... sometimes too flexible which brings you into trouble from a performance point of view if you decide to overload the UI with too much data, but that is a different topic to discuss later.

But at a high level, you can create a UI for a standard or custom BO as the "root/anchor" and depending on what data you need to show from other BOs or nodes of the "root/anchor" BO you can create additional UI elements to represent them with the "root/anchor" BO.

So for example, the Account UI has a complex overview of Contacts, Attachments, and Involved Parties. The Contacts is another BO and hence is a SADL query bound to a list UI control of Contacts related to the Account. The Attachments is a node of the Account and is a re-usable UI embedded component of Attachments for the Account, and Involved Parties is a node of the Account and is a list bound directly to the involved parties node of the Account.

[dhruv_mehta]

Hi Horst I hope SAP provide that in future releases :smile:

[former_member190667]

This has been a great resource! Thanks!