I need to set default values for a "Grouped Checkboxes" field.
The Checkbox is using a configured list datasource.
I did set the "Default Value" option as one of the configured list options's key, however I see no default checked option being displayed when trying to create new content.
You can set it by JQuery
$('.GroupedCheckedboxes').prop('checked', true);
It looks like there is a gap there at the moment. I've created an enhancement request to add support for this here:
https://github.com/craftercms/craftercms/issues/2566
In the ticket, I've also provided a small workaround patch you can make to the group checkbox control which will allow you to set default values.
I am not sure if the solution to my enhancement request will be the same as my workaround so you will want to keep an eye on that ticket.
Related
I am setting up Azure DevOps to track Features and other work items. One of the things I want to track is what environment bug was found in.
My preference is to have a list of checkboxes user can check/uncheck.
I have not found any way to do this using default setup or the Marketplace.
Anybody who can help me out?
To use checkboxes, you can try the extension Multivalue control. Follow below steps to do that:
Install the extension Multivalue control
Navigate to the specific inherited process, select the work item
type (Task in this sample). Add a new field （BugType with Text (single line) in this sample, you can also create a picklist field
based on your requirements).
New group (BugType in this sample)
Add a custom control to Task, select the Multivalue control from
the control list.
In Options select the field created in step2, and enter the bug
type you want to set (e.g Dev;Test;Pord). OK to save the
configuration.
Open a Task work item to verify the checkboxes.
You can add a Boolean field:
Then you can use checkboxes:
We have two fields Fix Versions and Affects Version in a bug wherein the drop down values are to be auto populated based on the tags created in Azure Repos. For ex: if there are tags v1.001.560, v1.001.561 etc and for any new tags created, the tag version should appear as a drop down value for these fields. Is there a feasible approach to achieve this? Please suggest.
In short, there is no method to meet your needs now. As a suggestion, you could submit a suggestion ticket to suggest the feature on: https://developercommunity.visualstudio.com/report?space=21&entry=suggestion. That will allow you to directly interact with the appropriate product group, and makes it more convenient for the product group to collect and categorize your suggestions.
DevOps only supports setting to specific values for your custom picklist fields. Please note custom field is used to support tracking data requirements you have that aren't met with the existing set of fields.
Besides, to realize your idea, we should auto populate tag values to the field when opening the work item. However, we also not have such a trigger even though getting the tags with Rest API.
I have created a dashboard in grafana having multiple status panels. I need to provide a dropdown such that when one option is selected all the panels having a name corresponding to the selected option will be filtered. So, basically i need to filter the panels based on their name.Is this possible. If yes, how can we go about it
a bit late for an answer now I suppose but will answer you anyway. You can create filters in Grafana without the need for a plug in through using the Variables feature in your Dashboard settings. Its also used in templating to make your data more dynamic but also crucial in display when you want to filter. Check out the link below
https://grafana.com/docs/grafana/latest/reference/templating/
The way to accomplish something like this is with Grafana's Repeating Rows/Panels feature.
Essentially, this lets you dynamically duplicate a row/panel for all the possible results of a given variable. Then a dashboard user can use the variable selection UI to drill down and only show certain rows or panels. Make sure you allow multi-select and/or All as an option for the variable(s) so that you can see multiple results at a time.
I created a plugin that should upload the contact entity "entityimage" to an external storage.
The code itself should works (it works as a console app), but I am unable to add a step that trigger on "entityimage" change as I can't find it in the filtering attribute list in the Plugin Registration Tool.
Is there a way to trigger this plugin only when "entityimage" change?
Regards,
Dremor
Reviewing the Contact's entityimage field in the Metadata Browser indicates that it is a "Virtual" field, which may be why it is unavailable as a filtering attribute.
Also, according to the SDK there does not appear to be any other message available besides "Update" on the Contact that could be used to indicate that the entityimage has changed.
And, changing the image through the UI does create an Audit History entry, however, it is a generic "Update" entry, with the old value and new value blank.
It appears that triggering a plugin on change of only the entityimage field is not possible, nor do there appear to be any OOB hooks to see if that field has changed.
The only other think I can think to research is Change Tracking. Otherwise it looks like you may have to upload the image on any Update of a Contact.
Or, you could sync the image URL's from CRM to an external system and compare the one in CRM to the external system before uploading.
Strangely enough, if you don't set any filtering attributes the plugin does get triggerd when changing the image, but i guess this also means that all field changes will trigger it.
Is it possible to find out whether the values stored in CRX are from touchui dialog or from classic ui dialog.
I am creating a checkbox for both UIs. When touchui dialog saves value in CRX it saves on but when classic ui saves value, it saves true. which makes it difficult to use value after reading( touch ui does not recognize true and classic ui does not take on).
Please suggest
Not really. Both mechanisms simply make a POST request to the appropiate resource to create/update it. You could add a hidden field to identify it, but I would recommend against this.
Instead, you should properly configure your dialogs so both versions store your properties in the same way.
In the granite version of the checkbox you can configure the value that will be set in the checkbox with the "value" property. (check the docs for more info)