In version 1.4 the Bookmark functionality expanded in a big way. Could you only create a bookmark for the entire application in the previous version. Now you have all kinds of bookmark types that can do different things. I’ll gloss over the bookmark types and talk a little about how they work. Then I will try to imagine some scenario’s how you can use the bookmarks as an integrated part of an application.
Along the way I will describe what I do like and what I think would be even better for the future.
Getting to know your bookmarks.
First off all it is good to know that now there are three types of bookmarks you can utilize in your application:
- Standard Bookmarks
The standard bookmarks are the ones you already know from the previous version and can create a bookmark for the entire application. - Fragment Bookmarks
Fragment bookmarks are there for when you want to allow the user to save the state of a part of your application. You will offer the ability to save all the components state within a container component (for example a PANEL component). - Portable Fragment Bookmarks
These kind of bookmarks are the same as Fragment bookmarks, but can do something extra. They can be exchanged between application. For now this is only for the bookmarks that you saved yourself.
Each of these can be used in an application. Also you can create a mix of bookmark types where you provide the ability to save parts and the whole application.
Each type of bookmark has methods to save, list, load, delete or share a bookmark.
Note that you cannot share a combination of fragments. The only way to do that is to use portable fragments and combine them by dragging them to a split cell component. Additionally you can create multiple bookmarks of the same elements in a different state and drag those into a split cell component.
Working with bookmarks
I could give some script and examples but karol.kalisz already did that so I advise you to have a look at these two blogs:
Design Studio 1.4: Online Composition Scenario (basics)
Design Studio 1.4: Portable Fragment Bookmarks & Reuse in Applications
Scenario’s to use Bookmarks
More Advanced Personalization
In contrast to Personalization you can create multiple bookmarks, you can store them in a list and choose a bookmark. You can create an bookmark icon on the right top menu that shows the list when clicked. For example when you’re working with a complex CRM application where you can set multiple filters to create a subselection of customers. A bookmark list like this will be very helpful :
You even can use a standard bookmark that will load automatically as a personalization option :
var x = Bookmark.getAllBookmarks();
x.forEach(function(element, index) {
if (element.text =="starter") {
Bookmark.loadBookmark(element.id);
}
});
Lumira like working for analysts
What If I created an application where in the first screen I have a crosstab (using the analytic template), use the data in a second screen where I have all kinds of Graphical options via script and collecting the visualizations I like in a third screen.
This is a scenario not unlike the Lumira way of working with data preparation, visualize and share. You can use Fragment bookmarks to save results in stage and stage 2. Additionally you can create portable bookmarks for the visualizations you like and add them to the third screen. The Split Cell component is within a PANEL component and that again can be fragment bookmarked. With share bookmark or print application you have the share function.
Self-service Dashboards
Continuing on the first scenario I can create my own visualizations and collect the ones I like in an application. This way I can create my own application. Especially If you a have something in place like the second scenario I described you have a powerful self-service dashboard available for your users.
Especially if you want to offer dashboards to a large group that wants different things this can be the way to go. Mind though that the users have to have some knowledge about what they’re using.
Additionally you have to make sure that the base foundation of your data model is solid enough that it can handle all kinds of users creating diverse scenario’s.
What bookmarks can’t do
Although the bookmarks are already very broad, there are some things they can’t do.
Split cell
At the moment the split cell component is a container without many properties or methods. I would have liked some options to create a layout like you already can with the grid component. Off course you can create the same with first the grid cell and adding split cells in each cell. So it’s a minor thing.
Additionally I would expect some script options that I can click on a fragment in the fragment gallery and use the clicked fragment to add automatically to a split cell by script.
Create Portable bookmarks for others
This is the only major thing that I would like. Especially in the self-service dashboard scenario I can imagine creating 50 tiles (each with a different KPI filter) and offering those fragments to a group of managers. Each manager can pick a selection from those 50 to create their own dashboard. But to do that they have to get access to my bookmarks or that I can save these bookmarks centrally. If you have something like that you probably want some authorization in place id addition to filtering by group
Tweatbeam for portable fragments?
I shouldn't even mention this as it's firmly in the area of fantasy. But wouldn't it be fun to be able to create a tweatbeam like presentation of your fragments?
Often you see public screens with dashboards. I could imagine a collection of visualizations and comments that would present themselves in this way. :
'#SAPDesignStudio' Twitter Wall - TweetBeam
Conclusion
All in all the bookmarks expanded enormously and you can do a lot of things now. I hope they will add the ability to make the portable bookmarks to others soon. But for now there are a lot of fun scenario’s you can imagine with the current state of affairs.
- SAP Managed Tags:
