In the sixth part of our blog series Step by Step to a Ticket System, you saw how an extensive ticket list can be presented in MS word. Today you will learn how you can create a ticket for a work contract and configure a view to be able to check the state of the work on the tickets. Let’s go!
Product type for work contracts
Working with forms is a large strength of in-STEP BLUE. If you would now to create work contracts for recorded tickets in your ticket system, it makes sense to record all the information about a work contract centrally in one form, just like with the tickets. This form should be created with the in-STEP BLUE Form Designer, create a category for the product type Work contract and create the product type that should be allocated to the new state machine for work contracts. You can read how to carry out these steps in Create a product type for tickets.
Specify categories with properties
How can you configure the product type for work contracts? First, create a category for work contracts and provide it with properties like Editor, Description, etc.
When specifying properties, you can also provide an expiry date that will be taken over when the work contract is mapped from the ticket. Additionally, it is recommended to create a product reference on the ticket so as to be able to map a relationship from it later.
Define form for work contract
Next, create a form in the template folder.
The form could look like this:
Confirm states for a work contract
Of course you also need a state machine, for example with the states new, in process and changed.
Confirm the state transfer and define, amongst other things, for what event a work contract should be changed from in process to changed.
Properties of the product type
Then create a product type for a Folder for work contracts and one for the work contracts themselves. A simple description on how to do this the easiest can be found in the above link. Exemplarily, the structure of the product types could look like this:
Pay attention here to the cardinality of the product types: there should be exactly one folder for the work contracts, but no limit on the amount of work contracts. How do the properties of the product type Work contract look now? Allocate the correct instance category, the state machine and the created form template.
Under Further Settings you can define that the name of the work contract should be given automatically. That way you can save time later when creating the work contracts and at the same time use a unique namespace.
Think about creating a standard for the product type Folder for work contracts and allocate a product type.
Deriving a work contract
After you have defined the new product type, you can now do the task that today’s blog entry is all about – creating a work contract for tickets. Open the dialog to manage the components using the menu entry Organizational unit and Components and there the configuration of the command server ... for products (CoreProcess). Deactivate all the commands that you don’t want to use by removing the tick in the Context menu column.
Now create a new command of the type Derive product … and configure it as you see here:
The setting Possible product type enters the product type that the command should be offered for. In this case, the derive command should only be offered for tickets.
Under Settings for derived products, enter what type the derived products should be. All the same, enter the referencing product property ticket of the work contract. With this you can specify that the derived work contracts reference the ticket from which they were derived.
If the ticket references the work contract, that has to be specified in Settings of the source product.
Under Properties to copy, specify which property values should be transferred when a ticket is being derived for a work contract.
In the in-STEP BLUE Help, you can find lots of further setting options and valuable information.
The view tickets and work contracts
After you can create work contracts for tickets, you need an overview in which the tickets can be listed. That is child’s play. Open the dialog to adapt the in-STEP BLUE bar and create a new view.
Select Product dependency hierarchy as the evaluation type. This type of analysis shows your products with your referenced products. Under the settings for of the Folder for tickets, select… That means that all the products of the type Ticket to be found in the folder will be shown in your view. And last but not least: so that the work contracts are given to the tickets, a connection between them as reference properties has to be configured.
To configure the reference property, the following dialog exists. Add a new reference using the “+” button. So that the work contracts are shown on the tickets, select the direction incoming.
Place a check beside … for products (CoreProcess) in the tab Menu items, because then your future derivation commands will be offered in your view. Of course, the columns to be presented in your view should also be defined, select a sensible icon and enter a name for the view like Tickets and work contracts.
When you have created the view, simply allocate the view group Tickets.
Finished. Now you can create a ticket for the corresponding work contract.
In the next entry in the blog series you will learn how you can create a ticket directly from the work contract. Just follow along and come step by step to your own ticket system. And if you have questions or ideas, the get in touch with us at firstname.lastname@example.org or 030/467086-20. We are looking forward to your feedback!