View Revisions: Issue #1060
| Summary | 0001060: Add job ticket domain and use labels | ||
|---|---|---|---|
| Revision | 2019-05-21 19:32 by rijkr | ||
| Description | IST: A single set of job ticket tags can be configured in config property "jobticket.tags". SOLL-1: Add job ticket domain label. Config properties: (1) "jobticket.domains" : a comma separated list of Job Ticket domains to be applied as job ticket number prefix. Each domain on the list is formatted as "DOM/name", where "DOM" is a unique N-letter upper-case mnemonic, "/" is a fixed separator, and "name" is a case-sensitive single word used in UI context. E.g. "A/DomainA,B/DomainB,C/DomainC". When "A" domain is applied, a generated ticket number looks like "A/EE1-FA3E-6596". (2) "jobticket.domains.enable" : Y | N (default) to enable "jobticket.domains" (3) "jobticket.domains.required" : Y (default) | N, to make a domain compulsory. (4) The last selected domain by a user is saved, and used as default in the next user session. SOLL-2: Add job ticket use label. Config properties: (1) "jobticket.uses" : a comma separated list of Job Ticket uses to be applied as job ticket number prefix. Each use on the list is formatted as "USE/name", where "USE" is a unique N-letter upper-case mnemonic, "/" is a fixed separator, "name" is a case-sensitive single word used in UI context. E.g. "E/Exam,T/Test". If "E" use is applied in domain "A", a generated ticket number looks like "A/E/EE1-FA3E-6596". (1.1) A use item can be restricted for use with one or more domains by appending the domain mnemonics. E.g. "E/Exam/A/C" restricts the "E/Exam" use to domains A and C. (2) "jobticket.uses.enable" : Y | N (default) to enable "jobticket.uses" (3) "jobticket.uses.required" : Y (default) | N, to make a use compulsory. SOLL-3: Extend format of config property "jobticket.tags": (1) A tag item can be restricted for use with one or more domains by appending the domain mnemonics. This is as in SOLL-2 (1.1). (2) If "MATH" tag is applied for use "E" in domain "A", a generated ticket number looks like "A/E/MATH/EE1-FA3E-6596". |
||
| Revision | 2019-05-21 19:08 by rijkr | ||
| Description | IST: A single set of job ticket tags can be configured in config property "jobticket.tags". SOLL-1: Add job ticket domain label. Config properties: (1) "jobticket.domains" : a comma separated list of Job Ticket domains to be applied as job ticket number prefix. Each domain on the list is formatted as "DOM/name", where "DOM" is a unique N-letter upper-case mnemonic, "/" is a fixed separator, and "name" is a case-sensitive single word used in UI context. E.g. "A/DomainA,B/DomainB,C/DomainC". When "A" domain is applied, a generated ticket number looks like "A/EE1-FA3E-6596". (2) "jobticket.domains.enable" : Y | N (default) to enable "jobticket.domains" (3) "jobticket.domains.required" : Y (default) | N, to make a domain compulsory. (4) The last selected domain by a user a saved, and used as default in the next user session. SOLL-2: Add job ticket use label. Config properties: (1) "jobticket.uses" : a comma separated list of Job Ticket uses to be applied as job ticket number prefix. Each use on the list is formatted as "USE/name", where "USE" is a unique N-letter upper-case mnemonic, "/" is a fixed separator, "name" is a case-sensitive single word used in UI context. E.g. "E/Exam,T/Test". If "E" use is applied in domain "A", a generated ticket number looks like "A/E/EE1-FA3E-6596". (1.1) A use item can be restricted for use with one or more domains by appending the domain mnemonics. E.g. "E/Exam/A/C" restricts the "E/Exam" use to domains A and C. (2) "jobticket.uses.enable" : Y | N (default) to enable "jobticket.uses" (3) "jobticket.uses.required" : Y (default) | N, to make a use compulsory. SOLL-3: Extend format of config property "jobticket.tags": (1) A tag item can be restricted for use with one or more domains by appending the domain mnemonics. This is as in SOLL-2 (1.1). (2) If "MATH" tag is applied for use "E" in domain "A", a generated ticket number looks like "A/E/MATH/EE1-FA3E-6596". |
||
| Revision | 2019-05-21 19:06 by rijkr | ||
| Description | IST: A single set of job ticket tags can be configured in config property "jobticket.tags". SOLL-1: Add job ticket domain label. Config properties: (1) "jobticket.domains" : a comma separated list of Job Ticket domains to be applied as job ticker number prefix. Each domain on the list is formatted as "DOM/name", where "DOM" is a unique N-letter upper-case mnemonic, "/" is a fixed separator, and "name" is a case-sensitive single word used in UI context. E.g. "A/DomainA,B/DomainB,C/DomainC". When "A" domain is applied, a generated ticket number looks like "A/EE1-FA3E-6596". (2) "jobticket.domains.enable" : Y | N (default) to enable "jobticket.domains" (3) "jobticket.domains.required" : Y (default) | N, to make a domain compulsory. (4) The last selected domain by a user a saved, and used as default in the next user session. SOLL-2: Add job ticket use label. Config properties: (1) "jobticket.uses" : a comma separated list of Job Ticket uses to be applied as job ticker number prefix. Each use on the list is formatted as "USE/name", where "USE" is a unique N-letter upper-case mnemonic, "/" is a fixed separator, "name" is a case-sensitive single word used in UI context. E.g. "E/Exam,T/Test". If "E" use is applied in domain "A", a generated ticket number looks like "A/E/EE1-FA3E-6596". (1.1) A use item can be restricted for use with one or more domains by appending the domain mnemonics. E.g. "E/Exam/A/C" restricts the "E/Exam" use to domains A and C. (2) "jobticket.uses.enable" : Y | N (default) to enable "jobticket.uses" (3) "jobticket.uses.required" : Y (default) | N, to make a use compulsory. SOLL-3: Extend format of config property "jobticket.tags": (1) A tag item can be restricted for use with one or more domains by appending the domain mnemonics. This is as in SOLL-2 (1.1). (2) If "MATH" tag is applied for use "E" in domain "A", a generated ticket number looks like "A/E/MATH/EE1-FA3E-6596". |
||
| Revision | 2019-05-17 13:00 by rijkr | ||
| Description | IST: A single set of job ticket tags can be configured in config property "jobticket.tags". SOLL: Add option for max. 5 job ticket tag sets "jobticket.tags.set.1" ... "jobticket.tags.set.5". Activate tag sets with config property "jobticket.tags.set": a comma separated list of active Job Ticket tag sets to be applied as job ticker number prefix. Each tag on the list is formatted as "n/TAG/word", where "n" is the jobticket.tags.set.n ordinal ID, "/" is a fixed separator, "TAG" is a unique N-letter upper-case mnemonic, and "word" is a case-sensitive single word used in UI context. E.g.: 1/A/Branch-A,2/B/Branch-B,3/C/Branch-C The last selected tag set of a user a saved, and used as default in the next user session. |
||
| Revision | 2019-05-17 12:57 by rijkr | ||
| Description | IST: A single set of job ticket tags can be configured in config property "jobticket.tags". SOLL: Add option for max. 5 job ticket tag sets "jobticket.tags.set.1" ... "jobticket.tags.set.5". Activate tag sets with config property "jobticket.tags.set": a comma separated list of active Job Ticket tag sets to be applied as job ticker number prefix. Each tag on the list is formatted as "n/TAG/word", where "n" is the jobticket.tags.set.n ordinal ID, "/" is a fixed separator, "TAG" is a unique N-letter upper-case mnemonic, and "word" is a case-sensitive single word used in UI context. E.g.: 1/A/Branch-A,2/B/Branch-B,3/C/Branch-C |
||
