---
type: reference
area: knowledge
status: reference
date: 2026-06-23
created: 2026-06-23
updated: 2026-07-16
tags:
  - knowledge
---
``` explanation
And then the second story, I'll go to a different MVS formers that might be a bit easier.
Here we go. So these two fields, they're currently calculated fields and they're locked completely from the user. We want to change this so that some users have the ability to edit from a dropdown.
So these fields already have a set of accepted values. They're just held in the views.
And currently, they're calculated, as it were, they're calculated on save.
But what we want is for it to only be calculated on the first save of the form. So when you're saving the add form.
and only if the value is empty. If the value is edited by the user in that ad form, then we want to keep what they've done. And we also don't want this logic to be, this calculation logic to be repeating for any other form saves. As soon as the
user has made a decision or the calculation has been done once, then we want to stop that calculation.
So yeah, all of the dropdown values can be found in the views, or I believe it will be a function attached to the form, the MBX form itself. We have similar logic for turning on and off calculation fields.
attached to these two date fields here. In this case, it's on and off by this toggle, but
What we would do instead is just have it on and off by whether you're saving the ad form.
For the first time.
```
Story 1 :  Need more checking

Hello George,

  

Yes, I confirm, but please note that if we received a task Wednesday after 15FR time the deadline will be next Thursday for Prio2, same for Prio3/4 but +1/2 weeks.

  

**Ex:**

1. **Prio2 received on 17/06 at 10 FR time; deadline is this Thursday 18/06.** 

2. **Prio2 received on 17/06 at 15:30 FR time, deadline is next Thursday 25/06 .**

Same rules for Prio3/4.

I have found the process for calculating PSA required date using the Priority, please can you confirm this is the process that should be used for NVS “Processing deadline”:

Priority 1: Processing Deadline = Today

Priority 2 : Processing Deadline = Next closest Thursday

Priority 3 : Processing Deadline = Next closest Thursday + 1 Week

Priority 4 : Processing Deadline = Next closest Thursday + 2 Weeks

Thank you,


case in story 1: too duscuss

for Priority 2, if today is already Thursday, should “next closest Thursday” mean today or the following Thursday?

  › 1. Today (Recommended)  Closest Thursday includes the current date, so a Thursday submission gets today.
    2. Following Thursday   Always pick a future Thursday after today.
    3. None of the above    Optionally, add details in notes (tab).


Story 2 :

	- Type d'ordonnancement et Type de Jalon 
	- Now they are locked but we need to activate them to some user
	- Type of input need to be a dropdown
	- Already populated with a set of values 
	- Only be calculated when doing the add form
	- And if user modified it we want to stop that calculation
	- Drop down values are attached in nvs form


**Context**

There are two fields (Type d'ordonnancement et Type de Jalon) on a model that currently behave as **calculated/auto-filled fields** — the user can't touch them. The team wants to make them **editable by certain users via a dropdown**, but with specific rules about when the auto-calculation kicks in.

---

**The Rules**

**Rule 1 — Editable by some users**  
Certain users should see these fields as a dropdown (values come from the DB/views). Others presumably still see them as read-only.
(what are user allowed to modify those fields?)

**Rule 2 — Auto-calculation only on the ADD form, first save**  
The calculation logic should run **only** when:

- It's an `add` (i.e. `instance.pk is None`, object doesn't exist yet)
- AND the field value is **empty/blank** at the time of saving

**Rule 3 — If the user filled it in, respect their choice**  
If a permitted user typed/selected a value in the add form before hitting save, **don't overwrite it**. The calculation is only a fallback.

**Rule 4 — Never recalculate again after that**  
Once the object is saved (i.e. it has a PK), the calculation should **never run again** on subsequent saves — regardless of who or what triggers the save. in (update case)

---

**The Reference: Date Fields Toggle**

Your team mentioned that similar on/off logic already exists for two date fields, controlled by a toggle. The pattern they want here is the **same switch mechanism**, except instead of a toggle, the switch is simply: **"Is this the first save (add form)?"**