Regarding Lead Time Conditions On Change Request

[Astik Thombare2]

Hi Community ,

I'm stuck with one of the tasks in ITSM Simulator 

Task-

Change requests without sufficient lead time pose a greater risk to the environment and should be documented as such. Risk calculations should consider required lead times, as defined by the organization's change policy: 

- If lead time of 7 days is not met for model = Normal change request, Risk should be set as "High", Impact should be left alone.

- If lead time of 3 days is not met for model = Standard change request, Risk should be set as "Moderate", Impact should be left alone.

1. Disable Risk Condition "Insufficient lead time".

2. Add a new risk condition: "Insufficient lead time - Normal Change" so that if a lead time of 7 days is not met for Normal change requests, the Risk will automatically be set to High, and Impact should be left alone.

3. Add a new risk condition: "Insufficient lead time - Standard Change" so that if a lead time of 3 days is not met for Standard change requests, the Risk will automatically be set to Moderate, and Impact should be left alone.

I tried to do it by referring to one of the out-of-the-box risk conditions, but the task is still failing. Can someone please guide me?

[Steven Stidham]

You need to add a condition for the change type -- Model IS Standard (or Model IS Normal) along with the Planned start date relative condition.

[TheKatherine]

Can I ask why we use the field (Model) instead of the field (Type)?

TheKatherine

[AniketS12033647]

The Type field is the legacy field traditionally used to classify change requests into categories like Normal, Standard, Emergency. Many existing workflows, business rules, and triggers are built around this field, so it still exists for backward compatibility.

The Model field is a newer, more flexible construct that references a separate Change Models table. This allows better control and customization of the change process, including states, workflows, transitions, and policies.

In practice, Type and Model values are usually kept in sync initially to maintain compatibility, but Model provides the foundation for future enhancements and finer control over change management