텍스트 모드를 사용하여 보기 편집

텍스트 모드를 사용하여 목록이나 보고서의 보기를 편집하여 표준 인터페이스에서 사용할 수 없는 필드에 액세스하고 보다 복잡한 보기를 만들 수 있습니다.

액세스 요구 사항

을 확장하여 이 문서의 기능에 대한 액세스 요구 사항을 봅니다.

이 문서의 단계를 수행하려면 다음 액세스 권한이 있어야 합니다.

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=ko#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=ko" 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=ko">Design a form with the form designer</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