Wiki source code of Cleanup a resource in Create
Version 22.1 by Eva Torken on 2023/08/23 16:20
Hide last authors
| author | version | line-number | content |
|---|---|---|---|
 |
18.1 | 1 | {{container}}{{container layoutStyle="columns"}}((( |
| |
1.1 | 2 | |
| 3 | In this microlearning, we'll take a look how to delete a resource from an eMagiz project. | ||
| 4 | |||
| |
18.1 | 5 | Should you have any questions, please get in touch with [[academy@emagiz.com>>mailto:academy@emagiz.com]]. |
| |
1.1 | 6 | |
| 7 | == 1. Prerequisites == | ||
| 8 | |||
| 9 | * Novice knowledge of the eMagiz platform | ||
| 10 | |||
| 11 | == 2. Key concepts == | ||
| 12 | |||
| 13 | This microlearning is about cleaning up a resource from the Create phase. Resources are attached to flows and can be definition files, transformation files, key stores, or others. These resources can actively be used by flows, and are attached properly. As flows are deleted, or changed in functionality, resources can still be attached to your project but not used by any flow. | ||
| 14 | |||
| 15 | == 3. Cleanup a resource == | ||
| 16 | |||
| 17 | Step 1: Navigate to the Create phase and press the resources link on the top right of the screen | ||
| 18 | Step 2: Locate the resources that are no longer attached to any flow. Whenever the value in the Configuration column is empty, it means that that specific resource is no longer used. See the view below. | ||
| 19 | |||
| |
18.1 | 20 | [[image:Main.Images.Microlearning.WebHome@intermediate-lifecycle-management-cleanup-resource-2.png]] |
| |
1.1 | 21 | |
| 22 | Step 3: Press the delete button to remove the resource from the project | ||
| 23 | |||
| |
22.1 | 24 | == 4. Key takeaways == |
| |
1.1 | 25 | |
| 26 | * Cleaning up properties is relatively easy, and the eMagiz platform indicates properly which 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 | |||
| |
22.1 | 30 | == 5. Suggested Additional Readings == |
| |
1.1 | 31 | |
| 32 | None | ||
| 33 | |||
| |
18.1 | 34 | )))((({{toc/}}))){{/container}}{{/container}} |