使用文本模式编辑视图

您可以使用文本模式编辑列表或报表中的视图,以访问标准界面中不可用的字段并创建更复杂的视图。

访问要求

展开以查看本文中各项功能的访问要求。

您必须具有以下权限才能执行本文中的步骤:

table 0-row-2 1-row-2 2-row-2 3-row-2 layout-auto html-authored no-header
Adobe Workfront计划* 任何
Adobe Workfront许可证*

新增:标准

当前:计划

访问级别配置*

编辑对筛选器、视图、分组的访问权限

编辑对报告、功能板和日历的访问权限以编辑报告中的报告元素

对象权限

管理对报告的权限以编辑报告中的视图

管理视图的权限以编辑它

*要了解您拥有什么计划、许可证类型或访问权限,请与Workfront管理员联系。
有关访问要求的详细信息,请参阅Workfront文档中的访问要求

先决条件

在报表或列表中开始使用文本模式之前,请始终确保您熟悉Workfront文本模式语法。

有关更多信息,请参阅:

在视图中编辑文本模式

使用文本模式编辑视图对于报告和列表是相同的。 从报表或列表访问视图的方式有所不同。

TIP
我们建议您在标准模式下构建尽可能多的视图,然后将其转换为文本模式以进行编辑。

有关生成视图的信息,请参阅Adobe Workfront中的视图概述

