I am trying to create proposal for displaying different webpage depending upon user's membership.(e.g. Premium member - access to whole website, Normal member - cannot see certain tabs which are available only to premium members)
So? The programming language that you are using to create those pages would have simple if/else statements; use those to control what is shown to the user.
Related
Suppose I want to write a simple addition program using C/AL in NAV 2016.
How can I dynamically ask user to enter the two numbers?
In Microsoft Dynamics AX we use "dialog" class for this purpose.
I need some code reference or the description to approach such process.
In Dynamics NAV do not have something like Dynamics AX dialog class.
In this case you need create a page with your fields to user complete the info.
Then in other page call this new page to open it and the user can complete de info or add in MenuSuite to access.
Example:
Page 88000 Calculator
Variables
Action and Action code
Page running
Then you can create a menuSuite for this page or write this code in other page to open it
PAGE.RUNMODAL(88000);
You can use
Page object as described in other answer. But to get values from it to calling function you would need to create source table for that page. Or throw some function to it like GetValues.
Use dialog.input. It may be obsolete though.
Use dialog class from windows .net library. Will not work in web client though.
Depending on situation report’s request page might be a good option.
To help you better please describe the requirement you stumbled upon.
In Sitecore, the publishing restrictions access via the dialog are stored under the inherited Publish base template - for example, the Item-level Publishable checkbox is stored under __Never publish.
I had expected to be able to restrict publishing by language, but the fields above are shared between languages so apply to all.
Obviously I could unshare the fields, but I'm not sure what other implications there may be. Has anyone tried this or implemented another solution?
You can restrict the publishing of an item by language, but it is also by version. These are stored in the Lifetime field section, rather than the Publishing section.
This will allow you to mark a specific version in a specific language as unpublishable, however it won't affect all versions in that language.
Other than that, an option would be to add a new field to a base template that is Unversioned, perhaps "Publishable In Language". You could then look into adding a new step into the publishItem pipeline that takes this into account when determining whether a version is to be published - this would possibly take place just after the DetermineAction step, where Sitecore uses its own logic to determine if an item is to be published. Unfortunately that class isn't easily overridable and uses private methods, so it's not a great candidate for extension itself.
I am trying to do some reporting on page views on a site and the results are being listed like the following:
www.example.com/directory/ - 100 views
www.example.com/directory/?id=123456 - 10 views
www.example.com/directory/?id=987654 - 5 views
What filter do I need to create to views the results as:
www.example.com/directory/ - 100 views
www.example.com/directory/?id=* - 15 views
Thanks in advance
Yes, getting historical grouped together is going to mean using something like Google Docs, Excel, Tableau Software, Analytics Canvas, etc.
Moving forward...
One of the simplest ways of keeping things grouped in GA is to set up an advanced profile filter. You'll want to use this with a new profile; keeping a "raw" or "empty" profile is highly advisable for when you actually want to look at those individual URLs.
That said, here's a filter pattern that should work for you:
Go to Admin > Filters (under the View Column)
+ New Filter > Create new Filter > Name it
Filter Type = Custom filter > Advanced
Here's the pattern:
Field A: www\.example\.com\/directory\/\?id=.+
Output To: www\.example\.com\/directory\/\?id=\*
Another way to aggregate the same URI with multiple query strings is to change the primary dimension to 'Page Title' under Behavior > Site Content > All Pages.
The best way to do this for your historical data is unfortunately in an excel pivot table. You can get in in the UI, but only by creating a custom report and searching for very specific directories.
Check out the documentation on excluding query strings in your GA profile. Maybe create a new profile and write an advanced rule to rewrite all "id" pages to "/directory/product-page".
A totally different approach is to use custom variables or custom dimensions and to stop looking in the normal "Behavior" reports section (used to be called "Content" in GA) – custom dims are available using Google Analytics Universal Analytics only, which means starting a new web property and possibly running both code snippets concurrently (totally safe to do).
Personally I find custom dimensions a bit easier to work with than custom variables, and I generally think that it's a good idea to start exploring the new Google Analytics.
The nice thing about either of these approaches is that you can still keep the full page path date in the same profile as your custom dimension / variables information; it'll stay in the Behavior section where it belongs with all the other page paths.
Where I'm going with this...
You can create a new dimension such as "page type" and then call it "products", "posts", "articles", or whatever these id #s represent in this /directory/; then you can look at metrics across the dimension like pageviews, time on page, etc. by page type.
You can even create other dimensions to help describe them in more detail, such as breaking down blog posts or products into their different categories; i.e. hierarchical dimensions. Once you start using this kind of thing you may wonder what you ever did without it!
I think it's fair that I stop this answer now since it's not about how to set up custom variables or custom dimensions; those links should get you started (it's really not difficult).
Note: You can use php to fill in the dimension information in the GA tracking snippet dynamically based on the page that is being viewed (again, that's another question).
As a user experience requirement, I need to create a dynamic dashlet.
According to what I need, a dynamic dashlet would be a special dashlet that can load inside "almost every content". I say almost every content because of course this kind of dashlet would have its own limits of course. At the same time, it would be nice that the dynamic dashlet has the ability of being maximized, what in fact would show the real content (for example, an Alfresco page).
Perhaps my question is ambiguous, but the intention to give the user the chance of check execute common functionality inside that special dashlet, this way the user doesn't have to leave the dashboard improving the user experience as a consequence.
Did anybody have had such requirement or similar before? Would that be possible to do?
I would like to know some tips and suggestions in order to find out the right approach.
Thanks in advance.
You could try re-using the webview Dashlet which can also show another page.
The only problem is that not every part which is visible in Share can be accessed via url. Sure the template gets build up by regions of *.ftl's but that doesn't mean you can 'just' view the *.ftl.
The only 'dynamic' thing I see is making a custom page template which shows one or couple of regions which are dynamically build by the url.
e.g. pointing to share/page/customPage?region1=documentlibrary should insert the documentlibrary template within that page and thus it can be shown within the iFrame of the webview Dashlet.
Actually the documentlibrary is a bad example, because there is already a portletMode available for Liferay. But hopefully you'll get my point.
I have several similar interactive reports. I want to have some kind of a template to which all reports will adhere. For example each report need to have a button and it's tedious to add button to each new report. If I want to change something in common part of all reports, I will need to go through all reports and apply changes that is difficult.
There isn't an ideal solution for you, but here are some things you can do to make creating new reports easier:
When creating a new Interactive Report (IR) region in an application, you could start by copying an existing IR in the same application. This gives you the option to copy any associated items and buttons at the same time.
You can create a "template" page (I normally call it a "skeleton" page to avoid confusion with the concept of Apex templates) with a typical set of components: IR region, standard buttons, items, processes. To create a new report, create a new page as a copy of the skeleton page and then modify it as required.
Neither of these deal with your second problem: if at a later date you decide that all IR regions should have a new "Foo" button, you are going to have to change each one individually. You could consider an approach using the Apex Builder APIs to generate such buttons, but if you did that (I have in the past) you wouldn't be supported by Oracle!