Update 28.0.202618.163701

When running Calculate First Possible Shipment Date from the Sales Order Handling journal, the system would throw an error if the Move Demand Date Planning User Setup record did not exist for the current user. This happened because the setup record was only created when a user first ran the Suggest Move Demand Date function from the Move Demand Date Journal — meaning any user who had not previously used that journal would encounter an error.

The fix ensures the required setup record is created automatically if it is missing, so Calculate First Possible Shipment Date works correctly for all users regardless of prior usage.

When using the Copy Planning Template function, if the source template was an Abakion Standard Template, the copied template incorrectly had Standard Template set to TRUE. This meant the copy appeared as a standard template rather than as a user-owned template, which could cause confusion and unintended behaviour.

The copy function now always sets Standard Template to FALSE on the new template, correctly treating the copy as a customer or user template regardless of the source.

The Category field on Planning Templates was neither editable nor visible in certain views. On the list page, selecting a category did not persist the value back to the record. On the card page, the field was not shown at all and could not be added via personalization.

Both pages have been updated so that the Category field is now consistently visible and editable. The selected value is correctly stored and shown when reopening the list or card.

The descriptions of the default planning templates Low-Level Code-2 and Low-Level Code-3 have been updated to match their respective Code field values. Previously, the descriptions were inconsistent with the codes, which could cause confusion when selecting templates. The descriptions now correctly reflect the template codes.

All public procedures and methods across the codebase have been documented with XML doc comments. This improves code readability, speeds up onboarding for new developers, and enables IntelliSense to display meaningful hover information. The change has no impact on runtime behaviour.

AL keywords such as IF, BEGIN, END, SETRANGE, FINDSET, and others have been normalised to PascalCase throughout the codebase, in line with the Microsoft AL Language style guide and the Abakion AL coding standard. This is a cosmetic change only — AL is case-insensitive and there is no impact on runtime behaviour. The normalisation eliminates reviewer noise from mixed casing and ensures new code is consistent with the standard.