IT:Applications/Wiki/Semantics/Planning-EEM/Blog

Template:Article __NODISCUSSION__

Blog

• 08.01.26 em Working on linking Owner to Contacts
• 03.11.25 em Improved, added the following:
  • Type, Sub-Type Show on select
  • Area, Sub-Area Show on select
  • Theme
  • Consequence
• 31.10.25 em EEM 3.4 improvements to streamline with EM 3.5; Show on select: Type, Sub-type, Area, Sub-Area
• 11.09.25 em Added ProjectTask on Type
• 25.08.25 em Optional Argument on START date must be earlier than END date:

Option 1 – Client-side JavaScript Validation (Recommended)
Add custom JavaScript to your wiki (e.g., in MediaWiki:Common.js or MediaWiki:PageForms.js) to check the values of Begin and End before saving:

$(function() {
  // Trigger on form submit
  $("form#pfForm").on("submit", function(e) {
    let begin = new Date($("input[name='Begin']").val());
    let end = new Date($("input[name='End']").val());

    if (begin > end) {
      alert("⚠️ The Begin date must be earlier than the End date.");
      e.preventDefault(); // stop submission
      return false;
    }
  });
});

This prevents users from saving if Begin is later than End.

Option 2 – Page Forms mandatory + Semantic Query Check (Soft Validation)
Make both fields mandatory and later use a query or Lua module to flag invalid data.
{{#ask: [[Category:EM]] [[EEM/Begin::>>{{#show:{{FULLPAGENAME}}|?EEM/End}}]]
 | ?EEM/Begin
 | ?EEM/End
 | format=table
}}

This query will only return pages where Begin is after End, allowing you to identify invalid entries.

Option 3 – Parser Function Check in Template (Warning Message)
Inside Template:EM, add a check that shows a warning if dates are reversed:

{{#ifexpr: {{#time:U|{{{Begin|}}}}} > {{#time:U|{{{End|}}}}}
 | '''⚠️ Error: Begin date is later than End date!'''
 | <!-- dates are valid -->
}}

This won’t block saving but will visibly warn users.

• 18.08.25 em

1. Updated implementation level with the following: not implemented 0-25% (red), partially implemented 26-95% (yellow), implemented 96-100% (green)
2. Template ask short edited "Reminder" or "9" column, added argument, "If values of column "9" and "10" are same, then background color is yellow

   <includeonly>
   |{{{1|}}}
   |{{{2|}}}
   |{{{3|}}}
   |{{{4|}}}
   |{{{5|}}}
   |{{{6|}}}
   |{{{7|}}}
   |{{{8|}}}
   |style="{{#if: {{{9|}}} 
      | {{#ifexpr: {{#time: Ymd|{{{9|}}}}} = {{#time: Ymd|{{{10|}}}}} 
          | background-color:yellow; 
          | {{#switch:{{#expr: {{#replace: {{CURRENTYEAR}}-{{CURRENTMONTH}}-{{#ifexpr: {{CURRENTDAY}} <10 | 0{{CURRENTDAY}}|{{CURRENTDAY}}}} | - | }} < {{#time: Ymd|{{{9|}}}}} }} 
              |1=background-color:green;
              |0=background-color:red;
              |none
          }}
        }}
      | background-color:none;
   }}"|{{{9|}}}
   |{{{10|}}}
   |style="{{#switch:{{{11|}}}|not implemented 0-25%=background-color:red;|partially implemented 26-95%=background-color:yellow;|implemented 96-100%=background-color:green;}}"|{{{11|}}}
   |-
   </includeonly>

• 14.08.25 em Redesign the template header + logo, Version 3.2 to 3.3
• 22.07.25 em corrected Implementation level from implemented > 95% to implemented >95% to avoid error in rendering; removed space between > and 95%
• 19.07.25 em template header has been updated to correct the query table, FROM

<includeonly>

{| class="wikitable sortable" width="90%"
! 
! client
! process
! Status 
! Type
! reason
! owner
! begin
! reminder
! end
! Implementation Level
|-
</includeonly>

TO which all table queries using EEM framework should follow the below format unless otherwise updated

<includeonly>

{| class="wikitable sortable" width="90%"
! 
! Subtitle
! Zone
! Status 
! Type
! reason
! owner
! begin
! reminder
! end
! Implementation Level
|-
</includeonly>

• 08.01.25 em Added Opportunity as Type on EM and MM portals
• 27.12.24 Implementation Level Property changed need colour
• 09.12.23 mm Development under Construction