Hello,
Thank you for your reply. This did clear out things a bit for me. Looks like I did have the wrong understanding after all. For me it seems that extending the Incident and Service Request classes is the way to go.
I'm still quite confused though. I'll try to explain it n a real-world example. Let's say I want to create a template for 2 Service Requests:
- Workstation Upgrade Request
- New Printer Request
Under Workstation Upgrade Request I want to have things like:
- component
- amount
- reason
Under New Printer Request I want to have properties like:
- reason
- printer type
I can extend the class by adding all the required properties, but then again when I'll try to make a template, under the Extensions tab I'll find all the added properties. So I'll end up having the Component property when creating a template for,
in this scenario, new printer request, which is not something I want. What I would like to do is to create a template for a given service request, which would contain only those "extensions" that are relevant to that particular request (new printer
request for example). Is this even doable?
There is one more problem that bothers me. I decided I want to start form scratch by deleting the MP I have created and creating a new one. But somehow, when I look at the out-of-the-box Incident Management Library MP, the Incident class in there is extended
with 3 additional properties. I don't know how did this happen, but I cannot delete those new properties thus I cannot "start from scratch". I was thinking about importing the default class but I don't know where to take it from. Any ideas how to
deal with this situation?
Kind regards,
Wojciech