Employee Center Form for Creation from Incident and Request

[Justin Wenner]

Hello,

I would like to create a Form in our employee center with a field 'request' or 'incident' and of the basis of this, it should be create a incident or request. The process are should be handled by a flow.

I try this with a normal maintain item, but the problem is, it is creating per default a request.

How i can realize my introdusion?

Best regards

Justin

[Dr Atul G- LNG · Accepted solution]

Hi @Justin Wenner 

Practically, this is not a valid use case. The reason is that if you make these two options a dropdown and select "Request," which catalog item would you display? Also, it’s not recommended. It's better to educate the users on what should be classified as an incident and what should be classified as a request.

There are already OOTB record producers and catalog items in place. Adding this new one could create configuration issues and impact the OOTB functionality. It’s better to avoid this.

[Justin Wenner]

Hello,

thanks for your quick answer. That was very helpful.

I have for this topic another question. Is it possible to create a form with a connection to the process engine 'flow' and don't automatically create an specific Dataset (Maintain Item = Request, Record Producer = Specific Table)?

[Dr Atul G- LNG]

Hi @Justin Wenner 

Request you please close the earlier question by accepting the answer.

 Is it possible to create a form with a connection to the process engine 'flow' and don't automatically create an specific Dataset (Maintain Item = Request, Record Producer = Specific Table)?

Atul:out of the box (OOTB), every item must have a flow or workflow attached, which is how the REQ (Request) and RITM (Requested Item) get generated. Could you please provide more details or clarify your question further so I can better understand and assist you?

[Justin Wenner]

Hello @Dr Atul G- LNG,

i would like to create a Form that executes a flow and create an incident in the flow. 

The Background is: I would like employees to be able to submit a form for an outage and that submission runs a flow. This flow creates an incident and automatically has actions.

Or is this Way better:

1. Record Producer to create a Incident

2. Flow with Trigger (Record created on table incident)

The problem here is that I would like to have more specific information and not just the short description and description.

Regards

Justin