I'm training Watson Discovery through the dashboard however I need more information about user queries, the dashboard only shows the user query text e.g " I want customer care number" or "continue" as shown in the picture, while I want to know more about the user query:
1.The timestamp of the query.
2.Channel that used Watson Discovery e.g Slack, Twitter.
If you want fine grained training in Discovery, you might want to use the APIs. Discovery training interface is basic and doesn't allow to see any custom information or even to give a customised rating score. It takes 0 and 10 by default and you can't change it for the interface.
However you can use the APIs to give any custom training range and also you can extract all the training data that's trained into the service.
Let me also inform that the training data has to be of a certain format JSON. You can mention the NLQ, filter, time, answerId to train for that question etc. I'm not sure you can add a custom field to it like the platform from where that training was given. But you can try giving it and if it works, then both of us would learn something new.
Related
I'm completely new to Qlik Sense and also with the coding syntax used in the data load editor.
I select the Account object from Salesforce through the connector and I select the fields Account ID, Country and LastActivityDate. Then I was surprised I could not filter that object by, for example, Country = Netherlands.
Now, I tried to do something in the sense of: WHERE Country__c="Netherlands", but of course it's not as easy as that.
I need to implement these filters:
Country__c = Netherlands
LastActivityDate is from 1st of May and beyond
Hate to be vague but these links should be of help.
Filtering data from data connectors :
But Qlik disclaims that the ability to filter is not available for all connectors.
https://help.qlik.com/en-US/sense/September2018/Subsystems/Hub/Content/Sense_Hub/LoadData/Filter-data.htm
If all else fails, load everything and make use of this little tool. Be weary of getting dependent on it.
http://tools.qlikblog.at/SetAnalysisWizard/QlikView-SetAnalysis_Wizard_and_Generator.aspx?sa=
I have many end users for my reports. Some of them want to look at all website data, some just section A, some section B, etc. For my own sanity and not having to create the same report over and over with different filters, I'm wondering if there's either:
A way to provide a link to a report where the link tells data studio what filter to apply to the report
A way to filter the report based on the user who's logging in.
I have the impression that neither of these is possible, and it seems like people are reluctant to have one dashboard that they have to proactively filter for their section (I'm still going to try that). But I'm hoping that there's perhaps something I didn't know about.
This is possible using Custom bookmark links (doc). The Drill down table example (doc) shows how you can create a table with records linking to a second page of the dashboard with different filters. You could use this to create filter pre-sets for different users groups.
This is currently not possible.
After I had great pleasure with the simple implementation of filters in the admin-on-rest List View, I would now like to have a similar view, which does not show the individual posts in a table or as cards but aggregated statistics related to the filter.
For example: Filter all users by male gender. The statistics should then be based on the men, e. g. a histogram with an age distribution.
Is it possible to modify a Custom Iterator in this way? If not, how can I achieve my goal? Can someone give me a jump-start?
You could indeed use a Custom Iterator, however you'll only receive a page of resources which may not be ideal to generate statistics.
If you want statistics on all the data targeted by the filters, you have two options:
declare a new resource for statistics allowing the same filters and generate the statistic on server side. Then, use a Custom Iterator to display them nicely
create a custom route for statistics and do what you would do in a classic React app without using aor
I need to apply a filter in some report for some users.
I was told that the best way to do this is a security filter but i discovered that security filters are applied to all the reports that the user open.
I need some kind o filter that filter an attribute on a user but just on some reports, not all.
example:
if report1{
if user1 then attribute = 1
if user2 then attribute = 2
}
let's say i have departments and chiefs of those departments.
It is not a matter of security but a matter of comfort.
I want to avoid the chief of a department to manually select (prompt) his department.
It would be more comfortable if the system would recognize the user and show the data of his interest.
There a different ways to solve this kind of scenario, depending on the level of flexibility you want to offer to your user and the effort you need to implement and maintain the solution.
The User Login way
No flexibility, low maintenance, more effort to implement
Use the User Login prompt. This is a system prompt (created by default MicroStrategy) that returns the user login. If you have a table with the data that a user can see like this:
UserLogin YourAttribute
user1 attribute1
user2 attribute2
user3 attribute3
... ...
You can create an attribute UserLogin to be parent of the Attribute you want to use as filter and then create a filter (User Login = User Login System prompt)that you will put in your report.
More detailed information can be found here.
Once implemented this solution will you need to maintain that new table and when the user run a report with that filter it will be able to see only his data. It's similar to a security filter, but now you can decide where to apply the filter.
Multiple reports for multiple prompt defaults
Flexibility, high maintenance, little effort to implement
For each user create a copy of that report with the proper answer as default.
Maybe you can create ten reports now, but if you need to modify that report tomorrow you will need to modify ten report or recreate again all copies with different prompt answers.
Anyway this is good for the users, because they can change the prompt answers if they need.
Using URL to answer prompts
Flexibility, low maintenance, variable effort to implement
Instead to run the report using MicroStrategy you can provide to each user a specific URL that, using MicroStrategy URLAPI, answer automatically the prompt.
Of course you need to prepare the URLs in advance or find a way to do it programmatically. This is a good solution if the user don't want to navigate the MicroStrategy web interface but just run the report.
Subscribe the prompt answers
Flexibility, low maintenance, medium effort to implement
Have the report with the proper prompt answer delivered to your user every morning (or when you want). Using MicroStrategy Distribution Services you can deliver a report or document to your user and for each user you can specify the correct prompt answers.
No user can receive the full report in their mail box or just a link to their history link, opening that link they will see the report with their data. Of course users (or probably you) will need to setup all the subscriptions required.
Final thoughts
In these case I prefer to leave flexibility to users and teach them how to use the product. Of course there are some people they have no time for this kind of things (usually C something levels), in that case the best this is to have the data delivered to their email.
I understand some of these options are not that straight forward to implement if you are new to MicroStrategy.
My suggestion: for now go with the subscriptions (if you can) or teach your users how to save their own copy of that report (in My Reports) with the prompt already answered (oh, yes, this was another option, but each user has to do it), every time they will open it now, the prompt won't show up (but if you change the original report they will need to do it again).
Let me know if you need more details.
Hi Sitepoint wizard people,
Say we have an admin application that has multiple users and various objects. What I'd like to do is control access within the object itself - that is, it will behave one way for one type of user, and another way for other users. For example...
Director Mike can override Reception user Sally's registration date. One would assume that Mike could set any date both in the past or in the future. Then we have Payroll user Steve who can also modify Sally's registration date, but only for dates in the past up until (for example) one year ago. To spice things up, then we have the HR Manager Mary who can also amend Sally's registration date, but only for dates from precisely 23rd June 2007 up until one month from now...
How can I program the access restrictions so that on the front end, the form control is restricted with a min and max date, and in the backend, the validator checks the entered date to make sure it falls between those dates? I'd obviously need to be able to tweak the min and max dates for each user type. Other objects might have different parameters - maximum amount on a discount field or days of the week for overtime, for example.
I've asked this question in different ways, but each time I get bogged down by the implementation. I'm currently developing it as a php/MySQL web-based application, but thoughts and comments from other platforms very welcome! This time I'm looking at first principles, so it doesn't matter what your background is, if you have any ideas, please let me know! What do you even call this type of access control...?
Depending of how you application is based, you could ask for credentials at the start of the application and depending on who is requiring access, you could load a different xml file containing different settings.
As for security issue, make sure that the different xml files can't be reached by the users.
Edit:
Since you are using MySQL you could do something like this.
Let's say you have a table of users that has those fields : UserId, UserName, RestrictionId.
And with a Restriction table that looks like : RestrictionId, FieldName, FieldCondition.
This way, in your php app, when a user is authenticated, you can go fetch the correct "Restrictions" on the field and apply them in your code. If it happens that you have multiple fields that require different rules then you can simply add them with the correct RestrictionId.
This DB design is far from perfect, I'm pretty sure you can do better
Since, you are already using MySql db. You can maintain the UserRole Master table details in DB itself. Load the user role data based on login, then you can easily validate the changes made by the user accordingly.