Hi there AppWorks fans,
Welcome to a new installment of AppWorks tips.
For this week, a quick hack! During a lunch-walk we were brainstorming what should the best way to remove the user inbox from the runtime!? We already tried the solution from this post, but it comes with an “after-taste”! In our case we still want to have the benefits of running entity lifecycle activities and BPM activities which fails in the solution of that post! So, can we do a nicer task on removing the inbox task? Yes, we can…
Let get right into it…
Remember the post from last week? The one where we played with icons on layout-tabs. We introduced you to the advanced tab of a ‘Theme’ document and in the end we pasted an interesting CSS part of content!
Now, watch this CSS-hack in that same ‘Theme’ document:
1 | div[aria-label="My Inbox"] { |
That’s an inbox removal, but what about this one…Removing the hamburger menu:
1 | bs-image-button[click-event-name="ham-click"] { |
This logo removal option?
1 | div.empower-logo { |
Why not removing the whole header for a minimalistic runtime? 🤠
1 | div.main-header-bar { |
With this header-bar hiding option, we can now implement our own navigation sidebar!? Or whatever navigation you would like to implement to your end-users!
That’s a “DONE”…sometimes things are just too easy for implementation and in this case we can still use our entity lifecycle activities and BPM activities (as the inbox is only hidden from our eye). Now we can also raise that valid question…”What else”? 🤔 I leave this question for you to explore in your own weekend! Have a good one, and I see you in the next post.
FYI: In our project, we introduced our own notification system based on entity modeling!
Don’t forget to subscribe to get updates on the activities happening on this site. Have you noticed the quiz where you find out if you are also “The AppWorks guy”?