- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-29-2023 01:34 AM
As far as I am aware, it is recommended to consistently create catalog items in the DEV environment. However, some individuals opt to directly create them in the PROD environment. Could someone please outline all the disadvantages of creating items directly in PROD, along with potential problems that may arise in the near future?
Thank you so much in advance!
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-29-2023 01:44 AM
There can be many ,
- It can be used while being built if not done carefully
- Can send out emails that are not fully verified
- Can trigger Approvals & SLAs
- Complex workflows / flows can take days to built.
That's just from top of my head, I'm sure there are more
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-29-2023 01:53 AM
First of all this is not a best practice to implement items directly in prod and here are few issues
1) By avoiding the process, you run the risk of delivering untested configurations to the live environment because you won't be able to thoroughly test and validate catalogue items, which results the mistakes or problems could happen in the prod environment. This can affect the people using it and make the whole system unstable.
2) Skipping the usual development process poses a risk of not documenting changes properly. This lack of documentation can make it hard for people to understand and manage the modifications that have been implemented.
3) Making things directly in the prod without following the usual steps can make it hard to keep track of different versions. This makes it difficult to undo changes or see how things have changed over time.
4) This can cause issues during the upgrades too as the data on prod and sub prod instances will not be similar
If my answer solved your issue, please mark my answer as ✅ Correct & 👍Helpful based on the Impact.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-29-2023 01:44 AM
There can be many ,
- It can be used while being built if not done carefully
- Can send out emails that are not fully verified
- Can trigger Approvals & SLAs
- Complex workflows / flows can take days to built.
That's just from top of my head, I'm sure there are more
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-29-2023 01:53 AM
First of all this is not a best practice to implement items directly in prod and here are few issues
1) By avoiding the process, you run the risk of delivering untested configurations to the live environment because you won't be able to thoroughly test and validate catalogue items, which results the mistakes or problems could happen in the prod environment. This can affect the people using it and make the whole system unstable.
2) Skipping the usual development process poses a risk of not documenting changes properly. This lack of documentation can make it hard for people to understand and manage the modifications that have been implemented.
3) Making things directly in the prod without following the usual steps can make it hard to keep track of different versions. This makes it difficult to undo changes or see how things have changed over time.
4) This can cause issues during the upgrades too as the data on prod and sub prod instances will not be similar
If my answer solved your issue, please mark my answer as ✅ Correct & 👍Helpful based on the Impact.
