I want to make a list of shared components that are not used by the application. Is it possible to do in oracle apex?
I also want to create a report of all the places where a particular component is used
It's specific for component, but you need to look for Utilization.
For example:
App Builder > Your Application > Utilities > Application Dashboard
For specific LOV you have Usage on the right pane of Details.
For Authorization Scheme there is tab Utilization.
Same for Templates > Utilization > References > clickable numbers of items.
Related
I have Sales database which contains sales data along with manager IDs, I have created the required reports in Qliksense and want to use Qliksense reports on custom UI (on an app).Also want to apply row level security so that one manager would be able to see only his data and other data would be restricted for him.
How to publish these reports on custom UI and provide data security using Qliksense Desktop or cloud?
PS - I do not have enterprise version yet.
The easiest way would be to go the dev hub and copy the iframe / embed script from there. It is under the single configurator menu item
The standard desktop version will not allow for row level security in any way you must have a license to do that. But once licensed that security will flow naturally to the iframe / embedded object
I have setup Elasticsearch and Kibana 7.0.1 version. May I know how to hide or remove the Management menu from Kibana UI?
As mentioned in this other thread, you can leverage the dashboard-only mode if you want to hide everything but dashboards.
Otherwise, since Kibana 7.2, you can go to Management > Spaces and decide to hide some Management features, such as:
Advanced settings
Index patterns management
Saved objects management
Also worth noting that there's an open issue to actually hide features based on cluster privileges.
The configuration of Kibana UI is received in the response to the /{SPACE_URI}?api/core/capabilities request. You can manipulate this response by putting Kibana behind a proxy (mitmproxy is a quick/clean choice) and within the response set body['navLinks']['kibana:management'] = False. Then you won't see that management button on the sidebar anymore.
After searching forever in Kibana 7.7.1, finally found that you can define what roles to include in the "Dashboard Only" mode under Advanced Settings. Here you can define a second role to have dashboard only, AND NOT access to all spaces as the kibana_dashboard_only_user does.
Advanced Settings --> Dashboard
You can hide the management menu by clicking the Collapse button at the bottom of the menu.
Collapse UI
I'm not so sure about removing it. Probably there is a more contextually appropriate solution for your concern, such as embedding a dashboard onto your app, or restricting management permissions to a certain group of users.
dashboard-only-mode may be of interest to you, and you can move up to minor version 7.1.0 in order to make this a free feature.
In SonarQube portal, it is possible to customize the columns for the Components List view. However, doing this affects all projects and views.
Is there a way to customize only a specific project?
Nope.
Note that you might be able to get what you're after with a saved Measures filter with the correct column set displayed in the Measure Filter as List widget on a dashboard. If you make that dashboard public, then it will show up the same for all projects, but you will have gotten the columns you want while leaving the Components view alone.
I have a question to Magnolia CMS (integrated with Spring) users.
I have to write e-shop integrated with CMS where we can divide all pages into two categories:
Edited and added by admin
static pages like user account settings, shopping cart etc.
First ones, must be totally customizable by admin - I mean, admin must be able to create his own template, add text areas or graphics/video whenever he wants. He also must be able ( this is very important) to create new products which must be also stored in db to be accessible for the application code ( to fill the products list by myself in the code or to set the prices on the static admin pages).
So user can add as many products as he would like, create separate template for some of them and I have to be able to search for this products in db ( for example when user try to use search criteria). The search panel must be created by me - but where admin will place it is up to him.
The second type of pages are static pages done in JSP and I do not expect to change it using CMS.
As the second type of pages is of course not a problem, I do not know what CMS solution I should use for first type of pages.
I thought about Magnolia CMS, but as I can see all templates must be created by programmer in the code.
Also I'm not sure if it's possible to implement mechanism to maintain products ( inside the e-shop) - from one hand admin must be able to add templates for them in CMS, but I must be able to access them from the code ( to maintain them at shopping cart, make invoice etc). The product prices are set from admin panel ( static pages) as well- not from CMS of course. Maybe I can add any single product at the static pages ( insert it into the db) and somehow connect CMS page with it ?
I also need to add that main page template must be designed by HTML designer, so perhaps it would be plain HTML and this main template would be updated due to the admin needs in CMS.
Cloud anybody please advice me the best CMS solution where I can achieve all this ?
Best Regards
I've seen fair number of shops implemented that way with Magnolia where you use spring & web flow to manage a shopping cart and checkout process, while letting editors to create & customise products & categories & promos available in the shop.
You can also get similar (w/o spring) integration just by installing shop module of Magnolia. It's product and product category management might come in handy even if you were to replace checkout by your own.
To answer the other questions and stipulations
you can write your templates in ftl and models in groovy and have those hosted inside of the repository, thus giving access to them to editor and allowing her to change whatever needs to be changed. However there is also danger in that since templates are responsible for generating html, editor might be able to break html layout by making changes directly to the templates. While you want editor to create new products and modify existing ones, Magnolia lets you separate template of products from the content of products so you can let editor to edit just all the fields that you deem editable for given product without having her to ever access html or ftl directly.
as you mention, html will come from designer, so what you pbly want is to take that html, break it into functional blocks that repeat in multiple pages, save it as ftl templates and replace sample text in there with FM tags to retrieve such data from Magnolia. Actually, even better, download the STK static prototype and hand it over to your graphic designer. Tell her to create design by changing css/js/images only, but not to change structure of the html itself in the prototype, then you can truly just drop in css/js/img provided back to you by the designer.
regarding static pages - you can always serve them from Magnolia even if you don't expect anyone to ever edit them (since it usually happens sooner or later that someone wants to edit them) or you can simply configure bypass for the url for such pages and have Magnolia ignore them so they can be served by underlying application server container
to bring in Spring based application, you might consider looking in more details at and using Magnolia's Blossom module which will in turn let you annotate your spring controllers to be treated as Magnolia templates to make integration even more simple.
HTH, Jan
I have a Magento site with one domain, one store and a store view for each language. I need to add a mobile version of the site and have that in all the languages.
If I add another store for the mobile version then store views for each language, I land up duplicating all the languages in the admin area.
The only solution I can see is to have 2 instances of Magento. One with all the store structures (acting front end – install A) and one with all the product (acting backend – install B)
Install A would have two stores and all languages per store and install B would have one store and store views for each language so we only manage each language once.
We would then need to connect these two Magento instances using the API (xml with SOAP). This way we manage each language once and the front end can have as many variations of that language as we like.
Does this look like a workable solution or is there a simpler way to achieve this functionality?
You don't need 2 magento versions.
Magento supports different themes on the same store view for different devices.
All you need to to is to configure a different theme.
For this go to: System->Configuration->Design, select each store view from the top left selector, or Default config if you want to use the same theme for all languages.
In the Theme section you can click on the Add Exception button under the field you need changed (most probably all that support exceptions) and fill in the following.
Matched Expression - iPhone|iPod|BlackBerry|Palm|Googlebot-Mobile|Mobile|mobile|mobi|Windows Mobile|Safari Mobile|Android|Opera Mini
Value - The name of your mobile theme.