Multiple Modules using Event Handler Rules

[mikejarosch-aw]

If you do not have a PSE script for an event in the first module of a module folder, then scripts for the same event will not fire for that event if they are in sibling modules of the same module folder.

[AdamNaj]

I've tried to reproduce your scenario with the following setup:

The AAA_Added script has the following content:

Write-Log "AAA_Added $(Get-Location)"

And yet I'm still getting the following in the logs - indicating that the script ran fine when I added the 1 item

69444 16:32:21 INFO  AAA_Added master:\system\Modules\PowerShell\Script Library\AAAA_Test\AA_Test\1

What am I doing wrong?

[mikejarosch-aw]

Hi Adam, if you remove Added in AAAA_Test does the AAA_Added fire?

[AdamNaj]

I've looked deeper into it and cannot replicate the problem you reported but I have found another one that could potentially be mimicking for what you have encountered... I have reported it separately for clarity here: #1391

The script and explanation that is available there might help diagnose the problem.

[AdamNaj]

We will be releasing 8.0 shortly. If you want this to be handled in it; I wonder if you could provide me with a scenario that will reliably replicate the issue.

[mikejarosch-aw]

This works reliably for me. It is on the xmcloud local container image. As shown in the image, the ItemName events are executed, but the ExpandInitialValue events are not. If I move ExpandInitialValue events above ItemName, then ExpandInitialValue events are fired, but ItemName are not.

Here are logs where ExpandInitialValue was first on Run 1 and then ItemName was first on Run 2

2460 22 Oct 2025 12:03:29 INFO ## Expand Initial Value: Test Page Run 1
1032 22 Oct 2025 12:03:44 INFO ## Expand Initial Value: Test Item Run 1
3020 22 Oct 2025 12:04:10 INFO ## Item Added: Test Page Run 2
3020 22 Oct 2025 12:04:10 INFO ## Item Renamed: test-page-run-2

I do have activation rules on them, so we are only running for content, but I get the same results if I remove them.

2388 22 Oct 2025 12:08:06 INFO ## Expand Initial Value: 1
2388 22 Oct 2025 12:08:06 INFO ## Expand Initial Value: 6
2388 22 Oct 2025 12:08:06 INFO ## Expand Initial Value: 3
2388 22 Oct 2025 12:08:06 INFO ## Expand Initial Value: thumbnail_A16392E9227E4CB18DBA72C6137AEC47
2388 22 Oct 2025 12:08:06 INFO ## Expand Initial Value: Test Page Run 3
2324 22 Oct 2025 12:08:31 INFO ## Expand Initial Value: Test Item Run 3
2460 22 Oct 2025 12:09:01 INFO ## Item Added: Test Item Run 4
1432 22 Oct 2025 12:09:19 INFO ## Item Added: F
1432 22 Oct 2025 12:09:19 INFO ## Item Added: 7
1432 22 Oct 2025 12:09:19 INFO ## Item Added: 0
1432 22 Oct 2025 12:09:19 INFO ## Item Added: thumbnail_DF70D9D7EB2A4CDDA2EAE0426948EB44
1432 22 Oct 2025 12:09:19 INFO ## Item Added: Test Page Run 4
1432 22 Oct 2025 12:09:19 INFO ## Item Renamed: test-page-run-4

[mikejarosch-aw]

@AdamNaj The xmcloud container image has v7 and I think this is the line causing the issue:

Console/src/Spe/Integrations/Tasks/ScriptedItemEventHandler.cs

Line 64 in bf18450

return;

But, in the main branch, it looks like it has been changed:

Console/src/Spe/Integrations/Tasks/ScriptedItemEventHandler.cs

Line 64 in ea5fe84

continue;

This commit 7ce7265 to fix this issue #1359

Maybe this has already been fixed and will be included in the 8.0 release as a side affect of fixing that issue? Would you be able to test that theory?

[AdamNaj]

Silly me... Whis indeed was already fixed by Michael last year.