Email Templates: Variant 1 - Intergraph Smart Materials - Version 10.1 - Administration & Configuration - Hexagon

Intergraph Smart Materials Classic Administration (10.1)

Language
English
Product
Intergraph Smart Materials
Subproduct
Classic
Search by Category
Administration & Configuration
Smart Materials/Smart Reference Data Version
10.1

On A.10.51 Email Templates, create an email template for the custom email for requisition feature. This email template must have a predefined base structure for this feature to work properly. This base structure is shown below.

A1051_1

To create an email template with the appropriate structure, create a new template and select the REQUISITION option from the Templates Type list. This structure will create an empty email body. To fill the body with text, use free text or the parameters in the sections. To ensure that the template was created properly, click the Compile button. If the new template was created properly, the following message appears:

Otherwise, you will receive detailed error messages.

Optional Settings

In addition to the mandatory settings of the email template, you can add optional settings. These settings are parameters and free text. Free text can be used everywhere in the template. Parameters can be used only between §Req_Begin§ and §Req_End§, and they must be written in the following form:

#name of parameter#

The parameters are bound to sections. These sections are defined below:

  • Master_Section: between §Req_Begin§ and §Req_End§ and outside the other sections

  • Req_Doc_Section: between §Req_Docs_Begin§ and §Req_Docs_End§

  • Req_VDR_Section: between §Req_VDR_Begin§ and §Req_VDR_End§

  • Req_Line_Section: between §Req_Line_Begin§ and §Req_Line_End§

  • Req_Line Doc_Section: between §Req_Line_Docs_Begin§ and §Req_Line_Docs_End§

  • Req_Line_VDR_Section: between §Req_Line_VDR_Begin§ and §Req_Line_VDR_End§

Every section can contain 32 KB of data. This information is important to keep in mind because during the release-to-procurement process, these sections will be filled with the referenced data. An error occurs when more than 32 KB of data is placed in a section. This situation is discussed later in this help.

To customize the email template subject, use the parameters for the Master_Section. Parameters of other sections cannot be used in the email subject.

The following parameters are allowed.

  • Master_Section and the email subject:

    #proj_id#,

    #r_code#,

    #r_supp#,

    #mr_revision#,
    #sr_revision#,

    #short_desc#,

    #description#,

    #rel_to_proc_date#

  • Req_Doc_Section:

    #req_docs_attd_id#,

    #req_docs_proj_id#,

    #req_docs_pk_type#,

    #req_docs_pk_id#,

    #req_docs_docu_id#,

    #req_docs_docu_code#

  • Req_VDR_Section:

    #req_vdr_attv_id#,

    #req_vdr_proj_id#,

    #req_vdr_pk_type#,

    #req_vdr_pk_id#,

    #req_vdr_vdr_code#,

    #REQ_VDR_COMMENT#

    #req_vdr_schedule_weeks#,

    #req_vdr_promise_weeks#,

    #req_vdr_priority#,

    #req_vdr_prom_delv_date#,

    #req_vdr_rev_delv_date#,

    #req_vdr_delivery_date#,

    #req_vdr_received_by#,

    #req_vdr_distrib_id#,

    #req_vdr_distrib_category#,

    #req_vdr_required_ind#,

    #req_vdr_first_issue#,

    #req_vdr_period#,

    #req_vdr_event#,

    #req_vdr_purpose#,

    #req_vdr_final_issue#

  • Req_Line_Section:

    #req_line_rli_pos#,

    #req_line_rli_sub_pos#,

    #req_line_currency_code#,

    #req_line_budget#,

    #req_line_total_release_qty#,

    #req_line_total_list_qty#,

    #req_line_recommend_qty#,

    #req_line_increased_qty#,

    #req_line_rli_unit_weight#,

    #req_line_rli_weight_unit#,

    #req_line_tag_number#,

    #req_line_ident_code#,

    #req_line_qty_unit_code#,

    #req_line_ity_code#,

    #req_line_dd_code#,

    #req_line_estimated_ros_date#,

    #req_line_procure_channel#,

    #req_line_inq_order_seq#,

    #req_line_proc_order_seq#

  • Req_Line_Doc_Section:

    #req_line_doc_rli_id#,

    #req_line_doc_rli_code#,

    #req_line_doc_attd_id#,

    #req_line_doc_proj_id#,

    #req_line_doc_pk_type#,

    #req_line_doc_pk_id#,

    #req_line_doc_docu_id#,

    #req_line_doc_docu_code#

  • Req_Line_VDR_Section:

    #req_line_vdr_rli_id#,

    #req_line_vdr_rli_code#,

    #req_line_vdr_attv_id#,

    #req_line_vdr_proj_id#,

    #req_line_vdr_pk_type#,

    #req_line_vdr_pk_id#,

    #req_line_vdr_vdr_code#,

    #REQ_LINE_VDR_COMMENT#

    #req_line_vdr_schedule_weeks#,

    #req_line_vdr_promise_weeks#,

    #req_line_vdr_priority#,

    #req_line_vdr_prom_delv_date#,

    #req_line_vdr_rev_delv_date#,

    #req_line_vdr_delivery_date#,

    #req_line_vdr_received_by#,

    #req_line_vdr_distrib_id#,

    #req_line_vdr_distribution_category#,

    #req_line_vdr_required_ind#,

    #req_line_vdr_first_issue#,

    #req_line_vdr_period#,

    #req_line_vdr_event#,

    #req_line_vdr_purpose#,

    #req_line_vdr_final_issue#

    • If a parameter is placed in the wrong section, an error message appears when you click the Compile button. This error message indicates exactly which parameter is in the wrong section.

    • An error message also occurs if a parameter is used more than once.

Below is an example of a properly configured template:

A1051_2