有关创建报告的信息,请参阅创建自定义报告

  1. 执行下列操作之一:

    1. 要从报表访问视图,请转到报表,然后单击​ 报表操作 > 编辑 > 列(视图) ​选项卡。

    2. 要从列表中访问该视图,请转到该列表,然后从​ 视图 ​下拉菜单中,将鼠标悬停在要修改的视图上,然后单击​ 编辑 ​图标

      此时将打开视图生成器。

  2. 在视图中选择一列。

    选择Report Builder的​ 列(视图) ​选项卡,然后选择一个列。

    note tip
    TIP
    要使用文本模式编辑视图,必须一次编辑一列。
  3. 单击生成器右上角的​ 切换到文本模式,然后单击​ 编辑文本模式

    note note
    NOTE
    在文本模式下编辑列时,Workfront会将textmode=true行代码添加到该列。 这表示在文本模式下修改了该列。

    下表概述了文本模式视图中的关键行:

    valuefield=</cod>

    table 0-row-2 1-row-1 2-row-0 3-row-0 4-row-0 5-row-0 6-row-0 7-row-0 8-row-0 9-row-0 10-row-0 11-row-0 12-row-0 13-row-1 14-row-2 15-row-2 16-row-2 17-row-2 18-row-2 19-row-2 20-row-2 21-row-2 22-row-2 23-row-2 24-row-2 25-row-2 layout-auto
    示例行 描述

    This is the name of the object or of the field as it appears in the database. For more information about how objects and fields appear in the database, see API Explorer.

    The following scenarios exist:

    code language-none
     <li value="1"> <p> If the name of the field you display is a phrase instead of a single noun, you must use camel case syntax for the <code>valuefield</code>. For example, for the Planned Start Date of a task the code is: </p> <p class="example" data-mc-autonum="<b>Example: </b>"><span class="autonumber"><span><b>Example: </b></span></span><code>valuefield=plannedStartDate</code> </p> </li>
     <li value="2"> <p>If you want to display a custom field, the <code>valuefield</code> value is the actual name of the field, as you see it in the interface. For example, for a custom field named "More information", the code is:</p> <p class="example" data-mc-autonum="<b>Example: </b>"><span class="autonumber"><span><b>Example: </b></span></span><code>valuefield=More information</code> </p> </li>
     <li value="3"> <p>If you want to display objects that are related to other objects in a view using the <code>valuefield</code> line of code the object names and attributes are separated by colons. </p> <p>For example, a column in a task view that would display the name of the Portfolio Owner has the following value for the valuefield line:</p> <p class="example" data-mc-autonum="<b>Example: </b>"><span class="autonumber"><span><b>Example: </b></span></span><code>valuefield=project:portfolio:owner:name</code> </p> <p>This indicates that from the object of the report (task), you can access the next related object (project), from there, you can access the following related object from project (portfolio), then the portfolio owner (owner) and then their name (name). </p> </li>
    </ol> <p>For information about how objects connect to one another, see the section <a href="https://experienceleague.adobe.com/workfront-basics/navigate-workfront/workfront-navigation/understand-objects.html?lang=zh-Hans#understanding-interdependency-and-hierarchy-of-objects" class="MCXref xref">Interdependency and hierarchy of objects</a> in <a href="https://experienceleague.adobe.com/workfront-basics/navigate-workfront/workfront-navigation/understand-objects.html?lang=zh-Hans" class="MCXref xref">Understand objects in Adobe Workfront</a>.</p> <p>Note: If you choose a field in text mode that is not valid in the standard interface, you are not able to switch back to the standard interface within the column.</p> </td>
    
    valueformat=

    This line represents the format used to display the valuefield. The valueformat identifies whether an object or field displays as text, number, percentage, or date.

    We recommend using HTML for your valueformat, especially when using valueexpression, to ensure the most accurate display of your information.

    For information about additional values for this line, see Use conditional formatting in Text Mode.

    valueexpression=

    You can add this line to replace valuefield, if you want to display a calculated field in the column.

    You must enclose the valuefield of the objects in curly brackets every time you use it in a valueexpression.

    The following scenarios exist:

    code language-none
     <li value="1"> <p>If you want to display a field in a column in upper case, you would use:</p> <p class="example" data-mc-autonum="<b>Example: </b>"><span class="autonumber"><span><b>Example: </b></span></span><code>valueexpression=UPPER({valuefield})</code> </p> <p>The <code>valuefield</code> of the object is spelled as it appears in the API Explorer. </p> </li>
     <li value="2">If you want to add multiple <code>valuefields</code> by stringing them together, you must separate them by a period.</li>
     <li value="3"> <p>For example, if you want to display the name of the Primary Assignee of a task using <code>valueexpression</code>, you would use:</p> <p class="example" data-mc-autonum="<b>Example: </b>"><span class="autonumber"><span><b>Example: </b></span></span><code>valueexpreesion={assignedTo}.{name}</code> </p> </li>
     <li value="4"> <p>If you want to use a custom field in a <code>valueexpression</code> line you must precede the name of the field by <code>DE:</code> to indicate that it is a custom field. The name of the field is spelled as it appears in the interface. </p> <p>Important: When you use a custom field that is placed in a custom form section that has restricted permissions for some users, the calculation of the valueexpression is blank when those users view this calculation in a report. For information about adjusting permissions on custom form sections, see <span help/quicksilver/administration-and-setup/customize-workfront/create-manage-custom-forms/form-designer/design-a-form/design-a-form.md"><a href="https://experienceleague.adobe.com/docs/workfront/quicksilver/administration-and-setup/customize-workfront/create-manage-custom-forms/form-designer/design-a-form/design-a-form.html?lang=zh-Hans">Create a custom form</a></span>.</p> <p>For example, if you have a custom field labeled "Developer Name" and you want to display this field in upper case in a column, you can use the following <code>valueexpression</code> to indicate this:</p> <p class="example" data-mc-autonum="<b>Example: </b>"><span class="autonumber"><span><b>Example: </b></span></span><code>valueexpression=UPPER({DE:Developer Name}</code>) </p> <p>When referencing a Typeahead type custom field, use the following expression to reference the name of the object selected in a field labeled "Developer Name":</p> <p><code>valueexpression=UPPER({DE:Developer Name:name})</code> </p> </li>
    </ol> </td>
    
    descriptionkey= / description=

    This line defines the text of a tool tip as you mouse over the name of the column. In this case it is using a key to translate the name value in the description text. If you want to modify the description, change this line to read:

    Example: description=Your Value.

    namekey= / name=

    This line defines the column label. In this case it is using the abbreviated value based on the key.

    If you want to modify the column name you can change this value to:

    Example: name=Your Value

    Name allows you to enter any text for the column name, whilenamekey requires you enter a key that is used to translate the name of a column.

    To change the column name you can also add the displayname line, if one is not present.

    displayname =

    You can add the following line to change the name of a column, which suspends the namekey/name value:

    Example: displayname=Your Value

    querysort= This line defines how the results are sorted when the column header is clicked. If it is not present then the column cannot be sorted after the report is run.
    width=

    This line represents the number of pixels that are used for the column. If the line is omitted or set to 0 (zero) then the column does not appear in the view.

    When you modify this field manually in text mode, you must also add the usewidths=true value to your column.

    usewidths=true You must use this line in addition to the width= line when customizing the width of a column.
    makeFieldEditable= This line defines whether the value displayed in a column is inline editable or not. If this line equals true, the value in the column is inline editable. If this line equals false, the value in the column is not inline editable.
    link.valuefield=

    Insert this line only when you want the value displayed in a column to link to the object associated with it. The link opens the details page of the object. This value should match the valuefield= line. When you insert this, you must also add the link.valueformat= line.

    For example, you can insert link.valuefield=priority in an issue view, and the Priority of the issue displays as a link. Clicking this link opens the Issue page.

    link.valueformat=

    Insert this line only when you have inserted the link.valuefield line to add a link to the value in a column. The link opens the details page of the object. This value should match the valueformat= line and indicates the format used to display the valuefield.

    Important: When viewing the text mode in a built-in column that also includes a link, you notice a number of lines referring to the link. Some of those lines might no longer be supported or are unnecessary when you create your own custom column in text mode and add the link statements to it. The lines that are mandatory when adding a linked value are link.valuefield and link.valueformat.

    aggregator.function=

    This refers to how the values of each column are summarized. There are multiple lines that start with aggregator. and they all refer to the aggregator that summarizes the results of the column.

    As a general rule, the aggregator. lines match those of the column object.

    code language-none
     <span class="autonumber"><span><b>Example: </b></span></span>
     <p>The Planned&nbsp;Hours column in a task report summarized by Sum may look like the following: </p>
    

    textmode=true valuefield=workRequired valueformat=compound aggregator.function=SUM aggregator.valuefield=workRequired aggregator.displayformat=minutesAsHoursString aggregator.valueformat=compound namekey=workRequired shortview=false

    aggregator. 行可能包含valuefield valueexpression

    ``

    `如果要保存更改并继续编辑视图,请单击​应用。

    单击​保存+关闭​以保存报告。

    单击​保存视图​以将该视图保存在列表中。`

``

recommendation-more-help
5f00cc6b-2202-40d6-bcd0-3ee0c2316b43