In my queue view, I have a global option set which is against a incident entity.
When I include it in my view, it appends the column name with a suffix "(object)".
This is happening for other option sets as well. Is there a way to remove this suffix?
Unfortunately this is product limitation. The view column names cannot be renamed, it will load from display name of attributes and for associated entity attributes extra text will be appended within () either entity name or object.
This could be an enhancement like discussed here.
You can only change column titles by unsupported means. To do so, you would do the following:
Open the view editor, select any column and choose 'Change Properties'
Add a new Web Resource .js file containing basic jQuery code to select the relevant column header and change its text
Set the Function Name in the column properties window equal to the function created in your .js file
Example code based on your scenario:
function changeColumnText() {
$(document).ready(function () {
$("label:contains('Source')").text('Source');
});
}
Related
I have a controller that implements Backend\Behaviors\FormController and Backend\Behaviors\ListController. I'm able to update or delete selected records from the list (delete by clicking the delete button and update by double click), however, I can't find a way to add preview link to the list and I can't find that mentioned in the documentation.
I'm able to preview any records if I enter the preview link manually in the URL bar. e.g.
http://my-project.dev/administration-backend/walid/my-plugin/model/preview/1
I just want to add the above preview link next to each record in the list.
Based on the comments above, the only way to do it is by list partials:
You should define custom list column, quoting OctoberCMS documentation:
Partial
partial - renders a partial, the path value can refer to a partial
view file otherwise the column name is used as the partial name.
Inside the partial these variables are available: $value is the
default cell value, $record is the model used for the cell and $column
is the configured class object Backend\Classes\ListColumn.
content:
type: partial
path: ~/plugins/acme/blog/models/comments/_content_column.htm
I am in a report page in APEX. I went to the report attributes page and inside that are columns which each have their own column attributes. I needed to know how to use the value of one column while I am in a separate column's attribute page. With the picture attached, I try to do above using #COLUMNNAME# to get the value, but the correct value is not being used. You use hashtags to reference column values in the column formatting section.
Javascript/Dynamic Action:
$('.dis_flag:contains(disabled="true")').parents('td[headers="DIS"]').siblings('td[headers="PHONE"]').children('input:text').attr('disabled', true);
where:
DIS - alias of my column, indicating disable editing or no (if disable it contains value disabled="true". But it can have any another value).
dis_flag - class name, i added for this column in "Column Formatting" -> "CSS Class". I added this class to refer this value more easy.
PHONE - alias of column, that must be disabled.
You can add this javascript code to the
"Page Load" Dynamic Action
"Page Attributes" -> "JavaScript" -> "Execute when Page Loads".
Report template. Making your own report template is more difficult, and hard to explain in two words. Just go to the templates list, find report template named Two Column Portlet, type Named Column (row template) and maybe you will understand what i mean.
When defining the properties of a custom control in the "Property Definition" section, you can choose as "Type" in the "Property" tab the option of "extraColumn" and "iconColumn".
How should this type be used ?
Both iconColumn and extraColumn relate to the corresponding tags of the dataView control. You would typically use these when your custom control contains a dataView and you wish to allow an outside control to pass in details about the columns to be used in the dataView.
When a data view is used in a standard XPage, the extraColumns appear as actual columns. The summaryColumn is the first column and shows as a link.
However, in a mobile application, extra columns show up as additional lines of data in the mobile data row. The summaryColumn value shows as "header" in the data row, while the extraColumn values show underneath that value.
<xe:dataView id="dataView1" pageName="#contactDetails" collapsibleDetail="true">
<xe:this.data>
<xp:dominoView var="view1" viewName="TeamDirectoryNameLU">
</xp:dominoView>
</xe:this.data>
<xe:this.summaryColumn>
<xe:viewSummaryColumn columnName="Name"></xe:viewSummaryColumn>
</xe:this.summaryColumn>
<xe:this.extraColumns>
<xe:viewExtraColumn columnName="Office" style="font-size:12pt"></xe:viewExtraColumn>
<xe:viewExtraColumn columnName="OfficePhone" style="font-size:12pt"></xe:viewExtraColumn>
<xe:viewExtraColumn columnName="Email" style="font-size:12pt"></xe:viewExtraColumn>
</xe:this.extraColumns>
</xe:dataView>
One row of that might display as:
Ian Kennedy
London Office
44-22-830-6000
ian.kennedy#company.co.uk
I've already created a custom module that overrides the sales/order/view/tab/info.phtml layout file and creates a new field in the sales_flat_order table. Now I need figure out how to add a text input field to the order page:
The save button doesn't necessarily need to be right near the custom field and the field doesn't need to necessarily appear right where I put it in the graphic. Bottom line is, the administrator needs to be able to edit my new custom field in the admin.
What is the best way to do that?
Look at Comments History block
implementation - class Mage_Adminhtml_Block_Sales_Order_View_History, its template \app\design\adminhtml\default\default\template\sales\order\view\history.phtml and Mage_Adminhtml_Sales_OrderController::addCommentAction(). You should create similar block class with similar template and create controller with action which will save form data to your db field.
The default value for the first item in a drop down list is the name of the database field. I need to change it to a more user friendly name. How do I change the value?
add a HTML Item onto the prompt page and add the following as an HTML item:
Example:
<script>
document.formWarpRequest._oLstChoicesMyList[0].text = '--SELECT A CITY--';
</script>
Replace 'MyList' with the name of the component.
from: link text
In Cognos 10, you can specify prompt text of your choice in Report Studio.
Select the value prompt
In Properties pane, under 'Prompt Text' section, the 'Header Text' property will be set to Automatic. Click the ellipsis button next to it and Header Text Dialogue opens.
Select 'Specified Text' choice. Click ellipsis.
Provide the text of your choice and click ok.
Run the report and you will see text that you provided will appear as first item in the drop down list.
I have provided a Screen shot for a better understanding.
You have a couple of options. First, you can rename the data item's name from database field name to a more friendly name in the Framework Manager metadata.
Second, you can rename the item in Report Studio. However, if you do this you will notice that it is still using the database name. You actually need to perform a calculation in the item expression for it to use your name instead of the default name. So say you are pulling in the string field [Namespace].[Unfriendly Name] and you named your report data item "Friendly Name." The top selection will still read "Unfriendly Name." However, if you replace the data item with the following:
[Namespace].[Unfriendly Name] || ''
It will see that there is a calculation involved and use your friendly name. In the case of a number field you have to add zero instead of concatenating ''.
This is also the case with report column headers (which you can replace with text instead of using this calculation method).
Convoluted? Yes.
Within the dataitem in the query.. you could do a ..
IF ( [dataitemA] = 'some text' ) THEN
( 'new text' )
ELSE
( [dataitemA] )
i try to avoid using javascript and html items becuase they dont generally work in pdf or excel outputs.
just a thought..
cheers!