I cannot delete a skill from the Skills tab.
The checkboxes to select the skill (pre-existing or added by me) are disabled.
Is it a bug or I am missing something?
Thank you
It's functionality that hasn't been added yet. We are still working on flushing out this UI. For now you will have to use the Swagger UI to do this. Click on the Conversation API link from the Console page and use the DELETE /v2/api/skills/{skillName}
Remove a skill API.
Related
How can I filter the skills list on the Twilio flex team view page? I need to filter the skills based on the worker role. I can detect the role from worker attributes. But how can I filter the skills displaying in team view when clicking on agent name at Twilio flex. I don't want to display all skills, I want to display some of them.
Or, is there any listener that I can use to detect when that panel is opening? In that situation, I can filter the skills view using the DOM selector.
Twilio developer evangelist here.
I don't have a good answer for you, I'm afraid, as that's a bit further into Flex than I've managed to go. However, I have some ideas.
You can listen for a worker to be selected in the supervisor view using the Actions Framework SelectWorkerInSupervisor action (you can listen to beforeSelectWorkerInSupervisor or afterSelectWorkerInSupervisor.
The thing I'm not sure about is how to actually filter the skills. I was looking at this filtering plugin for inspiration but I couldn't quite tell what was going on. I wonder if you can affect the state in redux based on your currently selected worker.
Sorry, this isn't a full answer. Hopefully it gives you some ideas though.
We have a need for our end-users to be able to click a "watch" button or something similar to get update notifications when page contents are updated.
Is there a feature or plugin for this?
Thank you.
There's no built-in mechanism for this, but you could build one by defining a "Subscription" model to keep track of which users are watching a given page, and adding a listener for the page_published signal that sends the notification to those users.
I have this application where users answer a survey and if there are any questions that are mandatory, the submit survey button will not be active (not clickable- grayed out) if they are not answered. Gatling is now passing the test even if the button is not clickable, is there any 'check' method that we can impose to see that the test fails if the button is not clickable? Please help. Thanks!
Gatling is not a browser but a HTTP (amongst other protocols) client, so it doesn't know anything about "clickable". You have to check based on response content.
Co's,
I am a newbie to drupal. I am using Drupal 7,fivestar,userpoints and voting rules modules in my intranet site. I created new rules by using the Rules module to award points to the content author based on the rating ( no of stars etc) provided by the logged in users. This is working fine.
But the problem is , whenever the logged in user clicked the fivestar widget, an event fires and the content author getting points based on the rules defined.
To resolve this, I want to disable the fivestar widget after the logged in user clicked the fivestar widget once.
How can we make it ? Could you please suggest how to achieve this ?
Version details for the modules i am using are below.
Fivestar 7.x-2.0-alpha2
Voting API 7.x-2.6
Userpoints 7.x-1.0
Voting Rules 7.x-1.0-alpha1
Rules 7.x-2.1
You must add a condition to the rule, something like "if user hasn't vote on the content yet". Probably you can achieve this just using the rules interface, otherwise you will have to do a little research on the fivestar api to verify users vote on a specific node.
Hope that helps!
I have an EPiServer project which is using the sequential workflow to validate content changes. This works fine, however we have a slight issue where content reviewers are just clicking Publish when they are happy with an editor's work. What they should be doing is using the workflow task window and indicating their approval through that.
To enforce this behaviour I would like to disable the Publish button in the content editor under certain circumstances (i.e. when there is an outstanding workflow task linked to the current page).
Does anyone have any ideas how I can do this, or even an alternative solution to the problem altogether?
Actually, I think you may want to revisit your workflow logic.
If a user with publishing rights publishes a page: that should be considered an approval. You could easily hook up to the Published event to see if the page is part of a currently running workflow.