Page Comparison

Pending work to be done

•  Create best practice page with solution and configuration advises
•  Improve setup new concern process based on MOL-6 + identified improvements based on other insights (journals, journal periods, DC hierarchy, default scripts to run, default roles & rights, default templates etc)
•  Review standardized ticket list and add all kind of detailed small knowledgable tasks which you run into during implementation, if they cannot be included/improved in the setup new concern process (configuration of internet user, fiscal year, enable cleanup script initial bookings, enable customer deduplication, enable cash register toggle at addon type level, TS plus accounts if needed etc)
•  Update standardized ticket list regarding ticket descriptions. Update legacy and add MXT Academy links where possible
•  Create library of standardized data migration + validation scripts. Could entail customers, owners, reservations, ledgers. (Or re-develop / improve MXTS Implementation Manager now content manager team is mature?)
•  Create list of default templates. Ideally a sub page with files which can simply be imported by the user or even added in new concern scripts.
•  Create overview of default roles&rights setup
•  Create a more concrete overview of roles and responsibilities how to approach new implementation, so it’s clear who does what when it comes to communication, ticket-updating, configurations (client or maxxton, which maxxton roles to distinguish)

What is it?

This article provides a concrete approach for when the project must be delivered. For this article to be useful, it is relevant the project is approached and prepared in accordance with the tools provided by the overarching implementation framework and general understanding of client’s business is there. This article assumes the project products (hereafter: Epics) are defined and the project plan is made.

...