Jump to: navigation, search
Line 8: Line 8:
 
<li>Word-process the .doc file from the last PDF: Using wildcards, search for Style Heading 3 and the following term: <br><nowiki>(Column) (*)^13</nowiki></li>
 
<li>Word-process the .doc file from the last PDF: Using wildcards, search for Style Heading 3 and the following term: <br><nowiki>(Column) (*)^13</nowiki></li>
 
<li>Do a global replace with:<br>
 
<li>Do a global replace with:<br>
<nowiki>}}^p{{Temp^p|column=\2^p|text=<br> </li>
+
<nowiki>}}^p{{Temp^p|column=\2^p|text=</nowiki><br> </li>
 
<li>Copy the result to this wiki page, delete the first Temp template-ending stub, add a closing set of double braces (}})</nowiki> at the end, and save the page.</li>
 
<li>Copy the result to this wiki page, delete the first Temp template-ending stub, add a closing set of double braces (}})</nowiki> at the end, and save the page.</li>
 
<li>Then use the following DPL query to format the result as a table on the wiki page, which you can then copy into a Word table for further word-processing.
 
<li>Then use the following DPL query to format the result as a table on the wiki page, which you can then copy into a Word table for further word-processing.

Revision as of 15:19, May 3, 2016

Initial Conversion Job Aids

Procedure: Temp table to convert GIM column descriptions into tabular format


Steps

  1. Word-process the .doc file from the last PDF: Using wildcards, search for Style Heading 3 and the following term:
    (Column) (*)^13
  2. Do a global replace with:
    }}^p{{Temp^p|column=\2^p|text=
  3. Copy the result to this wiki page, delete the first Temp template-ending stub, add a closing set of double braces (

)</nowiki> at the end, and save the page.

  • Then use the following DPL query to format the result as a table on the wiki page, which you can then copy into a Word table for further word-processing.
    {{#dpl:
    |namespace=Documentation
    |titlematch=%{{PAGENAME}}%
    |uses=Template:Temp
    |skipthispage=no
    |include={Temp}:column:text
    |table=,-,'''Column''','''Description'''
    |mode=userformat
    }}
  • Example

    The following example is the ATTEMPT_DISPOSITION table:

    ATTEMPT_DISPOSITION_KEY The key that uniquely identifies the disposition. The value combines the state and the descriptor that provides additional details. The key value enables you to calculate the state by using appropriate bit masks. The first eight bits specify the cause, which equals the integer value that is supplied by Outbound Contact Server. The next eight bits specify the descriptor that is generated by Genesys Info Mart.
    CAUSE The cause as specified in the OCS model. This value can change with localization.
    CAUSE_ID An integer that equals the value that is supplied by Outbound Contact Server to specify the cause.
    CAUSE_CODE The cause code that is equivalent to the OCS model cause. This value does not change with localization.
    DESCRIPTOR Specifies whether the final transition was caused by an agent or by the system, or whether this is unknown. Because not all outbound dispositions support descriptor, most dispositions have only an 'Unknown' value. This is a string value that can be localized or changed, based on reporting needs.
    DESCRIPTOR_CODE The code of the descriptor. This field is set to one of the following values:

    - BY_AGENT - BY_SYSTEM - UNKNOWN

    This value is not localizable and should not be changed.

    CREATE_AUDIT_KEY The surrogate key that is used to join to the CTL_AUDIT_LOG control table. The key specifies the lineage for data creation. This value can be useful for aggregation, enterprise application integration (EAI), and ETL tools--that is, applications that need to identify newly added data.
    UPDATE_AUDIT_KEY The surrogate key that is used to join to the CTL_AUDIT_LOG control table. The key specifies the lineage for data update. This value can be useful for aggregation, enterprise application integration (EAI), and ETL tools--that is, applications that need to identify recently modified data.


    Column Description
    ATTEMPT_DISPOSITION_KEY The key that uniquely identifies the disposition. The value combines the state and the descriptor that provides additional details. The key value enables you to calculate the state by using appropriate bit masks. The first eight bits specify the cause, which equals the integer value that is supplied by Outbound Contact Server. The next eight bits specify the descriptor that is generated by Genesys Info Mart.
    CAUSE The cause as specified in the OCS model. This value can change with localization.
    CAUSE_ID An integer that equals the value that is supplied by Outbound Contact Server to specify the cause.
    CAUSE_CODE The cause code that is equivalent to the OCS model cause. This value does not change with localization.
    DESCRIPTOR Specifies whether the final transition was caused by an agent or by the system, or whether this is unknown. Because not all outbound dispositions support descriptor, most dispositions have only an 'Unknown' value. This is a string value that can be localized or changed, based on reporting needs.
    DESCRIPTOR_CODE The code of the descriptor. This field is set to one of the following values:

    - BY_AGENT - BY_SYSTEM - UNKNOWN

    This value is not localizable and should not be changed.

    CREATE_AUDIT_KEY The surrogate key that is used to join to the CTL_AUDIT_LOG control table. The key specifies the lineage for data creation. This value can be useful for aggregation, enterprise application integration (EAI), and ETL tools--that is, applications that need to identify newly added data.
    UPDATE_AUDIT_KEY The surrogate key that is used to join to the CTL_AUDIT_LOG control table. The key specifies the lineage for data update. This value can be useful for aggregation, enterprise application integration (EAI), and ETL tools--that is, applications that need to identify recently modified data.

    |ICON=}}

    Comments or questions about this documentation? Contact us for support!