Skip to Content
Last modified by Danniar Firdausy on 2024/09/18 13:41
From version 23.9
edited by Danniar Firdausy
on 2024/09/18 13:41
Change comment: There is no comment for this version
To version 23.8
edited by Danniar Firdausy
on 2024/09/05 12:15
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,12 +1,12 @@
1 1  {{container}}{{container layoutStyle="columns"}}(((
2 2  
3 -In this microlearning , we will explore how to delete unused resources from an eMagiz project. You will learn how to identify and remove resources that are no longer attached to any flows, helping you keep your project clean and organized.
3 +In this microlearning, we'll take a look how to delete a resource from an eMagiz project.
4 4  
5 5  Should you have any questions, please get in touch with [[academy@emagiz.com>>mailto:academy@emagiz.com]].
6 6  
7 7  == 1. Prerequisites ==
8 8  
9 -* Novice knowledge of the eMagiz platform.
9 +* Novice knowledge of the eMagiz platform
10 10  
11 11  == 2. Key concepts ==
12 12  
... ... @@ -23,9 +23,9 @@
23 23  
24 24  == 4. Key takeaways ==
25 25  
26 -* Identifying and removing unused resources in the eMagiz platform is straightforward, with clear indicators showing which resources are no longer in use.
27 -* Resources like Message Definitions and Message Transformations are automatically created by eMagiz and marked with a green dot. Custom definitions, however, will remain in your project and cannot be automatically cleaned up.
28 -* To keep your project manageable, it's recommended to include a manual step in your ACCP or PROD deployment plan to clean up unused resources during every release cycle.
26 +* Cleaning up resources is relatively easy, and the eMagiz platform indicates properly which resources are unused
27 +* Please note that resources with type Message definition & Message transformation are automatically created by eMagiz (with the green dot in the icon). In case you use a custom definition, that resource will remain as a resource on your project (so can't be really cleaned).
28 +* Add a manual step to your ACCP or PROD deployment plan to clean the resources section at every release to keep things manageable.
29 29  
30 30  == 5. Suggested Additional Readings ==
31 31