How to retrieve information automatically then freeze it immediately?

Question

Hello !

I am in the process of writing a modification history document in Medini to accompany all of my deliverables. I know it's gimmicky but I would like to automatically retrieve their role and departement from the name of the person who wrote an update (information from the project sheet "Team") . But if his role or departement change in the meantime, the information must not change or disappear in the modification history column (it always has to be the same to know which person has done the modification and what was his role/departement at this exact moment) .

So the question is, is it possible to perform this kind of action in Medini or not at all?

Thanking you in advance for your help!

Ryan.

medini_1066182260 · Answer

Hello everyone, and thank you very much for your responses and sorry for the late answer.

Compared to Nils' answer, I would like to avoid using scripts because the tool will be made available to several people and a simpler solution would be preferable. For this specific case, I prefer that they write directly in a text box rather than having to execute a script each time.

On the other hand, for Jan's answer, I didn't know about assignment history and this is the first time I've heard of it. Would it be possible to have more details? Is this a native function in Medini or something to code upstream?

Thank you again for your help,

Ryan.

medini_1024169437 · Answer

We also have the assignment history, so basically if a role assignment is changed, the old assignment is put on that "stack" to remember who as assigned earlier. I never scripted againts it but that could be an agle too. It basically was the reason why we introduced the history.

Jan

medini_1059007410 · Answer

Hi Ryan,

Storing this kind of information in your checklist (that's where you store your history, right?) is possible via a script. My recommendation would be to have a reference column to select the person (not sure if that would be in your case "REVIEWER 3" as an object or the person object itself), and then have a script, which can be executed on the checklist item(s) (CLI=row(s)). This means the CLI is/are selected in the model browser and you start "Execute > your script" from the context menu.

The script then looks up all the relevant information starting from the referenced person/role and writes it into the string properties of your checklist item. If you do not run the script again (that's why it should not be started for the whole checklist), the information stays at it is.

Regards,

Nils