Activity codes are used for sizing, functionality, localization, and to identify changes to standard components. There is a standard naming convention used for all changes made:
Patches are used to update Sage X3. When customizations are made, a patch can be created to apply the changes to the test system, and to later apply those same changes to the production folder. To create a patch of a change, you enter the objects that have been changed along with the activity codes associated with the modification.
After applying the patch, you can go to the object and re-apply any changes that were lost during the patching process.
- X - Changes made for North American Add-ons
- Y - Changes made by Sage for a client customization
- Z - Changes made by a client for their own customization
- Creating new reports
- Adding a field to a table or screen
- Changing the name of a field on a screen
- Changing the properties on a window
- Creating a new table, screen, window or object
Create a patch
Patches are used to update Sage X3. When customizations are made, a patch can be created to apply the changes to the test system, and to later apply those same changes to the production folder. To create a patch of a change, you enter the objects that have been changed along with the activity codes associated with the modification.
- Patches are created using the Patch creation function (APATCH) under Patches in the Development > Utilities block.
Re-integrate changes and activity codes
After applying the patch, you can go to the object and re-apply any changes that were lost during the patching process.
- Fields that are named with a “Y” or “X” or “Z” will not be changed by standard patches from X3 and can be left as they are.
- It is only the standard fields that can potentially lose changes. These will need to be re-applied manually and activity coded again for future protection.
- It is important that the activity code is assigned at the lowest possible point. If a whole object is assigned an activity code, it will be hard to identify and re-integrate a change when it comes time to remove it for patching.
-
Sage X3 and Sage Software are trademarks of Sage Software, Inc. Microsoft SQL Server, Microsoft SQL Enterprise Manager and SQL Server Management Studio are registered trademarks of Microsoft Corporation. Oracle is is a registered trademark or Oracle Corporation. All other product names used here are trademarks or registered trademarks of their respective owners.
Sage X3 and Sage Software are trademarks of Sage Software, Inc. Microsoft SQL Server, Microsoft SQL Enterprise Manager and SQL Server Management Studio are registered trademarks of Microsoft Corporation. Oracle is is a registered trademark or Oracle Corporation. All other product names used here are trademarks or registered trademarks of their respective owners.
-
