1. Entity codes

    Article: AN0001808Updated: 04.09.2021

    Model IT contains tens of entities logically divided into particular model layers. These entities contain various properties according to the entity type. Most of entities contain property Name (e.g. name of application, server, project, data center, problem or incident etc.). A number of entities also contain property Code, that uniquely identifies a record by the help of sequences and is used in a global search.

    There are following number series used in the model.

    Class name Logical layer Sequence format in the column Code (code)
    Test round Project layer TR{#:0000000}
    Detailed request Project layer DR{#:0000000}
    Test scenario Project layer TS{#:0000000}
    Test case Project layer TC{#:0000000}
    Test plan Project layer TP{#:0000000}
    Defect Project layer DEF{#:00000000}
    Request for change (RFC) Project layer CHR{#:00000000}
    Project Project layer PRJ{#:00000000}
    Task Project layer TASK{#:00000000}
    Change Project layer CH{#:00000000}
    Incident Operational layer INC{#:00000000}
    Known error Operational layer KNERR{#:00000000}
    Workaround Operational layer WOAR{#:00000000}
    Problem Operational layer PRB{#:00000000}
    Contract Service layer CON{#:00000000}
    Servise request Service layer SREQ{#:00000000}
    Release Project layer REL{#:00000000}
    Configuration item Various layers CI{#:00000000}


    Number series used in related models: 

    Model Class name Sequence format in the column Code (code)
    Knowledge Base Article KB{#:0000000}
    Finance Accountig document ACCDOC{#:0000000}
    Finance Accounting transaction ACCTR{#:00000000}
    Requests User call USC{#:00000000}
    Requests Catalogue request CAR{#:00000000}

    You can change these number series according to your needs. You can also introduce series in other entities. We recommend to use series of different formats for different classes. This will make only relevent records being returned by global search.